Rationale: Does exactly what it claims: a deterministic static scanner of 529 lines plus a self-contained D3 v7 renderer of 2977 lines, with thorough agents docs, structural tests, gitleaks CI, and a worktree-isolated publish script. Keep rather than modernize because no frontier agent technique improves a build-time diagram generator and the live gsvdotcom site is correct. Three grounded defects warrant a small improve follow-up. First, the committed data scan json is stale with only 6 nodes and 0 plugins dated 2026-04-26, while a live scan produces 223 nodes. Second, the gh-pages deploy workflow still fires on every push to main and ships that empty 6-node scan to a host the gotchas doc itself calls legacy. Third, the generated-artifacts test asserts the intercheck quality skill id is present in the committed scan json but it is absent, so that test is red against the committed artifact. None break the live site since regenerate-and-deploy regenerates fresh, but they leave a failing test, a misleading artifact, and a CI job publishing empty output.
Low and complementary. The overlap-domain hull logic parallels intermap call graphs and intersearch embeddings, but interchart uniquely renders whole-ecosystem topology of plugins, skills, agents, MCP, and hooks. No merge warranted. interkasten is a declared companion, not an overlap.
None material. It is a static visualization utility, so 2026 agent-architecture frontier ideas do not define gaps. Adjacent touchpoint: the scanner overlap-domain redundancy signal is regex-based and could be routed through intersearch embeddings, a future enhancement not a deficiency.</sota_gap>
Build-time ecosystem visualizer. The scanner statically walks the monorepo reading plugin json, SKILL md, hooks json, and infra dirs, emitting a JSON node and edge graph plus regex-driven overlap-domain hulls. The template is the D3 force-graph renderer. generate.sh injects data into a placeholder and publishes to generalsystemsventures.com slash interchart. One skill, one slash command, no MCP, no hooks, no subagents. A live scan yields 223 nodes, 298 edges, 38 overlaps.</purpose_confirmed>
[“Regenerate and recommit data scan json from the real monorepo root so it reflects about 223 nodes instead of 6, fixing the red intercheck-quality regression test.”, “Delete or fix the gh-pages deploy workflow; it currently publishes an empty 6-node diagram to legacy GitHub Pages on every push to main.”, “Add a CI guard that regenerates the scan and asserts the node count exceeds a floor near one hundred so a stale artifact cannot silently pass.”, “Optional P3: pin or vendor the D3 v7 CDN dependency and consider routing overlap-domain candidates through intersearch embeddings instead of hand-tuned regex.”]