@mutmutco/codex-plugin 4.5.217 → 4.5.218

package/.codex-plugin/plugin.json

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

package/cli/dist/main.cjs

@@ -27056,10 +27056,10 @@ var rollout_plan_default = {
     note: "The v4.0.0 stamp happens at cut time (D6e #4463); until then the candidate is the origin/development head artifacts (built cli/dist + npm pack), identity proven by dist content hash (D6a)."
   },
   baseline: {
-    version: "4.5.217",
-    tag: "v4.5.217",
-    commit: "6888824b66e5",
-    npm: "@mutmutco/cli@4.5.217"
+    version: "4.5.218",
+    tag: "v4.5.218",
+    commit: "3847ee21a247",
+    npm: "@mutmutco/cli@4.5.218"
   },
   exitCriterion: "fleet-n-of-n",
   hubOnlyShortcut: "forbidden",
@@ -27076,14 +27076,14 @@ var rollout_plan_default = {
           repo: "mutmutco/mmi-hub",
           role: "canary",
           schedule: "train",
-          v3Target: "v4.5.217"
+          v3Target: "v4.5.218"
         }
       ],
       rollbackTrigger: "Any red inside the post-contract soak window: `devops train gate` FAIL attributable to the v4 doors, Hub endpoint health probe failure, a pre-v4 client admitted instead of receiving actionable HTTP 426, or npm consumer install/doctor failure on the v4-only dist.",
       rollback: {
         independent: true,
-        mechanism: "npm dist-tag latest -> 4.5.217 and redeploy the Hub Lambda from tag v4.5.217 (6888824b66e5); installed clients repair via `mmi-cli doctor`. No other cohort is touched.",
-        v3Target: "v4.5.217 (@mutmutco/cli@4.5.217, tag commit 6888824b66e5 \u2014 last known-good release carrying the repo-index v4-only contract)"
+        mechanism: "npm dist-tag latest -> 4.5.218 and redeploy the Hub Lambda from tag v4.5.218 (3847ee21a247); installed clients repair via `mmi-cli doctor`. No other cohort is touched.",
+        v3Target: "v4.5.218 (@mutmutco/cli@4.5.218, tag commit 3847ee21a247 \u2014 last known-good release carrying the repo-index v4-only contract)"
       }
     },
     {

package/cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mutmutco/cli",
-  "version": "4.5.217",
+  "version": "4.5.218",
   "description": "MMI Future CLI — the org dev toolbox and shared cross-IDE engine for every registry-declared MMI coding surface.",
   "type": "module",
   "license": "UNLICENSED",

package/package.json

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

package/skills/org-guide/references/work-and-releases.md

@@ -32,7 +32,13 @@ a universal test count. Run only the focused checks the repository policy permit
 substitute a broad local build or full suite. MMI worktrees install vitest under `cli/node_modules`,
 not at the root, so never run `npx vitest` there (#8967): invoke the worktree-local runner directly,
 `node <worktree>/cli/node_modules/vitest/vitest.mjs run <suite>` (or `npm --prefix cli exec -- vitest run <suite>`),
-and run `.mjs` `node:test` suites with `node --test <file>`, never under vitest. Complete the documentation preflight below before pushing.
+and run `.mjs` `node:test` suites with `node --test <file>`, never under vitest. Run `mmi-cli tests policy`
+and every focused test from the assigned issue worktree whose session cwd selects it — policy receipts
+are recorded per worktree, so a receipt from another tree does not clear the guard; never cd-prefix into
+a lane root or sibling worktree (use `git -C` / `npm --prefix` instead, #3187). A historical main-based
+hotfix worktree without test-policy.json chains
+`mmi-cli tests policy --json --base origin/main --policy-ref <current origin/development commit> && <focused test>`
+in one command (#3243). Complete the documentation preflight below before pushing.
 Open a PR through `mmi-cli devops pr create` with a closing issue link, and land through
 `mmi-cli devops pr land`. Verify required checks, merge, issue closure, and cleanup before calling
 the implementation complete. A merged implementation is not a production release.