refactor(toolkit): dispatch toolkit-js compact variants on full patch version

toolkit-js now selects its compact-js variant on the full
<major>.<minor>.<patch> compactc version instead of truncating to
<major>.<minor>, since a compactc patch can ship a contract format expecting a
different compact-js patch. Renames the variant workspaces (compact-0.29 ->
compact-0.29.0, etc.), strips any tree-hash suffix from COMPACTC_VERSION when
matching, and errors on unsupported patches.

Assisted-by: Claude:claude-opus-4-8
Signed-off-by: Oscar Bailey <79094698+ozgb@users.noreply.github.com>

Author: ozgb

changes/toolkit/changed/toolkit-js-compact-patch-version-dispatch.md

@@ -0,0 +1,27 @@
+#toolkit #compactc
+# Dispatch toolkit-js compact variants on the full patch version
+
+toolkit-js now selects its `@midnight-ntwrk/compact-js*` variant on the full
+`<major>.<minor>.<patch>` compactc version instead of truncating to
+`<major>.<minor>`. A compactc patch can ship a contract format that expects a
+different `compact-js` patch, so the previous "compact-js is patch-stable within a
+minor line" assumption no longer holds.
+
+The variant workspaces are renamed accordingly:
+- `compact-0.29/` → `compact-0.29.0/` (compact-js 2.4.3)
+- `compact-0.30/` → `compact-0.30.0/` (compact-js 2.5.0)
+- `compact-0.31/` → `compact-0.31.0/` (compact-js 2.5.1)
+
+`resolveCompactcVersion` now keeps the leading `<major>.<minor>.<patch>` and drops
+any trailing build/tree-hash suffix (e.g. `0.31.0-6587676a9bb2`, the form the dev
+shell exports from the root `COMPACTC_VERSION` file). An unsupported patch such as
+`0.31.1` now errors loudly rather than silently mapping to the minor line.
+
+`SUPPORTED_COMPACTC_VERSIONS`, the root `package.json` dependencies, each variant's
+package name, the regenerated `package-lock.json`, the `test-all-compactc.sh`
+comments, and the README maintenance docs all use the full-patch naming. The
+`compact-*` workspace glob and `node-toolkit-compact-*` build filter pick the
+renamed workspaces up automatically.
+
+PR:
+Issue:

util/toolkit-js/README.md

@@ -226,26 +226,28 @@ transitively, a matching `@midnight-ntwrk/compact-runtime`). To let one toolkit
 different `compactc` versions, each supported version has its own sibling workspace that pins that line:
 
 ```
-compact-0.29/   → @midnight-ntwrk/compact-js* 2.4.3
-compact-0.30/   → @midnight-ntwrk/compact-js* 2.5.0
-compact-0.31/   → @midnight-ntwrk/compact-js* 2.5.1
+compact-0.29.0/   → @midnight-ntwrk/compact-js* 2.4.3
+compact-0.30.0/   → @midnight-ntwrk/compact-js* 2.5.0
+compact-0.31.0/   → @midnight-ntwrk/compact-js* 2.5.1
 ```
 
-The root package depends on every variant (`@midnight-ntwrk/node-toolkit-compact-<major>.<minor>`). At runtime,
-`src/compactc-resolver.ts` reads `COMPACTC_VERSION`, picks the matching variant, and installs a module-resolution
-hook that redirects **every** `@midnight-ntwrk/compact-js*` / `@midnight-ntwrk/compact-runtime` import — including
-the transitive ones reached while a `contract.config.ts` is loaded — to that variant's pinned copy. `src/bin.ts`
-(the CLI) and `test/setup-compactc-resolver.ts` (the tests) both use this single resolver, so tests exercise the
-same dispatch as production.
+The root package depends on every variant (`@midnight-ntwrk/node-toolkit-compact-<major>.<minor>.<patch>`). At
+runtime, `src/compactc-resolver.ts` reads `COMPACTC_VERSION`, picks the matching variant, and installs a
+module-resolution hook that redirects **every** `@midnight-ntwrk/compact-js*` / `@midnight-ntwrk/compact-runtime`
+import — including the transitive ones reached while a `contract.config.ts` is loaded — to that variant's pinned
+copy. `src/bin.ts` (the CLI) and `test/setup-compactc-resolver.ts` (the tests) both use this single resolver, so
+tests exercise the same dispatch as production.
 
-`COMPACTC_VERSION` accepts either `<major>.<minor>` or the full `<major>.<minor>.<patch>` form; dispatch is on
-`<major>.<minor>` only, since `compact-js` is patch-stable within a minor line.
+Dispatch is on the full `<major>.<minor>.<patch>` version, since a `compactc` patch can ship a contract format
+that expects a different `@midnight-ntwrk/compact-js` patch. `COMPACTC_VERSION` may also carry a trailing
+build/tree-hash suffix (e.g. `0.31.0-6587676a9bb2`, the form stored in the root `COMPACTC_VERSION` file); only the
+leading `<major>.<minor>.<patch>` is matched.
 
 ### Adding support for a new `compactc` version
 
-1. **Create the variant workspace.** Copy an existing one, e.g. `cp -r compact-0.31 compact-<major>.<minor>`.
+1. **Create the variant workspace.** Copy an existing one, e.g. `cp -r compact-0.31.0 compact-<major>.<minor>.<patch>`.
    In its `package.json`:
-   - set `"name"` to `@midnight-ntwrk/node-toolkit-compact-<major>.<minor>`;
+   - set `"name"` to `@midnight-ntwrk/node-toolkit-compact-<major>.<minor>.<patch>`;
    - pin `@midnight-ntwrk/compact-js`, `@midnight-ntwrk/compact-js-command`, and `@midnight-ntwrk/compact-js-node`
      to the line that targets the new `compactc`;
    - align the `@effect/*` versions (`@effect/cli`, `@effect/platform-node`) with what that `compact-js` line
@@ -259,8 +261,8 @@ same dispatch as production.
    default baked into the resolver.
 
 3. **Depend on the variant** from the root `package.json` `dependencies`
-   (`"@midnight-ntwrk/node-toolkit-compact-<major>.<minor>": "^0.1.0"`). The `compact-*` workspaces glob picks it
-   up automatically.
+   (`"@midnight-ntwrk/node-toolkit-compact-<major>.<minor>.<patch>": "^0.1.0"`). The `compact-*` workspaces glob
+   picks it up automatically.
 
 4. **Add the concrete patch version** to `DEFAULT_VERSIONS` in `scripts/test-all-compactc.sh`.
 
@@ -272,7 +274,7 @@ same dispatch as production.
    ```
 
 To drop an old version, reverse these steps: remove it from `SUPPORTED_COMPACTC_VERSIONS`, the root dependency,
-and the test script, then delete the `compact-<major>.<minor>/` workspace.
+and the test script, then delete the `compact-<major>.<minor>.<patch>/` workspace.
 
 > [!IMPORTANT]
 > The CLI option surface can change between `compactc`/`compact-js-command` versions. For example, the global

util/toolkit-js/compact-0.29/package.json …l/toolkit-js/compact-0.29.0/package.jsonutil/toolkit-js/compact-0.29/package.json renamed to util/toolkit-js/compact-0.29.0/package.json util/toolkit-js/compact-0.29/package.json renamed to util/toolkit-js/compact-0.29.0/package.json

@@ -1,5 +1,5 @@
 {
-  "name": "@midnight-ntwrk/node-toolkit-compact-0.29",
+  "name": "@midnight-ntwrk/node-toolkit-compact-0.29.0",
   "version": "0.1.0",
   "license": "Apache-2.0",
   "description": "Interface gateway between Rust `midnight-node-toolkit` and TS `@midnight-ntwrk` packages",

util/toolkit-js/compact-0.29/src/index.ts …l/toolkit-js/compact-0.29.0/src/index.tsutil/toolkit-js/compact-0.29/src/index.ts renamed to util/toolkit-js/compact-0.29.0/src/index.ts util/toolkit-js/compact-0.29/src/index.ts renamed to util/toolkit-js/compact-0.29.0/src/index.ts

@@ -1,5 +1,5 @@
 {
-  "name": "@midnight-ntwrk/node-toolkit-compact-0.30",
+  "name": "@midnight-ntwrk/node-toolkit-compact-0.30.0",
   "version": "0.1.0",
   "license": "Apache-2.0",
   "description": "Interface gateway between Rust `midnight-node-toolkit` and TS `@midnight-ntwrk` packages",

…il/toolkit-js/compact-0.29/tsconfig.json …/toolkit-js/compact-0.29.0/tsconfig.jsonutil/toolkit-js/compact-0.29/tsconfig.json renamed to util/toolkit-js/compact-0.29.0/tsconfig.json util/toolkit-js/compact-0.29/tsconfig.json renamed to util/toolkit-js/compact-0.29.0/tsconfig.json

@@ -1,5 +1,5 @@
 {
-  "name": "@midnight-ntwrk/node-toolkit-compact-0.31",
+  "name": "@midnight-ntwrk/node-toolkit-compact-0.31.0",
   "version": "0.1.0",
   "license": "Apache-2.0",
   "description": "Interface gateway between Rust `midnight-node-toolkit` and TS `@midnight-ntwrk` packages",