@mutmutco/codex-plugin 3.132.1 → 3.133.0

package/.codex-plugin/plugin.json

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

package/package.json

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

package/skills/epic/SKILL.md

@@ -31,6 +31,12 @@ Keep the parent as the umbrella — do not close it until the last child merges.
 
 ## Step 1 — draft the batch file
 
+Before drafting, inspect the umbrella's existing children:
+
+```bash
+mmi-cli oracle issue children <owner/repo#N>        # each child: number/title/state/repo/boardStatus/linkedPrs
+```
+
 Write a JSON array (one object per child) to a scratch path under `tmp/`. Each row:
 
 ```json
@@ -54,7 +60,9 @@ Write a JSON array (one object per child) to a scratch path under `tmp/`. Each r
   the prefix. A top-level `--surface <value>` may supply the default for every applicable row.
 
 The batch **pre-validates every row before creating any** — one bad row fails the whole set with an
-aggregate error, so you fix all of them once. Get the user's go on the drafted set before writing.
+aggregate error, so you fix all of them once. It warns when a row title closely matches an existing open
+child of the same parent; inspect that warning before creating a duplicate. Get the user's go on the drafted
+set before writing.
 
 ## Step 2 — create the children
 

package/skills/mmi-doctor/SKILL.md

@@ -15,13 +15,16 @@ mmi-cli doctor
 
 By default this **heals and cleans** (MMI-Hub#3975): plugin env repairs, managed `.gitignore`,
 merged-branch / dead-worktree reap (including deferred IDE-locked removals), light board mechanical
-fixes, docs-index working-tree heal, and related full-lane checks. Secrets stay **out** of default
+fixes, docs-index working-tree heal, detection that names hung `mmi-hook` / `hook-run` processes
+older than the session bound, and related full-lane checks. Secrets stay **out** of default
 doctor — use `mmi-cli vault secrets diff` when you need a catalog gap check.
 
 Doctor does **not** update the CLI or the host plugins (MMI-Hub#4954). The scheduled `mmi-updater`
 reconciler is the single writer of those versions; doctor only REPORTS — the `mmi-cli` row names the
 version gap and the `npm install -g @mutmutco/cli@<released>` that closes it, and the `fleet` row reads
-the reconciler's journal (installed / expected / drift per surface).
+the reconciler's journal (installed / expected / drift per surface). Its plugin-heal/update pass
+covers every surface from any invocation surface — including Cursor's local-checkout row, not only
+the active surface.
 
 ## Flags
 

package/skills/release/SKILL.md

@@ -169,6 +169,11 @@ Warm the cache with a plain `npm ci` in the release checkout, then rerun the ide
 rollback the failed fold already ran makes the rerun clean. Never regenerate or rewrite the lockfile in
 response to a SIGTERM kill.
 
+**Repeated `EPERM` or `EBUSY` unlink errors during the fold's npm install on Windows are one race window,
+not a lockfile failure (#4982).** Rename `node_modules` aside once into a gitignored `tmp/` path, then rerun
+the identical train command. `npm ci` extracts into the now-empty tree and performs no unlinks; do not retry
+this workaround repeatedly.
+
 **Then check the version yourself — do not rely on doctor having printed a row (#3674).** "Read the rows"
 resolves to "proceed" when the row is *absent*, and doctor's version row is conditional. On 2026-07-27 this
 step reported healthy with no version line while the installed CLI was 3.70.0 against a released 3.71.0;