feat(frameworks): harden activation with project evidence - #87
Merged
Conversation
forhappy
marked this pull request as ready for review
July 30, 2026 18:24
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.
What changed
Illuminate\Support\Facades\Routereceiver and static handlersProjectEvidenceIndexfor npm, Composer, Python, Ruby, Maven/Gradle, Cargo, Go, .NET, and Swift manifestsEngine::default()extraction behavior for callers without repository contextWhy
Framework detection previously allowed path conventions and textual near-matches to contribute too much confidence. That could classify unrelated APIs as framework facts, while filesystem routers lacked repository dependency evidence. The dispatcher was also centralized as a hardcoded language match, making broader framework support harder to extend consistently.
This change makes exact code/configuration evidence authoritative, treats path conventions as supporting evidence, and supplies bounded project context for cases where filesystem structure is itself the framework contract.
Impact
Validation
cargo clippy -p compass-languages -p compass-resolve -p compass-core --all-targets -- -D warningscargo test -p compass-languages -p compass-resolve -p compass-coregraphify update .