Repository navigation
fix: improve scoped call resolution and quality reporting - #3
Merged
Merged
Conversation
NianJiuZst
marked this pull request as ready for review
November 1, 2026 13:26
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
External constructor results could bind to unrelated project methods, same-named Rust types and nested functions could share targets, and Rust call chains and Python factories could lose receiver evidence. This follows merged #2 with focused runtime fixes and separates incomplete-oracle coverage from target agreement.
Changes
?.Same-corpus results
The four source revisions, indexed file sets, source bytes and upstream
d2e0389are unchanged. The original strict all-edge key and full edge sets remain reported. Shared edges increase by 877 net: 980 additions and 103 removals. Removed shared edges are not all claimed as old false positives; conservative modeling still leaves coverage gaps.The new P* measures exact target agreement only for cgr calls at sites already labeled by upstream. Full upstream call recall is unchanged in definition, and all additional unlabeled edges are counted separately. This is conditional agreement, not semantic precision or a replacement for the original global gate.
Express already scored 99.28% under this definition before these changes; the denominator change is not presented as an algorithmic improvement. Its one lost strict shared edge is a callback reference; shared call count stays unchanged. Non-route node identity remains 100% aligned. The original 97%/95% strict gate remains unmet, and Tokio's conditional P* slightly declines.
Details: report, machine-readable evidence. Runtime commit:
0d48a07caa67791e64dccf015922a877ab3f9fee.Local validation
One-off proof scripts, fixtures, databases and logs stay outside the repository. Both READMEs, vendored kernel code and previous performance numbers are unchanged; this PR makes no new performance claim. Hosted CI is separate from the local evidence above.
GitHub CI run: all nine checks passed for
7ecbf5f469474f00d7fae8a2e7dbe38807452e46, including Linux/macOS/Windows tests and smoke, static musl, lint and kernel reproduction.