Add scoped overviews, hotspots, and graph freshness warnings - #355
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.
Large graph overviews could not be narrowed to a source area, dependency hotspots required expensive broad output, and answers gave no notice when their index was stale. This adds source-scoped architecture and community views, compact hotspot rankings, and advisory freshness checks against the selected artifact's recorded repository.
hotspotsand MCPget_hotspots, with deterministic distinct-contact and incoming-dependent rankings. Inferred and document relationships are optional labelled layers; unresolved and ambiguous targets remain excluded. Scoped rankings retain dependencies outside the selected area.Validation:
Compatibility: unscoped architecture and existing MCP community defaults retain their meaning. Scoped architecture wraps the original result; MCP envelopes can include optional
freshness. Disposable traversal caches rebuild automatically. Graph and historical schemas remain unchanged.Public qualification: independent graph-record checks matched hotspot rankings, scope boundaries and community membership on pinned Cobra, Flask, Gson, Zod and Axum graphs. Default hotspot text used 427–614 estimated tokens. The frozen-graph warm-index replay passed 22/25 Compass questions versus 18/25 Graphify questions. Mean estimated output was 516 versus 758 tokens; on the 16 questions both tools passed, it was 511 versus 756. This is a debug correctness/token replay with a 180-second query cap, not a latency comparison. Two broad Compass questions missed required markers and one Zod path query timed out. The separate cold run and repeated census timeout are retained; no claim of cold-build speed or complete concept recall is made.
Freshness preflight refuses configured conversion filters and submodules before working-file checks; the CLI regression proves a configured clean filter is never executed. Invalid scope errors remain under 200 bytes without terminal controls. All 14 GitHub CI checks passed on final head
e3ae229f5c65a1296d1fd7114b827bc7789b9669; the PR is mergeable.