Repository navigation
Description
This was generated by AI during triage.
Current status (2026-09-29)
Inspected baseline: main@b64bb2f.
Status: reopened only for the two remaining commitments below. The runtime upgrade and distribution are delivered.
PR #80 upgraded to the owner-approved complete official Archify 3.0.0 runtime: commit 9286c3b9c2cef359e98586b420d769d87bcb163f, 104 pristine files. PR #81 moved runtime ownership into exact @jdylanmc/topo-archify@0.1.0. Integrity checks, historical baselines, adapter boundaries, native rendering, and required notices remain. The historical 214-file old-pin target is superseded by the approved v3 distribution, not a request to restore obsolete vendoring.
Remaining acceptance
-
AC-17: Supply real upstream-suite evidence for the exact shipped Archify 3.0.0 revision under Node.js 22/Linux, integrated through an appropriate existing CI seam. Report required development fixtures/tools separately from the pristine runtime. Do not substitute package smoke, Topocode regressions, or the suite from another upstream revision.
-
AC-10 / NFR-02: Record the maintainer's explicit reconciliation of the original narrow
OFL-1.1wording with the scoped embedded-font attribution implementation and update the maintained specification/policy wording accordingly. Do not silently expand the license allowlist.
Why the prior closure did not finish this scope
The renderer fork's full source suite runs against its 3.0.1 source tree, while the distributed runtime is selected from 3.0.0. Topocode CI runs package/native-family smoke plus its own regression suite, not the complete upstream suite at the selected runtime revision. These are useful but different evidence. The current conservative allowlist still does not list OFL-1.1; that wording mismatch is not evidence of a license violation or missing notices.
Preserved constraints
Keep all renderer access behind @topo/diagram-core, pristine runtime bytes and historical integrity baselines, verbatim upstream/font/brand/trademark notices, and the upstream-first/explicit-patch policy. No renderer patch, new runtime version, broader license policy, or product behavior change is authorized by this backlog cleanup.
This issue is not agent-ready while the policy reconciliation needs owner judgment, and it does not block using the already-published packages.
Evidence: maintained renderer commitments, Topocode CI, license policy, runtime selection, fork source version, and integration evidence limits.
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 real pinned Archify runtime and @topo/diagram-core adapter are shipped. This issue remains open for the explicit renderer commitments preserved by #78, not for rebuilding the working renderer boundary. The current integrity manifest/test covers 62 runtime files, not the required pristine 214-file upstream inventory.
Remaining scope
- AC-10 / NFR-02: explicitly reconcile the original narrow OFL-1.1 allowance wording with the scoped embedded-font notice implementation. Existing shipped notices are not evidence of a license violation; do not silently broaden policy.
- AC-16: preserve and verify all 214 pristine upstream files at d673e8300df60a5c8166abe78787fdc78f6b8000, with explicit tamper failure and no rewritten historical baseline.
- AC-17: run the real upstream suite accompanying that pristine pin in supported Node.js 22/Linux CI. The existing Topocode tests are not a substitute.
- AC-18 / CON-07: retain required upstream license, third-party, brand and trademark material verbatim; keep the upstream-first policy and an explicit tracked patch set if any patches are necessary.
Readiness and dependencies
Remove ready-for-agent because the maintained specification explicitly requires an unresolved license-policy reconciliation. The runtime smoke path is delivered, but full-copy/upstream-suite compliance must not be marked complete from it. No vendor edits, new upstream pin, or expanded license policy are authorized by this cleanup.
Merged delivery evidence: #47, #48, #55, #78. These merge commits are ancestors of the inspected main revision.
Current source and regression evidence:
docs/product-spec.mdpackages/diagram-core/archify-integrity.jsonpackages/diagram-core/src/integrity.tspackages/diagram-core/test/diagram-core.test.mjspackages/diagram-core/package.json.github/workflows/ci.ymldocs/licenses.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-09, FR-02 package boundary, NFR-01, NFR-02, CON-02, CON-03, CON-07.
What to build
A usable workspace renderer boundary that produces an architecture artifact from a frozen example using the agreed unmodified Archify pin. This is a working package-to-artifact path, not only a copied directory. Keep all access through @topo/diagram-core and make the pinned code, upstream suite, integrity baseline, and licensing obligations work together in the normal repository toolchain. Story authoring and the composed product site belong to later slices.
Acceptance criteria
-
AC-04: The rest of topo reaches Archify only through @topo/diagram-core. No other package imports the vendored tree directly and no registry dependency named archify is introduced.
-
AC-10: The existing license gate passes with the vendored package present and the explicitly approved OFL-1.1 allowance; do not broadly relax license enforcement.
-
AC-16: The pristine copy at d673e8300df60a5c8166abe78787fdc78f6b8000 matches all 214 recorded upstream file hashes. A deliberately changed file causes an explicit integrity failure without rewriting the historical baseline.
-
AC-17: The upstream suite accompanying the pinned copy actually runs and passes in CI under the supported environment. Supply required runner/browser glue without editing the pristine copy or substituting an empty/trivially passing gate.
-
AC-18: Retain LICENSE, THIRD_PARTY_NOTICES.md, and brand attribution/trademark disclaimer verbatim. Keep the upstream-first, explicit-listed-patch policy visible.
-
Demonstrate the package rendering a frozen architecture fixture and retaining required notices; this supports the parent render path but does not declare the story or bundle criteria complete.
Verification and readiness
-
Use existing per-package and repository script seams for package-boundary, integrity-drift, and licensing behavior.
-
Run the real upstream suite and one actual artifact-rendering smoke in the supported Node 22/Linux CI environment; report its real requirements and results.
-
Keep existing lint, typecheck, build, unit/integration, license, and browser regression behavior intact. Do not add a repository documentation gate.
Readiness: Fully specified; no prerequisite child. Integrated upstream runner/environment behavior is a delivery risk to demonstrate, not a settled test result or a new product-policy question.
Open product decisions: None for this scoped slice. Return newly discovered material scope decisions to the human.
Blocked by
None.
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
Merge pull request #47 from jdylanmc/jdylanmc/issue-41-diagram-core
[-]Render a pinned, licensed architecture artifact through @topo/diagram-core[/-][+]Complete pristine Archify vendoring, upstream CI, and license-policy reconciliation[/+]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 real pinned Archify runtime and @topo/diagram-core adapter are shipped. This issue remains open for the explicit renderer commitments preserved by #78, not for rebuilding the working renderer boundary. The current integrity manifest/test covers 62 runtime files, not the required pristine 214-file upstream inventory.
Remaining scope
Readiness and dependencies
Remove ready-for-agent because the maintained specification explicitly requires an unresolved license-policy reconciliation. The runtime smoke path is delivered, but full-copy/upstream-suite compliance must not be marked complete from it. No vendor edits, new upstream pin, or expanded license policy are authorized by this cleanup.
Merged delivery evidence: #47, #48, #55, #78. These merge commits are ancestors of the inspected
mainrevision.Current source and regression evidence:
docs/product-spec.mdpackages/diagram-core/archify-integrity.jsonpackages/diagram-core/src/integrity.tspackages/diagram-core/test/diagram-core.test.mjspackages/diagram-core/package.json.github/workflows/ci.ymldocs/licenses.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.
fix(diagram-core): stabilize v3 rendering context
[-]Complete pristine Archify vendoring, upstream CI, and license-policy reconciliation[/-][+]Complete pinned Archify upstream-suite evidence and license-policy reconciliation[/+]jdylanmc commentedon Sep 29, 2026
Backlog reconciliation (2026-09-29)
Reopened with maintainer approval and narrowed to matching-pin upstream-suite evidence plus license-policy wording reconciliation. The pristine 104-file Archify 3.0.0 runtime and npm distribution remain completed. Source-suite success for the fork's 3.0.1 tree is not matching-revision upstream-suite evidence for the shipped 3.0.0 runtime. No license violation is asserted.
Evidence and preserved historical requirements are in the updated issue body. Baseline:
main@b64bb2f. No repository source or credential changes.