Repository navigation
fix: repair export and receiver resolution gaps - #2
Merged
Merged
Conversation
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.
CommonJS export chains left 678 direct
express()calls unresolved, while member fallback could connectres.format()to an unrelated localformat()function. Rust module roots, conditional re-exports and reduced return annotations also lost receiver information. This change repairs those paths and includes semantic facts in incremental invalidation.Changes
?types.Fixed-corpus results
The oracle stays pinned at
d2e0389, with the same four source revisions and every edge retained. P and R below mean agreement with that upstream snapshot, not semantic ground truth.Shared edges increase by 3,092 net (3,224 additions, 132 removals). Non-route node identities remain 100% aligned. The global 97%/95% gate is not fully met. Gin's relative P drops partly because newly enabled routes produce containment edges absent from upstream. Some removed shared edges remain real coverage gaps; they are not all claimed as correctness improvements.
The bilingual investigation explains causes, remaining gaps and incompatible route representations. Machine-readable evidence records the runtime commit, binary hashes, all per-kind results and independent SQLite intersections. README performance numbers remain pinned to their original revision; this PR makes no new speed claim.
Validation
cargo build --release --locked -p cgr— passed with Rust 1.94.1.CGR_SYNC_SEQUENCES=6 CGR_SYNC_STEPS=100 cargo test --locked --workspace— 137 passed, 1 existing ignored, including 600 random edit steps.--workspace --exclude cg-kernel --all-targets -- -D warnings) and the CI package-format check — passed.default.INTERSECTreproduces all four strict shared-edge counts.head -3.One-off proof scripts, fixtures, SQLite snapshots and logs remain outside the repository. The changed files contain runtime code, a correction to the existing CI smoke harness, and documentation/results. The vendored kernel and both READMEs are unchanged.
GitHub CI run: all nine checks passed for
9f1c1c3, including Linux/macOS/Windows tests and smoke checks, static musl, lint and kernel reproduction.