Graph PR-B: clean (non-overlapping) demo seed spacing + force reseed#63
Merged
Conversation
…ed (PR-B) The demo sub-graphs were laid out on a 140px grid — far under the node-card collision diameter (~224px) — so they loaded as overlapping "garbage piles". - hierarchyDemo.ts: sub-graph grid spacing 140 -> 260 (> collision diameter), so the seeded layout is non-overlapping on load with zero physics cost (matters for the 1000-node showcase). Nodes stay placed/pinned (no drift). - create-hierarchy-demo --force: deletes the existing demo (edges -> work items -> graphs, in order, so no orphan edges) and recreates it, so the spacing fix can be applied to an already-seeded DB. Verified: reseeded (17 graphs / 2911 items / 4073 edges); a 90-node sub-graph has 0 overlapping card pairs; THE GATE 5/5. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
🧪 Comprehensive Test Suite
Full-stack smoke gate runs in the CI workflow. |
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.
The demo sub-graphs were seeded on a 140px grid — under the ~224px card collision diameter — so they loaded as overlapping piles.
hierarchyDemo.ts: sub-graph spacing 140 → 260 (> collision diameter) → non-overlapping on load, zero physics cost (important for the 1000-node Compute Core showcase). Nodes stay pinned (no drift).create-hierarchy-demo --force: tears down the existing demo (edges → work items → graphs, so no orphan edges) and recreates it, to apply the spacing fix to an already-seeded DB.Pairs with PR-A (one-shot physics): PR-A's Organize/auto-layout cleans any graph; PR-B makes the canonical demo clean by construction so it never needs organizing.
Verified: reseeded the dev DB (17 graphs / 2911 items / 4073 edges); a 90-node sub-graph has 0 overlapping card pairs; THE GATE 5/5.
🤖 Generated with Claude Code