Repository navigation
feat: integrate bounded dependency-neighborhood navigation on main - #33
Merged
Merged
Conversation
New1Direction
marked this pull request as ready for review
October 28, 2026 06:41
This was referenced Oct 28, 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.
Clean integration of draft PR #24 onto current main
Ports tested source-backed graph neighborhood navigation on top of the now-merged server-sliced control room (#32), avoiding old stacked ancestry.
Behavior
/api/neighborhood?id=<existing node>&depth=1|2returns a deterministic, evidence-linked subgraph (maximum 90 nodes / 300 edges), with original relationship directions, selected center, explicit truncated/omitted counts, and source-only/noncausal labels.Merge gate
Fresh Python 3.11/3.13 regression, actual headless Chrome (mobile to desktop, 405-node fixture and graph traversal), layout tests, and read-only repo.ing GitHub smoke must pass. No deployment or production mutation.
Limits
Only source-backed structural links, not authenticated runtime dependency or causal outage proof. Single-operator loopback preview, no hosted tenant controls.