Skip to content

feat: upgrade pristine Archify runtime to 3.0.0 - #80

Merged
jdylanmc merged 3 commits into
mainfrom
jdylanmc/archify-3
Sep 28, 2026
Merged

jdylanmc merged 3 commits into
mainfrom
jdylanmc/archify-3

Conversation

@jdylanmc

@jdylanmc jdylanmc commented Sep 28, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • Upgrade @topo/diagram-core from Archify 2.17.0-dev.1 to the complete pristine 3.0.0 release ZIP.
  • Pin exact upstream commit 9286c3b9c2cef359e98586b420d769d87bcb163f and archive SHA-256 e30f65ddab8bbb0c467fa4be5bccf7e3853bd3ee86e8338f31e102037496be18.
  • Retain all 104 upstream files, their bytes and executable modes; no vendor patches. Keep pin metadata outside the upstream tree and preserve the previous integrity baseline unchanged.
  • Keep the runtime checked in as explicitly requested: no build-time download, no new npm renderer dependency.
  • Add v3-required portable output metadata only at the renderer adapter boundary; authored story documents remain unchanged.
  • Preserve Topocode's 12px effective text floor using final-font-aware Lifecycle state sizing and the native minimum route gap.

Visible v3 changes

  • Updated native reader, controls, node index, and notes layout.
  • Native Lifecycle v1 compatibility is retained; empty bands are omitted and terminal states receive the native double border.
  • PNG exports now include the native title row and padded canvas frame. The diagram itself remains uniformly scaled and complete; SVG remains canonical bare geometry.
  • Archify's own removed guided/story-view controls are not Topocode's authored-story catalogue. The catalogue, generated Repository view, source navigation, and canonical exports remain.

Verification

  • Existing renderer baseline was exercised before upgrade; new v3 pin assertions failed on the old runtime as expected.
  • Every checked-in vendor path and byte was compared directly with the checksum-verified official ZIP; the prior v2 manifest was checked against the base revision.
  • Native integrity tests cover expected inventory/version, actual rendering, equivalent output, bounded batches, tampering, missing/extra files, and symlink rejection.
  • Existing gallery test reproduced the v3 Lifecycle text regression at 1280x720 before the adapter correction; its five-viewport assertions now pass.
  • All 52 browser cases passed, including all five families, final glyph containment, linked navigation, generated repository exploration, base-path bundles, source details, and SVG/PNG exports.
  • Raster assertions now verify the exact v3 frame dimensions and the inner diagram's uniform scale; no export or geometry assertions were skipped.
  • The complete local TOPO_BROWSER_TEST_PORT=41873 corepack yarn test:regression passed at exact head 91b671f79a07bce1f11c0b389af8e8487fef04f6: all lint/typecheck/build/root/package/license checks, 125 CLI tests, 9 diagram-core tests and 52 browser cases.
  • The actual clean Topocode checkout generated its v3 review site successfully (188 files, 861 edges, 80,303 lines). Live Lifecycle review at 1280x720 measured a minimum 12.428px effective text with all 14 labels visible before the portability correction; the unchanged five-viewport requirement passes on the final local candidate too.
  • The first hosted run passed 125 CLI tests and 51/52 browser cases; the added wide-Lifecycle glyph assertion exposed a Linux system-ui font difference. The follow-up 91b671f uses an explicit Arial/Helvetica stack without lowering the font floor or removing containment assertions. Both the complete local gate and exact-head Node.js 22/Linux CI now pass.
  • The follow-up also runs v3 rendering in owned temporary working directories. Regression coverage confirms that a caller's unrelated story.html symlink cannot affect generated output-path validation.
  • No source or dependency changes were made in the primary checkout.

Scope boundaries

The official runtime ZIP does not include the upstream development test suite. This PR does not claim completion of that separate #41 obligation, expand the license allowlist, or close #41. Upstream LICENSE, third-party/brand notices and font attribution remain verbatim.

Native delivery receipts bind the raw native artifact. Topocode's typography/narrative adaptations and shared-asset packaging produce different final bytes; the documentation explicitly does not represent those bytes as an unchanged upstream artifact or a successful upstream finalize result.

The owner requested review before proceeding. Keep this PR in draft; do not merge or close issues automatically.

Refs #41

Vendor the complete official v3.0.0 ZIP with a new pinned inventory and preserve the prior baseline. Adapt generated output metadata and Lifecycle final typography without changing upstream bytes or authored story contracts. Keep the 12px effective-text requirement and native route clearance.

Refs #41
Account for v3 terminal borders, empty lifecycle bands, duplicate node-index text, and title-framed raster exports. Assert the canonical diagram retains a uniform scale inside the frame, preserving existing topology, readable text, source navigation and SVG/PNG coverage.

Refs #41
Use a consistent Lifecycle sans-serif stack across macOS and Linux while retaining glyph containment and the 12px floor. Resolve v3 output metadata only inside owned temporary directories, independent of caller files. Keep pristine vendor bytes unchanged.

Refs #41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Complete pinned Archify upstream-suite evidence and license-policy reconciliation

1 participant