Repository navigation
Description
Reconciled status (2026-09-27)
Inspected baseline: main@c8e22ec. Maintained intent: docs/product-spec.md.
Disposition: completed; closing this bounded delivery.
Completed: topo bundle validates the composed site, stages and atomically publishes static output beneath a configurable base path, preserves existing output on failure, and checks shipped viewer/font notices. Plain-server browser coverage exercises the bundle without a Topocode process. The old explorer-in-bundle clause is intentionally superseded by #71; it must not be restored to satisfy the historical wording.
Remove the obsolete blocking relationship to #43: its prerequisite implementation is on main, and its remaining follow-up scope is not a prerequisite for this completed delivery.
Merged delivery evidence: #53, #71, #78. These merge commits are ancestors of the inspected main revision.
Current source and regression evidence:
packages/cli/src/bundle.tspackages/cli/src/bundle.test.tspackages/site/tests/e2e/catalogue.spec.tsdocs/product-spec.md
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)
Parent
#40 - Specification: Storybook-for-architecture whiteboard MVP.
Source revision: 2026-09-19T12:09:45Z; complete specification body SHA-256 1965e96d069d64a85cb7850abde9d91249874a7cf1bd2e0b38197262a86827de.
Requirements: FR-05, NFR-01, NFR-04, S-4, CON-01.
What to build
Provide the new supported topo bundle command that emits the composed site as deployable static files. The output includes stories, the catalogue, retained explorer, required assets, and notices; a consumer can serve it without a topo process and put its own hosting/authentication in front. Reuse the same composition contract as local serving rather than inventing a second site.
Acceptance criteria
-
AC-08: A bundle renders correctly from a plain static file server with no topo process running and no topo server runtime assumption.
-
AC-09: Distributed output carries MIT and SIL OFL 1.1 notices covering embedded viewer and font bytes, using the established notice machinery.
-
Honor the specification's host/base-path boundary through documented configuration; do not hard-code the author's machine, local topo origin, hosting provider, or authentication service.
-
Include the catalogue, stories, assets, and explorer coherently. Preserve the agreed render-failure/no-partial-artifact behavior.
-
This slice does not implement upload, deployment, public URLs, PR preview orchestration, authentication, or npm publication.
Verification and readiness
-
Serve the emitted directory using a plain static server and use Playwright to open the catalogue, a story, and the explorer with no topo process.
-
Assert that references/assets resolve under the documented deployment configuration and that required license notices are present.
-
Verify malformed/render-failing input cannot be reported as a successful partial bundle.
-
When the navigation slice is assembled, its wrapper URLs must also work in bundled output; that is assembled acceptance, not an invented prerequisite for starting this independent bundle work.
Readiness: Fully specified; needs the composed site. The navigation slice is a sibling, not a prerequisite; both must be present for complete parent acceptance.
Open product decisions: None for this scoped slice. Return newly discovered material scope decisions to the human.
Blocked by
- Define owner-controlled composition and complete customization walkthrough #43: Browse and customize a generated story catalogue alongside the explorer
A closed prerequisite alone is insufficient: its implementation must be available on this delivery's agreed base.
Boundaries
-
Scope is Specification: Storybook-for-architecture whiteboard MVP #40, not the broader historical Roadmap: deferred architecture and engineering-health capabilities #1 roadmap. Preserve existing scanner, explorer, curated views, and enrichment behavior.
-
No hosting, authentication, deployment, public npm publication, human sketch canvas, or mandatory model service.
-
No heuristic staleness or explanation-coverage gate. Structural/source validation does not prove semantic truth.
-
Use the existing unit/script/browser verification seams and keep the repository regression gates. No documentation gate is added.
-
The source snapshot for this breakdown has AC-14 already delivered by PR chore(lint): add correctness baseline #39. Begin implementation from a base containing that merged change.
-
Keep the preserved prototype unchanged. Do not silently edit the vendored renderer or substitute an unapproved upstream version.
-
The implementation owner chooses local code structure within the agreed contracts; return newly discovered material product choices to the human.
Delivery grouping
Intentionally separate coherent deliveries, one eventual PR per child; not one parent-wide implementation PR. No delivery is launched by publication.
No assignee or exclusive ownership is claimed. Publication does not authorize worker dispatch, implementation, merge, or parent closure.
Assembled acceptance
The complete parent acceptance remains all AC-01 through AC-19 over the assembled state. Independent child completion is not a claim that the full MVP is shipped. The final delivery owner verifies the complete local authoring, composition, linked navigation, and static bundle journey once all prerequisite changes are on the agreed base. Parent closure and merges remain human-owned.
Activity
fix(cli): preserve composed bundle data
fix(cli): share site payload validation
Merge pull request #53 from jdylanmc/jdylanmc/issue-45-bundle
jdylanmc commentedon Sep 27, 2026
Backlog reconciliation (2026-09-27)
Inspected baseline:
main@c8e22ec. Maintained intent:docs/product-spec.md.Disposition: completed; closing this bounded delivery.
Completed: topo bundle validates the composed site, stages and atomically publishes static output beneath a configurable base path, preserves existing output on failure, and checks shipped viewer/font notices. Plain-server browser coverage exercises the bundle without a Topocode process. The old explorer-in-bundle clause is intentionally superseded by #71; it must not be restored to satisfy the historical wording.
Remove the obsolete blocking relationship to #43: its prerequisite implementation is on main, and its remaining follow-up scope is not a prerequisite for this completed delivery.
Merged delivery evidence: #53, #71, #78. These merge commits are ancestors of the inspected
mainrevision.Current source and regression evidence:
packages/cli/src/bundle.tspackages/cli/src/bundle.test.tspackages/site/tests/e2e/catalogue.spec.tsdocs/product-spec.mdExisting 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.