fix: Dart dependency graphs and cross-language caller isolation - #492
Conversation
There was a problem hiding this comment.
inspect review
Triage: 25 entities analyzed | 0 critical, 0 high, 9 medium, 16 low
Verdict: standard_review
Findings (0)
Reviewed by inspect | Entity-level triage found 0 high-risk changes
There was a problem hiding this comment.
inspect review
Triage: 25 entities analyzed | 0 critical, 0 high, 9 medium, 16 low
Verdict: standard_review
Findings (0)
Reviewed by inspect | Entity-level triage found 0 high-risk changes
There was a problem hiding this comment.
inspect review
Triage: 25 entities analyzed | 0 critical, 0 high, 9 medium, 16 low
Verdict: standard_review
Findings (0)
Reviewed by inspect | Entity-level triage found 0 high-risk changes
|
Refreshing the stale PR head after the final explicit-this regression fix. Final local validation: 1,115 core/CLI tests pass, including eight focused core regressions and cold/warm CLI coverage. The branch is now 2c427f2; CI must evaluate that head. |
There was a problem hiding this comment.
inspect review
Triage: 26 entities analyzed | 0 critical, 0 high, 9 medium, 17 low
Verdict: standard_review
Findings (0)
Reviewed by inspect | Entity-level triage found 0 high-risk changes
There was a problem hiding this comment.
inspect review
Triage: 26 entities analyzed | 0 critical, 0 high, 9 medium, 17 low
Verdict: standard_review
Findings (0)
Reviewed by inspect | Entity-level triage found 0 high-risk changes
Summary
Fixes #491.
Validation
Boundaries
This fixes the reported extraction and mixed-language collision bugs, not complete Dart semantic resolution. Dart import aliases, package URIs, dynamic dispatch and incremental resolution reuse require separate work. Dart remains conservatively ineligible for incremental edge reuse.