Repository navigation
LOD-4: inspect exact relationships through semantic summaries and bundles #218
Description
Focused implementation help requested under #193 / LOD-4. The nested-cut candidate #216 conserves every edge and shows typed bundle counts, but users still need to explore the exact original relationships inside/between summaries.
Claim an owned branch/worktree and coordinate renderer/helper ownership with #216 before editing. Borrow CodeGraph techniques only; no shared package.
Acceptance:
- From a visible summary or typed directional bundle, open an accessible exact relationship list with original edge IDs/types, source/target titles and navigation to the actual source items. Internal links, self-loops, parallel edges and reverse directions must remain distinct and fully accounted for.
- Preserve canonical node/edge identity and selected path through expand/collapse/Back. Summaries and bundles are display-only; no synthetic node/edge or position writes on navigation. Keep the camera return and both Auto hysteresis states fixed by LOD-WIRE-1: navigate nested graphs with clean focused buses #216.
- Provide useful upstream/downstream/focused-neighborhood navigation, explicit counts and named context when endpoints are outside the current view/cut. Do not silently drop connections because their card is not placed; the complete list remains reachable on phones.
- Exercise an owned nested fixture containing cross-service cycles, mixed types, parallel edges, internal links, self-loops and a high-degree hub. Verify every source edge appears exactly once in the appropriate partition, original API readback is unchanged and real mouse/keyboard/touch navigation preserves focus.
- Add failing-before invariants and strict real browser coverage with zero retries/required skips, retain failure artifacts and use existing fixture/auth/edge-first cleanup helpers. Preserve Persist unsent layout changes across reload and browser restart without cross-account replay #181 layout durability and current small-graph behavior.
- Update the existing architecture/validation ledger with actual capability and remaining spatial/scale/loading limits; get exact-source independent review and all applicable CI before dev closeout.
No release/deploy/protection changes or edits to the owner's localhost graph are needed. All source SVG/data are still loaded in #216; this issue does not establish 1k/10k readiness or hosted parity.
Activity
mvalancy commentedon Oct 28, 2026
I am taking the Core relationship-exploration implementation in owned worktree
.worktrees/core-lod-relationships-20261028, branchfeat/semantic-relationship-exploration-20261028, based explicitly on frozen #216 sourcea311154bf154af977a238d4b5de55773efa4e2dc. #216 validation continues on its unchanged tree; this follow-up will reconcile live dev and receive its own review/gates before integration.Initial scope: exact internal/bundle relationship lists, endpoint identity and direction, upstream/downstream neighborhood navigation, complete phone-accessible fallback and preserved camera/cut/focus. I will add executable negative controls before claiming acceptance. No shared CodeGraph library and no source graph writes from inspection.
#217 remains available for independent transfer/MCP work. Please coordinate here before editing the semantic overview/relationship helper files.
mvalancy commentedon Oct 28, 2026
Accepted in dev
007148f1a526b8ef028222a429b346a67e5c3c2cthrough #216. Remote parents are dev77899e98...and reviewed source6a6792650e0d455b361e0c6d38bc0f08f4a00f42; complete tree8e92c6679f3434abe2964e3eee5e7d8f6873cf51matches the pre-merge tested composition exactly. Native admin merge used the repository owner's standing dev-only authorization; independent agent review was not represented as a non-author GitHub approval.Post-dev CI40640788120 and Comprehensive40640788203 passed. Downloaded all nine unified reports: 102 passed, zero failures/warnings/skips/evidence errors, exit0/no timeouts, clean unchanged dev source/fingerprint
49622b2e487d00fd17cf789075a189fca230f9832d325c722240830cf2873b53. Counts: static4, smoke6, new-user42, semantic2, nested2, layout9, routes7, mobile27, performance3. Living effects separately passed3. Applicable quality/unit/build/security, real Neo4j MCP and all three runtime-image contracts passed; runtime logs confirm API/MCP/SQLite and replacement recovery. Main/nightly-only production stack and PR-only comment jobs were not applicable, not claimed as executed.Final browser artifact contains every referenced attachment. All six nested JSON/PNG pairs were checked: zero card/control intersections, unrelated crossings/overlaps and diagonals, max1 bus/cell, with183 original relationships accounted for. Five PNGs are byte-identical to the independently reviewed pre-merge images; the changed desktop overview was viewed again and is clean. Real journeys passed unchanged API snapshots, zero navigation mutations and strict edge-first owned-fixture cleanup. Earlier failures and corrections remain in PR discussion/repo ledgers.
Closing exact relationship exploration: original edge IDs/types and endpoint titles remain inspectable from internal groups, typed directional bundles and item neighborhoods. High-degree hub, self-loop, parallel/reverse and cross-service relations were checked against exact API-derived partitions. Incoming/outgoing/two-hop lists, filters, item inspection/Back and keyboard/touch focus/camera return passed. Hidden/unplaced endpoints remain explicitly counted and reachable in the complete list.
This accepts exact exploration and bounded group traces. Detailed item/path routing remains #220; full LOD scale/loading/hosted/release work remains #193.