@mutmutco/codex-plugin 4.3.4 → 4.3.5

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "mmi",
-  "version": "4.3.4",
+  "version": "4.3.5",
   "mmiCompat": "4.x",
   "description": "MMI workflow skills and org gates delivery.",
   "author": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mutmutco/codex-plugin",
-  "version": "4.3.4",
+  "version": "4.3.5",
   "description": "MMI workflow skills and org gates delivery.",
   "author": {
     "name": "MMI Future",

package/skills/release/SKILL.md

@@ -812,7 +812,10 @@ node scripts/release-distribution.mjs verify "X.Y.0"
 Removing that proof tree afterwards: `npm ci` writes `node_modules`, which `git status --porcelain`
 never shows and which makes `git worktree remove` refuse with `Directory not empty`. Delete
 `node_modules` first, then remove the worktree. On Windows a global install made from a worktree leaves
-a junction there, so delete the directory rather than following it.
+a junction there, so delete the directory rather than following it. In a guarded agent shell pass the
+**literal absolute** proof path to `git worktree remove` — the checkout guard refuses a variable-held
+target (`Blocked git worktree remove with an unanalyzable variable-held target`, #2492 / #6060); only an
+interactive shell may pass `"$PROOF"`.
 Release-blocking for Hub tooling changes: every public artifact must match the registry version and BOM
 identity. Manual fallback if CI can't publish: `node scripts/release-distribution.mjs publish "X.Y.0"`
 from a machine with npm auth.
@@ -851,7 +854,12 @@ cross-environment shape for surfaces with no publish-time staged payload, not a
 Off the publish environment, either:
 - fall back to an **unpacked-content** proof — download the registry tarball (`npm pack <pkg>@X.Y.Z`
   from the registry, or `npm view … dist.tarball`), `npm pack` from the tag checkout, unpack both, and
-  compare the trees (do not alarm on SSRI alone). Hub host-plugin npm surfaces stage the canonical
+  compare the trees (do not alarm on SSRI alone). On Windows unpack with the native
+  `%SystemRoot%\System32\tar.exe` named explicitly — a bare `tar.exe` can resolve to Git's GNU tar
+  through PATH, which reads a drive-letter path as a remote host (`Cannot connect to C: resolve
+  failed`, #6059) — and run `npm pack` from the package directory (`cd` there; no positional path
+  and no `--pack-destination` under a path with spaces), since routing npm through `cmd.exe /c`
+  reparses quoted paths (#6058). Hub host-plugin npm surfaces stage the canonical
   `skills/` tree and declared hook-policy `scripts/` into the package at publish time via
   `assembleDeclaredPayloads` (#5471); those paths are gitignored and absent from a plain tag checkout,
   so a local `npm pack` without staging cannot reproduce them and an empty `diff -r` is an unreachable