diff --git a/.agents/skills/topo/SKILL.md b/.agents/skills/topo/SKILL.md index a91e24b..ff777ec 100644 --- a/.agents/skills/topo/SKILL.md +++ b/.agents/skills/topo/SKILL.md @@ -38,9 +38,10 @@ Corepack, model service, account or renderer download is needed. Serve the output with a static server. Hosting, access control and uploading are separate owner decisions. Preserve all emitted license notices. -The init-first home and Rust/Tauri support are unreleased source/local-candidate features; public -npm 0.1.0 predates it. Use a candidate containing this change, not a claim that -the existing registry version was updated. +Init-first Home and Rust/Tauri require Topocode 0.2.0 or newer. After that +release is published, install with `npm install --save-dev @jdylanmc/topo-code@0.2.0`. +Release preparation is not proof of registry availability; never silently +substitute the older 0.1.0 workflow. `topo enrich` is a separate, explicitly configured provider-command workflow for secondary commentary. It is not required for source-grounded story editing. diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 57ab0d4..1cdfadd 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -42,8 +42,9 @@ jobs: - run: yarn test:regression - name: Verify the installed public toolbelt run: | + PACKAGE_FILE="jdylanmc-topo-code-$(node -p "require('./distribution/package.json').version").tgz" node scripts/pack.mjs dist - node scripts/package-smoke.mjs dist/jdylanmc-topo-code-0.1.0.tgz ../renderer/dist/jdylanmc-topo-archify-0.1.0.tgz + node scripts/package-smoke.mjs "dist/$PACKAGE_FILE" ../renderer/dist/jdylanmc-topo-archify-0.1.0.tgz - uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4 with: name: npm-candidates diff --git a/CHANGELOG.md b/CHANGELOG.md index 5713164..4d8f021 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,10 +1,56 @@ # Changelog -Notable changes are recorded here. Initial npm candidates are version 0.1.0; -publication remains a separate release-owner action. +Notable changes to the public Topocode package are recorded here. Renderer +versions are independent; publication remains a separate release-owner action. ## Unreleased +## 0.2.0 - 2026-09-30 + +Release preparation date; npm publication is not implied by these notes. +Changes since the published 0.1.0 baseline. The renderer remains +`@jdylanmc/topo-archify@0.1.0` with pristine Archify 3.0.0. + +### Added + +- Create a ready-to-serve branded Home on plain or skills-enabled `topo init`, + including empty/unborn repositories. Reuse its categorized inventory across + Home and stories, retain selectable Repository exploration, and bundle + truthful unscanned sites. See #84. +- Support minimal first-party Rust language and Tauri bridge selection through + normal commands, with deterministic parser-backed evidence, lexical ownership + and explicit partial/unresolved coverage. JS/TS remains the default; no Cargo, + proc-macro or model execution is introduced. +- Add hash-bound technical Workflow stories with decision/data shapes, exact + node/edge excerpts and source-traced versus inferred connections. Explicit + Graphviz 16.0.0 has its own layout receipts and a narrowly pinned embedded + EPL-2.0 exception with full notices/source availability. See #85. +- Include generic Rust/Tauri fixtures and installed authoring/operation guidance + for fresh contexts and cache recreation, without consumer application data. + +### Fixed + +- Share one app-owned theme across shell, evidence, authored/generated viewers, + focus navigation and native default exports without modifying renderer bytes. +- Preserve Rust impl/trait methods through validated publication, preview and + bundle; structural owner identities keep named methods and qualified anchors + stable across comment-only moves. +- Reject uncertain Tauri helper positions across spreads/rest bindings and + invalidate obsolete helpers after dot/computed-member writes while preserving + known scalar and unmodified-receiver controls. +- Preserve renderer-owned evidence/specification assets and distinguish native + from adapted/shared-output hashes. Roll back reported replacement failures + and reject orphaned preview caches rather than publishing mixed generations. +- Keep byte-pinned upstream license files unchanged through Windows-style Git + checkout conversion without weakening digest checks. + +## 0.1.0 + +Initial public release baseline: +[`6c7b5c9`](https://github.com/jdylanmc/topo-code/tree/6c7b5c926d54fadcae51c450edfb210cd6be38dc), +tag `npm-bootstrap/v0.1.0-6c7b5c926d54fadcae51c450edfb210cd6be38dc`. +The original preparation entries below are retained as historical notes. + ### Renderer upgrade - Upgrade `@topo/diagram-core` to the complete pristine Archify 3.0.0 release @@ -23,26 +69,6 @@ publication remains a separate release-owner action. ### Added -- Support explicit first-party Rust language and Tauri bridge selection through - normal scan/preview/bundle commands, retaining JS/TS defaults, deterministic - source identities, lexical ownership, per-plugin partial/unresolved evidence - and conservative shadowing/mutation handling. No Cargo, proc-macro or model - execution is introduced. -- Add snapshot-bound technical Workflow stories with decision/data shapes, - exact node/edge excerpts and source-traced versus inferred connections. - Explicit Graphviz 16.0.0 rendering has engine-specific layout receipts and a - narrowly pinned embedded EPL-2.0 exception with full notices and source - availability. Native diagram families remain unchanged. -- Ship generic Rust/Tauri fixtures, installed authoring/operation guidance and - transferable parser, rendering, theme, publication and regeneration findings. - No consumer application's authored diagrams or caches are included. - -- Create a ready-to-serve, branded diagram Home on plain or skills-enabled - `topo init`, including empty/unborn repositories without scanning. Reuse the - categorized inventory across Home and native story pages, keep Repository - exploration selectable and old deep links working, and bundle truthful - unscanned sites with notices. This is unreleased; public npm 0.1.0 is unchanged. - - Add GitHub-only publication of verified tarballs: normal OIDC and explicit first-package bootstrap through version/commit-bound tags, with a UI-managed token exposed only to its publish step. No local npm authentication is needed. @@ -142,22 +168,6 @@ publication remains a separate release-owner action. ### Fixed -- Retain Rust impl/trait methods through validated Repository publication, - preview, bundle and cache recreation. Structural impl/extern owner identities - keep named descendants and qualified anchors stable across comment-only moves. -- Reject uncertain Tauri helper positions across spreads/rest bindings and - invalidate obsolete helpers after equivalent dot/computed-member writes, - while preserving known scalar and unmodified-receiver controls. -- Preserve byte-pinned upstream license files through Git checkout conversion, - including Windows autocrlf, without weakening exact license digest gates. - -- Make shell, evidence, authored/generated viewers and native default exports - share one app-owned theme across focus navigation, stored preferences, media - changes and native actions without altering pristine renderer package bytes. -- Preserve renderer-owned evidence/specification assets through scan and bundle, - distinguish native and adapted/shared-output hashes, and roll back reported - generation-replacement failures rather than leaving mixed generations. - - Publish explicit local tarball paths so npm cannot interpret `dist/filename.tgz` as GitHub shorthand; verify both release modes with offline dry-run publication. - Prevent static-bundle browser fixture cleanup from waiting on unused TCP diff --git a/README.md b/README.md index 3e72d72..ff6aa92 100644 --- a/README.md +++ b/README.md @@ -14,34 +14,34 @@ No hosted service, no telemetry, no account. Normal commands also support explicitly selected, parser-backed **Rust/Tauri** and snapshot-bound technical workflows with decisions, exact node/edge source -evidence and an explicit Graphviz renderer. These capabilities are unreleased; -the existing registry 0.1.0 is unchanged. See [supported configuration, portable +evidence and an explicit Graphviz renderer in **Topocode 0.2.0**. +See [supported configuration, portable examples and limits](./docs/rust-tauri.md). The goal is to put a software engineer in the human-in-the-loop position: every claim the tool makes about a codebase is backed by evidence you can follow, and everything a human adds is recorded as such. -> **Status: Local preview.** The scan-to-site workflow, deterministic reports, +> **Release preparation: 0.2.0.** The scan-to-site workflow, deterministic reports, > source-grounded stories, static analysis modules, optional AI commentary, and > pinned Archify 3.0.0 rendering are implemented. Topo is the storybook for > architects: the generated shell inventories every diagram while preserving -> real Archify viewers. npm candidate packages and portable project skills are -> available; registry publication remains a separate release-owner step. +> real Archify viewers. This source prepares the next minor release; registry +> publication remains a separate release-owner step. ## Install the toolbelt -The public `@jdylanmc/topo-code@0.1.0` predates the init-first home described -here. Use a locally built candidate tarball for this unreleased behavior; no -version bump or publication is implied. After installing the candidate, run +Once 0.2.0 is published, install the public package below. Its exact +`@jdylanmc/topo-archify@0.1.0` dependency is installed automatically; no source +checkout or paired tarball is required. Then run `npm exec --no -- topo init . --skills`. This adds project-local Topocode skills and instructions without replacing existing files. Read `.agents/skills/topo/SKILL.md`, serve, author/validate stories, preview and bundle using the installed CLI. Plain `topo init` creates the same site without skills. -Install both candidate tarballs in one npm command: +Version 0.2.0 adds init-first Home and the supported Rust/Tauri workflow: ```sh -npm install --save-dev /path/to/jdylanmc-topo-archify-0.1.0.tgz /path/to/jdylanmc-topo-code-0.1.0.tgz +npm install --save-dev @jdylanmc/topo-code@0.2.0 npm exec --no -- topo init . --skills npm exec --no -- topo serve . ``` @@ -141,7 +141,8 @@ node /absolute/path/to/topo-code/packages/cli/dist/main.js scan "$PWD" ``` Documentation uses `topo` as shorthand for that built entry point. The supported -input for scanning is a local Git repository containing TypeScript/JavaScript. +input for scanning is a local Git repository containing TypeScript/JavaScript, +or explicitly selected Rust/Tauri source as described in the technical guide. Initialization and authored stories do not require scannable source. Unknown configuration, unresolved local/workspace imports and incomplete scans fail explicitly. An intentional `--allow-partial` preview is visibly non-authoritative diff --git a/distribution/README.md b/distribution/README.md index 1bddb17..358b46b 100644 --- a/distribution/README.md +++ b/distribution/README.md @@ -5,20 +5,18 @@ project agent skills, schemas, prebuilt assets and notices. No hosted service or model invocation during scanning. The exact renderer dependency is `@jdylanmc/topo-archify@0.1.0`, containing pristine upstream Archify **3.0.0**. +This source prepares **Topocode 0.2.0**. Once that version is published: + ```sh -npm install --save-dev /path/to/jdylanmc-topo-archify-0.1.0.tgz /path/to/jdylanmc-topo-code-0.1.0.tgz +npm install --save-dev @jdylanmc/topo-code@0.2.0 npm exec --no -- topo init . --skills npm exec --no -- topo serve . npm exec --no -- topo bundle . --output ./site-output --base-path /architecture/ ``` -The init-first Home described here is **unreleased**. The already-public -`@jdylanmc/topo-code@0.1.0` predates it; use a local candidate containing this -change. No registry update or version bump is implied. - -Installing both tarballs in the same command satisfies the exact renderer -dependency normally, without a fake registry, workspace links or source checkout. -The install requires the other declared public npm dependencies. +The public install resolves the exact unchanged renderer and other declared +npm dependencies automatically, without paired tarballs or workspace links. +Preparing this source/package does not itself establish registry availability. `--skills` is opt-in: creates `.agents/skills/topo`, `.agents/skills/topo-story-authoring`, `.agents/skills/topo-archify-maintenance` @@ -47,13 +45,13 @@ provider-command surface, not part of scanning. Generated `.topo/cache` output is disposable; configuration and authored documents are not. Explicit first-party Rust/Tauri selection, technical decision/data workflows -and hash-bound source evidence are supported by this unreleased candidate. +and hash-bound source evidence are part of 0.2.0. Read `docs/rust-tauri.md` and the synthetic `examples/rust-tauri/` before configuring analysis or authoring technical stories. Rust/Tauri are parser-backed and partial, not Cargo/rust-analyzer semantics. Graphviz is an explicit bounded backend with its own receipts and complete EPL-2.0/source-availability notices, not a native-renderer fallback. App-owned themes also govern native default -exports. None of these changes updates the already-published 0.1.0. +exports. Version 0.1.0 remains immutable; 0.2.0 is a distinct minor release. Bundles are plain static files with notices; hosting, deployment and access control are yours. Runtime rendering does not download Archify or call a model. diff --git a/distribution/package.json b/distribution/package.json index bbc16e9..6c8c206 100644 --- a/distribution/package.json +++ b/distribution/package.json @@ -1,6 +1,6 @@ { "name": "@jdylanmc/topo-code", - "version": "0.1.0", + "version": "0.2.0", "description": "Local-first repository architecture storybook: topo CLI and portable agent skills.", "type": "module", "license": "MIT", diff --git a/docs/npm-release.md b/docs/npm-release.md index 964ec39..fffbba7 100644 --- a/docs/npm-release.md +++ b/docs/npm-release.md @@ -1,16 +1,26 @@ # npm distribution and release Issue [#13](https://github.com/jdylanmc/topo-code/issues/13) ships one practical -CLI-plus-skills toolbelt, not a public SDK. Initial candidate versions: +CLI-plus-skills toolbelt, not a public SDK. Versions for this release preparation: -**Init-first Home is unreleased.** The already-public 0.1.0 predates this change. -Locally built 0.1.0 candidate tarballs can prove the change without changing -registry contents; do not republish that version or imply it contains this fix. +**Topocode 0.2.0** adds init-first Home, minimal parser-backed Rust/Tauri, +technical Graphviz workflows and the associated theme/evidence hardening. +The public 0.1.0 release remains immutable. Preparation is not publication: +the release owner must complete the normal GitHub-hosted OIDC flow and verify +the public artifact before claiming availability. | npm package | Version | Upstream runtime | | --- | --- | --- | | `@jdylanmc/topo-archify` | 0.1.0 | Archify 3.0.0, `9286c3b9c2cef359e98586b420d769d87bcb163f` | -| `@jdylanmc/topo-code` | 0.1.0 | exact dependency on `@jdylanmc/topo-archify@0.1.0` | +| `@jdylanmc/topo-code` | 0.2.0 | exact dependency on `@jdylanmc/topo-archify@0.1.0` | + +After publication, consumers install only the public Topocode package; npm +resolves the unchanged renderer dependency: + +```sh +npm install --save-dev @jdylanmc/topo-code@0.2.0 +npm exec --no -- topo init . --skills +``` The renderer fork is https://github.com/jdylanmc/topo-archify. Its `integrations/topo-npm/release.json` records upstream version/commit and the @@ -35,11 +45,11 @@ corepack yarn install --immutable node scripts/bootstrap-renderer.mjs /path/to/jdylanmc-topo-archify-0.1.0.tgz TOPO_BROWSER_TEST_PORT=41875 corepack yarn test:regression node scripts/pack.mjs dist -node scripts/package-smoke.mjs dist/jdylanmc-topo-code-0.1.0.tgz /path/to/jdylanmc-topo-archify-0.1.0.tgz +node scripts/package-smoke.mjs dist/jdylanmc-topo-code-0.2.0.tgz /path/to/jdylanmc-topo-archify-0.1.0.tgz ``` The private adapter declares an exact required peer so Yarn can restore the -development workspace before the first renderer publication. Yarn reports that +development workspace independently of renderer registry access. Yarn reports that peer missing until bootstrap. Bootstrap performs a real isolated npm tarball install, verifies its identity/integrity, then copies it into this checkout's `node_modules`; it does not alter manifests/lockfiles, fake a registry, or use @@ -67,7 +77,7 @@ External runtime dependencies remain declared. Consumers receive schemas, three portable skills and project instructions, example source-change fixtures and composed legal notices. Debug source maps and tests do not ship. -The candidate includes optional native Rust parser dependencies, an explicitly +Version 0.2.0 includes optional native Rust parser dependencies, an explicitly selected Tauri bridge and `@viz-js/viz@3.30.0` with the exact embedded Graphviz license exception. Installed `docs/rust-tauri.md` and `examples/rust-tauri/` cover mixed-language operation, technical authoring and cache-only recreation. @@ -93,9 +103,10 @@ human approval. No schedule or auto-merge is configured. Creating the exact bootstrap tag described below is an explicit release action, not a routine push. Ordinary CI packs and tests; it neither handles npm secrets nor publishes. The -Topocode CI workflow pins the renderer packaging commit, not a floating branch. For this -coordinated first release that commit must be pushed before remote CI can fetch -it. Update that ref deliberately for later renderer releases. +Topocode CI workflow pins the renderer packaging commit, not a floating branch, +and derives the Topocode tarball filename from `distribution/package.json`. +Version 0.2.0 retains the existing renderer revision. Any later renderer ref +change must be deliberate and available remotely before CI can fetch it. ## GitHub-hosted trusted publishing @@ -123,7 +134,7 @@ and verify those exact bytes: Neither path uses a GitHub environment; leave npm's **Environment name blank**. The publish argument must be an explicit local path, such as -`./dist/jdylanmc-topo-code-0.1.0.tgz`. npm can classify the bare +`./dist/jdylanmc-topo-code-0.2.0.tgz`. npm can classify the bare `dist/filename.tgz` form as GitHub shorthand rather than a local file. Package regressions run the actual workflow arguments through credential-free, offline `npm publish --dry-run` and compare the consumed tarball's integrity. @@ -142,7 +153,11 @@ has no OIDC permission; its tested artifact digest and Actions run remain eviden not a claim of npm provenance. Both paths disable lifecycle scripts during publication. Package repository URLs identify the actual downstream repositories. -### First-package bootstrap from browser and GitHub Actions +### Historical first-package bootstrap from browser and GitHub Actions + +The following 0.1.0 procedure is retained for the initial-publication record. +It is **not** the 0.2.0 release path: the package already exists, and bootstrap +must never be used as a fallback for missing or failed OIDC configuration. The operator can use npmjs.com in a browser even when this machine cannot reach the registry/CLI. No local npm authentication is needed. The **human enters the @@ -228,13 +243,21 @@ Do not create a GitHub environment just for this workflow. ### Normal releases entirely through GitHub -In **Actions**, select **Publish renderer to npm** in `topo-archify`, choose -**Run workflow**, branch `main`, and the exact committed version (initially -`0.1.0` before its first publication). Use `mode=verify` for a verification-only -run. After independent review and established npm trust, use `mode=oidc` for a -new, unpublished version. Normal OIDC never consults the bootstrap secret. - -Then use **Publish Topocode to npm** in `topo-code` in the same way. Its +For Topocode **0.2.0**, keep the already-published renderer **0.1.0** unchanged; +do not republish it or start a renderer release. After independent review and +normal merge of the release preparation, the authorized owner selects +**Publish Topocode to npm** in `topo-code`, **Run workflow**, branch `main`, +version `0.2.0`, and `mode=oidc`. `mode=verify` remains available for a +verification-only run. The version must exactly match the committed +`distribution/package.json`. + +Established npm trusted-publisher configuration is a prerequisite. If it is +missing or OIDC fails, stop and have the owner correct that configuration; +do not use the historical bootstrap token. Normal OIDC never consults that +secret. A future independently approved renderer upgrade follows its own +versioned workflow rather than automatically following the Topocode version. + +The Topocode verification job deliberately fetches the exact renderer from **the public npm registry**, runs the full regression and installed consumer journey, and only then offers the Topocode artifact for publication. A missing renderer version @@ -249,7 +272,8 @@ Published versions are immutable; never rerun an already-published version as an overwrite attempt. Retain the workflow run, source commit and artifact digest as release evidence. A post-publication check failure may occur after npm accepted the upload: investigate registry state rather than retrying publication blindly. -No workflow has been dispatched, token handled or package published by the worker. +Release preparation and local tarball tests do not establish publication; +retain the successful hosted run and public-artifact verification as the receipt. Sources: [npm trusted publishing](https://docs.npmjs.com/trusted-publishers/), [official source and current allowed-action requirements](https://github.com/npm/documentation/blob/main/content/packages-and-modules/securing-your-code/trusted-publishers.mdx), diff --git a/docs/product-spec.md b/docs/product-spec.md index 2ec4cdd..ad3b978 100644 --- a/docs/product-spec.md +++ b/docs/product-spec.md @@ -11,7 +11,9 @@ This file is the maintained product intent. GitHub issues track bounded work and keep delivery history. The original MVP specification is preserved in [issue #40](https://github.com/jdylanmc/topo-code/issues/40). This version reconciles that specification with the product on `main` after -[PR #71](https://github.com/jdylanmc/topo-code/pull/71). +[PR #71](https://github.com/jdylanmc/topo-code/pull/71), the init-first +[PR #84](https://github.com/jdylanmc/topo-code/pull/84), and supported Rust/Tauri +[PR #85](https://github.com/jdylanmc/topo-code/pull/85), prepared for 0.2.0. The product now has one persistent Archify storybook shell. PR #71 intentionally removed the old PixiJS/WebGL repository explorer. Original clauses that required @@ -24,8 +26,8 @@ same shell: structural packages/directories, files, and compiler declarations rendered as bounded Archify views. This replaces neither authored stories nor their renderer-neutral contract and does not restore WebGL. The approved init-first migration makes Home the default and Repository an -explicit selection. This source/local-candidate change is unreleased; public -npm 0.1.0 predates it. +explicit selection. This is part of the 0.2.0 release contents; registry +publication remains a separate release-owner action. ## People and core workflow @@ -181,7 +183,7 @@ This table preserves the disposition of every numbered original requirement. | --- | --- | | **FR-01; AC-01** | Shipped: committed renderer-neutral stories and runtime anchor resolution. | | **FR-02; AC-13, AC-15** | Shipped adapter and atomic failure behavior. The requirement to retain a parallel WebGL renderer is superseded by PR #71. | -| **FR-03; AC-05, AC-06** | Init-first source migration: branded Home and truthful unscanned empty state; scan/preview populate one categorized inventory. Public npm 0.1.0 predates it. The old explorer requirement remains superseded by PR #71. | +| **FR-03; AC-05, AC-06** | Implemented for 0.2.0: branded Home and truthful unscanned empty state; scan/preview populate one categorized inventory. The old explorer requirement remains superseded by PR #71. | | **FR-04; AC-07** | Shipped through the existing serve command. | | **FR-05; NFR-04; AC-08** | Shipped host-agnostic static bundles. | | **FR-06; AC-11** | Partly shipped: bounded catalogue configuration. Broader composition/extensibility and the required manual walkthrough remain unresolved above. | @@ -217,13 +219,14 @@ sketch canvas (**N-4**), manual JSON authoring (**N-5**), an unlisted renderer fork or font changes (**N-6**), rebuilt commodity diagramming infrastructure (**N-7**), heuristic coverage gates (**N-8**), or restoration of the retired WebGL explorer. It does not authorize publishing under the `archify` name. -Rust/Tauri prototypes, Graphviz, plugin marketplaces and `.topo-view.json` -remain outside the supported core story contract; this migration integrates none. - -Further npm publication remains a release-owner step. The existing public -0.1.0 does not contain the init-first migration. The local candidate -CLI-plus-skills tarball, opt-in `topo init --skills`, exact renderer dependency, -and clean installed-consumer regression are implemented; see +Standalone Rust/Tauri prototypes, plugin marketplaces and `.topo-view.json` +remain outside the supported contract. PR #85 adds bounded first-party +Rust/Tauri analysis and explicit Graphviz technical workflows through normal +commands; see [supported capabilities and limits](./rust-tauri.md). + +Publication of 0.2.0 remains a release-owner step. Its CLI-plus-skills package, +opt-in `topo init --skills`, unchanged exact renderer dependency, Home, +Rust/Tauri support and clean installed-consumer regression are implemented; see [distribution](./npm-release.md). #57 is paused Unified Modeling Language work. #70 is the separately aligned repository exploration delivery. #74, #75, #76, and #77 cover diff --git a/docs/rust-tauri.md b/docs/rust-tauri.md index d0749de..b2ace6f 100644 --- a/docs/rust-tauri.md +++ b/docs/rust-tauri.md @@ -1,7 +1,9 @@ # Rust, Tauri and technical stories -This is supported **unreleased candidate** behavior of normal `topo` commands, -not an experiment executable or a registry update. Node 22 and 24 are supported. +This is supported **Topocode 0.2.0** behavior of normal `topo` commands, +not an experiment executable. Node 22 and 24 are supported. After publication, +install with `npm install --save-dev @jdylanmc/topo-code@0.2.0`; release +preparation alone is not a registry-availability claim. The installed package includes this document, the story JSON Schema and `examples/rust-tauri/`; no development checkout or previous agent session is required. @@ -67,7 +69,7 @@ and a source-order discriminator among identical headers, such as ordinals, not lines/columns. Named descendants, qualified anchors and Rust ownership edges survive unrelated comments/blank lines; positions and hashes still change as evidence. Adding or reordering structurally identical owners -can change their ordinals. Old unreleased candidate anchors containing +can change their ordinals. Pre-0.2.0 development anchors containing `@line:column` must be reconciled once against the corrected structural names. Tauri helper propagation requires an established scalar argument position. diff --git a/scripts/package-smoke.mjs b/scripts/package-smoke.mjs index bae48f9..09c1f4b 100644 --- a/scripts/package-smoke.mjs +++ b/scripts/package-smoke.mjs @@ -9,6 +9,7 @@ import { createHash } from "node:crypto"; const [topoTarball, rendererTarball, retainedDirectory] = process.argv.slice(2); if (!topoTarball || !rendererTarball) throw new Error("Usage: node scripts/package-smoke.mjs topo.tgz renderer.tgz [new-evidence-directory]"); +const expectedVersion = JSON.parse(await readFile(new URL("../distribution/package.json", import.meta.url), "utf8")).version; const root = retainedDirectory ? path.resolve(retainedDirectory) : await mkdtemp(path.join(tmpdir(), "topo-installed-consumer-")); @@ -88,7 +89,7 @@ syncBuiltinESMExports(); `); const manifest = JSON.parse(await readFile(path.join(installed, "package.json"), "utf8")); assert.equal(manifest.name, "@jdylanmc/topo-code"); - assert.equal(manifest.version, "0.1.0"); + assert.equal(manifest.version, expectedVersion); assert.equal(manifest.dependencies["@jdylanmc/topo-archify"], "0.1.0"); assert.equal(manifest.scripts, undefined); assert.equal((await lstat(installed)).isSymbolicLink(), false);