feat: preserve runtime dependency provenance - #299
Merged
Conversation
shaggitza
force-pushed
the
fix/277-route-provenance
branch
from
July 29, 2026 16:43
20a741a to
99747c4
Compare
shaggitza
force-pushed
the
fix/277-route-provenance
branch
from
July 29, 2026 17:28
99747c4 to
839f616
Compare
This was referenced Jul 29, 2026
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
Phase 1 of #277: preserve authoritative declared FastAPI dependency provenance in runtime extraction and use exact source-attested providers as mypy propagation roots.
EndpointDependencyGraphevidence while retaining the legacyEndpoint.dependenciesprojection unchanged;Dependantoccurrences, including qualified physical callable identity/source, scope, cache semantics, Security scopes, partial/callable structure, nesting, duplicates, and graph-local limitations;None(not collected) from established-empty, conditional, and unavailable graphs without weakening route-discovery status;This closes a concrete false negative: app/include-level dependencies and independently established nested providers can now propagate through their helper calls. In the DI example,
POST /itemsis correctly affected throughcheck_scope -> get_current_user -> decode_token.Fail-closed behavior
depends_or_security, not falsely classified as declaration-localSecurity.Scope
This tranche intentionally does not modify secure-AST extraction, route assembly/source ownership, baseline/target lifecycle reconciliation, effective dependency overrides, or general callable points-to/dataflow. #277 remains open for those later phases.
Validation
tests/benchmarks/test_pilot_typed_run_v3.py(posix_spawn(..., setsid=True)unavailable locally);tests/benchmarks/test_ground_truth_run_v1.pyprocess-limit child spawn is unreliable under the active local agent fleet.srcandtestsfiles.GitHub Actions is authoritative for both platform-sensitive benchmark files and the Python 3.10–3.12 matrix.