@mutmutco/pi-plugin 4.2.1 → 4.2.3

package/package.json

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

package/scripts/env-write-lint.mjs

@@ -46,6 +46,15 @@ const PS_WRITE_RE = new RegExp(
 // `copy`/`move` are the cmd.exe spellings AND the default PowerShell aliases for Copy-Item/Move-Item, so
 // `copy .env.example .env` reached disk past every analyzer (pre-existing since #2663; found by the #3563
 // cross-vendor check, openai-sol). `xcopy`/`robocopy` are the other two Windows spellings.
+
+// #5820: segment separators include NEWLINES. Without them a multi-line script — a heredoc body, an
+// SSH `bash -s` payload — collapses into ONE segment, and the copy/git/touch scans below then pair a
+// verb on one line with "the last path token in the segment" from an unrelated line further down:
+// `cp a b` on line 1 plus a later line ending in an env-shaped token was denied as env_write_copy,
+// neither line a write (found applying the documented jerv-central procedure, runbooks/box-ops.md).
+// Adding \r\n strictly TIGHTENS the scans — every real create form still matches on its own line.
+const SEGMENT_RE = /(?:\|\||&&|[;&|\r\n])/;
+
 const COPY_VERBS = /^(?:cp|mv|install|ln|rsync|copy|move|xcopy|robocopy|Copy-Item|Move-Item)$/i;
 
 /** Inspect one command for a real-.env CREATE. Returns { block, reason, reasonId } or null (clean). */
@@ -87,7 +96,7 @@ export function analyze({ toolName, command } = {}) {
   // `bash -lc "cp …"` all put a wrapper first. And the destination is not always last — PowerShell takes
   // `-Destination`, and `cp <file> <dir>/` names the directory while the basename comes from the source
   // (all four ALLOWED before this; cross-vendor check, openai-sol).
-  for (const raw of command.split(/(?:\|\||&&|[;&|])/)) {
+  for (const raw of command.split(SEGMENT_RE)) {
     const seg = raw.trim();
     if (!seg) continue;
     const tokens = seg.split(/\s+/).filter(Boolean);
@@ -107,7 +116,7 @@ export function analyze({ toolName, command } = {}) {
   }
 
   // `git checkout <ref> -- <path>` / `git restore --source <ref> <path>` materialise a file from history.
-  for (const raw of command.split(/(?:\|\||&&|[;&|])/)) {
+  for (const raw of command.split(SEGMENT_RE)) {
     const tokens = raw.trim().split(/\s+/).filter(Boolean);
     const gitAt = tokens.findIndex((t) => (t.replace(/\\/g, '/').split('/').pop() ?? '') === 'git');
     if (gitAt === -1 || !/^(?:checkout|restore)$/i.test(tokens[gitAt + 1] ?? '')) continue;
@@ -115,7 +124,7 @@ export function analyze({ toolName, command } = {}) {
   }
 
   // touch: any non-flag arg that is a real .env token creates the file.
-  for (const raw of command.split(/(?:\|\||&&|[;&|])/)) {
+  for (const raw of command.split(SEGMENT_RE)) {
     const seg = raw.trim();
     if (!seg) continue;
     const tokens = seg.split(/\s+/).filter(Boolean);

package/skills/release/SKILL.md

@@ -469,6 +469,17 @@ stray tag locally and on origin, confirm `next-version` would re-derive the *sam
 then re-run a **single** `mmi-cli devops release --apply`. If the newer skip-version already published
 cleanly, keep it and only remove the broken older Release/tag.
 
+**Resuming a resumable partial state? The recovery form is `--resume --watch --json`, and nothing
+else (#5815).** `--resume` and `--apply` are **mutually exclusive** and the CLI refuses the pair:
+`--apply cuts the NEXT version, --resume finishes the immutable tag already on origin`
+(`cli/src/index.ts`, the #3851 guard). A continuation that reaches for
+`--resume --apply --watch` is asking the train to mint a new version while finishing an old one —
+it refuses before any mutation, so nothing is lost, but the operator has spent a turn on a form that
+can never run. `--apply` belongs to a **new** release cut, never to recovery.
+```bash
+mmi-cli devops release --resume --watch --json --repo <owner/repo>
+```
+
 ## Step 4 — GitHub Release + start prod deploy (non-blocking)
 
 For `tenant-container` repos, publish the GitHub Release and dispatch the central tenant deploy.
@@ -662,6 +673,23 @@ without a leading `v`.
 Run that verify from a checkout **at the tag** (`main` right after the release merge, `git checkout
 "vX.Y.0"`, or a worktree at the tag) — verify checks the working tree and refuses any other commit once
 the tag exists, so a stale `development`/`rc` checkout can't masquerade as a broken release.
+
+**Build the tag checkout before verifying, or it refuses deterministically (#5814).** `verify` (without
+`--skip-npm-view`) runs a live `npm pack` per public surface, and `npm pack` refuses a package whose
+declared `bin` target is absent — e.g. `updater publishes bin jerv-hub -> dist/index.cjs, which npm pack
+does not ship — run npm run build`. Whether that bites depends on the repo: a build output that is
+**tracked** (MMI-Hub commits `updater/dist/index.cjs`) is present in a clean tag checkout, one that is
+**gitignored** is not, and a fresh clone has no `node_modules` either way. So provision the tag worktree
+first, and check the declared bin targets rather than assuming:
+```bash
+git worktree add "$PROOF" "vX.Y.0"      # $PROOF outside the repo — see the scratch note below
+cd "$PROOF" && npm ci && npm run build  # build only if a declared bin target is missing from the checkout
+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.
 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.