Improve Python and TypeScript graph discovery - #238
Merged
Conversation
forhappy
marked this pull request as ready for review
August 13, 2026 19:01
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.
Summary
Why
The HTTPX and NestJS evaluation exposed missing operation vocabulary, weak compound-owner handling, and overly broad TypeScript framework identity propagation. The original ranking refinement also proved too broad when audited against Rust and Java repositories. This PR now uses a total, language-neutral ordering and narrowly evidence-backed owner refinements; language-specific binding interpretation remains in the TypeScript utility.
Source-reviewed query impact
All 25 absent-symbol negative controls pass. The comparison uses frozen low-inference graphs and independently source-reviewed expected seeds, relevant nodes, direction, and ambiguity.
The final low-inference NestJS rebuild retains 60,111 nodes and 79,446 edges, with zero dangling or duplicate edges and 100% source/occurrence backing. Eight invalid relationships remain safely omitted.
Universal qualification
The fixture qualification covers 57 languages, 27 semantic flows, 24 framework families, 1,775 invariants, 82 exact route resolutions, ambiguity and unresolved cases, deterministic clean/warm/rebuild/alternate-checkout byte equality, and enterprise scale ceilings.
The shared ranker contains no language switch. TypeScript occurrence-rule parsing is owned by
frameworks/typescript.rs; other language utilities and resolvers remain isolated and can apply their own evidence encodings without inheriting TypeScript assumptions.Validation
cargo fmt --all -- --checkcargo clippy --workspace --lib --bins --locked -- -D warningscargo test --workspace --lib --bins --locked./scripts/qualify_code_graph_v1.sh --fixtures-onlysh scripts/check_product_boundary.sh