Repository navigation
Description
This was generated by AI during triage.
Current status (2026-09-29)
Inspected baseline: main@b64bb2f.
Status: completed by PR #79, merged as bb468ead0bd5919c88c3ea8097a1e75904abed37 and present on current main.
-
Default Repository canvas in the existing persistent Archify shell.
-
Package/directory -> file -> compiler-declaration drill-down with breadcrumbs, back navigation, source evidence, and durable scope/page/focus URLs.
-
Bounded, paginated real Archify diagrams; no silent truncation of represented entries, with static-relationship evidence available beyond a page's visible endpoints.
-
Dirty/partial/stale and missing-evidence states remain explicit; bundling rejects stale repository evidence, including changed already-untracked source.
-
The same exploration works through
topo serveand plain static bundles with deployment base paths. -
Existing authored stories and their contract are preserved. The retired
/explorer/route and WebGL runtime remain absent.
The owner reviewed the delivery and accepted it for v0.1. Subsequent PR #80 upgraded the pristine renderer to Archify 3.0.0; PR #81 published the CLI-plus-skills package without undoing this delivery.
Evidence: merged PR #79, current exploration contract, and current product intent. Static compiler relationships are not runtime execution, timing, ownership, or exhaustive-impact claims.
Remaining richer view composition (#9), owner customization (#43), and broader roadmap (#1) are separate scope, not unfinished replacement exploration.
Previous issue text and original requirements (historical; current disposition is above)
Reconciled status (2026-09-27)
Inspected baseline: main@c8e22ec. Maintained intent: docs/product-spec.md.
Disposition: remains open for the scope below.
The retirement is complete: #71 removed the old WebGL/Pixi explorer from source, generation, serving and bundles. The persistent Archify storybook and scanner/evidence foundations exist, but the replacement generated repository-exploration experience described here is not implemented.
Remaining scope
- Discover and agree the replacement interaction and information architecture before implementation.
- Keep generated exploration source-grounded, honest about incomplete evidence/history, and integrated with the persistent catalogue, deep links, static base paths, keyboard access and responsive viewer containment.
- Render through the real pinned @topo/diagram-core boundary; keep the retired /explorer/ route and WebGL assets absent.
Readiness and dependencies
Backlog/discovery only; not ready-for-agent and not authorized for implementation. This is replacement exploration, not unfinished removal work and not permission to change authored stories.
Merged delivery evidence: #71, #78. These merge commits are ancestors of the inspected main revision.
Current source and regression evidence:
docs/product-spec.mdpackages/cli/src/catalogue.tspackages/cli/src/bundle.test.tspackages/site/tests/e2e/catalogue.spec.ts
Existing exact-main CI is successful. This reconciliation inspected current code, committed regression coverage and merged history; it does not claim a new test run, manual walkthrough, visual acceptance, cross-machine experiment, or approval of paused work.
Historical issue scope (preserved; current disposition and readiness are above)
Context
The current Storybook-style shell delivery removes the legacy WebGL repository explorer from the shipped site. Its route, navigation entry, and explorer-only assets must not remain advertised or served; useful scanner and source-evidence foundations remain available for future use.
Backlog outcome
Design and implement a future repository architecture exploration experience using real, pinned Archify through Topo's established diagram boundary. The replacement must be source-grounded, preserve honest scanner/evidence and partial-history states, and fit the persistent diagram catalogue rather than reintroducing a disconnected second application.
Scope guard
Backlog only; not authorized in the current shell delivery. This issue does not authorize implementation, readiness labeling, restoration of the removed WebGL route, or changes to authored .topo stories.
Acceptance direction
- Repository architecture exploration is rendered through real Archify, not the retired WebGL explorer.
- Exploration is generated from committed repository/scanner evidence with explicit incomplete or non-authoritative states.
- It integrates with the site shell, deep-linking, static bundle/base-path behavior, keyboard access, and responsive iframe containment.
- The old /explorer/ product and WebGL-specific assets remain absent.
- Exact interaction and information architecture require separate discovery before implementation.
Activity
jdylanmc commentedon Sep 27, 2026
Backlog reconciliation (2026-09-27)
Inspected baseline:
main@c8e22ec. Maintained intent:docs/product-spec.md.Disposition: remains open for the scope below.
The retirement is complete: #71 removed the old WebGL/Pixi explorer from source, generation, serving and bundles. The persistent Archify storybook and scanner/evidence foundations exist, but the replacement generated repository-exploration experience described here is not implemented.
Remaining scope
Readiness and dependencies
Backlog/discovery only; not ready-for-agent and not authorized for implementation. This is replacement exploration, not unfinished removal work and not permission to change authored stories.
Merged delivery evidence: #71, #78. These merge commits are ancestors of the inspected
mainrevision.Current source and regression evidence:
docs/product-spec.mdpackages/cli/src/catalogue.tspackages/cli/src/bundle.test.tspackages/site/tests/e2e/catalogue.spec.tsExisting exact-main CI is successful. This reconciliation inspected current code, committed regression coverage and merged history; it does not claim a new test run, manual walkthrough, visual acceptance, cross-machine experiment, or approval of paused work.
perf(diagram-core): bound native batch lifetimes
perf(cli): stage repository viewers sequentially
perf(cli): share generated viewer runtime assets
test: budget full-repository integration scans
feat: add Archify repository exploration (#79)
jdylanmc commentedon Sep 29, 2026
Backlog reconciliation (2026-09-29)
Closing as completed: PR #79 delivered the owner-reviewed, source-grounded default Archify Repository view, and it remains on main through the v3 renderer upgrade and npm release. Replaced the stale 'not implemented' status with bounded delivered behavior and evidence.
Evidence and preserved historical requirements are in the updated issue body. Baseline:
main@b64bb2f. No repository source or credential changes.