@mutmutco/claude-plugin 3.131.0 → 3.132.0

package/.claude-plugin/plugin.json

@@ -1,7 +1,8 @@
 {
   "name": "mmi",
   "displayName": "MMI",
-  "version": "3.131.0",
+  "version": "3.132.0",
+  "mmiCompat": "3.x",
   "description": "MMI workflow skills and org gates delivery.",
   "author": {
     "name": "MMI Future",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mutmutco/claude-plugin",
-  "version": "3.131.0",
+  "version": "3.132.0",
   "description": "MMI workflow skills and org gates delivery.",
   "author": {
     "name": "MMI Future",
@@ -13,7 +13,6 @@
   },
   "files": [
     ".claude-plugin/plugin.json",
-    ".pi-plugin/package.json",
     "skills",
     "hooks",
     "scripts",

package/skills/mmi/SKILL.md

@@ -53,16 +53,13 @@ Still run it in the foreground and wait. The lock stops corruption, not confusio
 that reports "skipped — lock busy" has healed nothing, and an agent that does not read that line will
 carry on believing its tooling was fixed.
 
-`doctor --no-repo-writes` heals a stale npm global or a stale/unresolved plugin install (the **env**
-half of the interactive doctor, #3485/#3975) — it never touches the repo working tree. When it prints
+`doctor --no-repo-writes` heals a stale/unresolved plugin install (the **env** half of the interactive
+doctor, #3485/#3975) — it never touches the repo working tree. When it prints
 `↻ Updating mmi tooling, one moment…`, relay that before waiting; when it prints `↻ MMI tooling
 updated — …`, relay the reload/restart guidance.
 
 What the env half heals:
 
-- a behind npm global → `npm install -g @mutmutco/cli@<released version>`, pinned, never the floating
-  `@latest`, which npm can resolve off a cached packument and reinstall the stale version right after a
-  publish (#3422). Effective on the next invocation.
 - a stale or unresolved Claude plugin → `claude plugin marketplace remove mmi` → `… remove mutmutco` →
   `claude plugin marketplace add mutmutco/MMI-Hub` → `claude plugin install mmi@mutmutco`. A fresh
   reinstall, never `claude plugin update`, which nests into itself past MAX_PATH on Windows and wipes the
@@ -72,6 +69,10 @@ What the env half heals:
   docs/doctor-contract.md § Guarded cache prune): never the running/newest/installed version, a cache a
   live session holds is named "still held" and never forced.
 
+What it does **not** do since #4954: install anything. A behind npm global is REPORTED (the `mmi-cli`
+row names `npm install -g @mutmutco/cli@<released>`) and the `fleet` row reads the scheduled
+`mmi-updater`'s journal — that reconciler is the single writer of CLI and plugin versions.
+
 - **Fast path** → `whoami` then `board read`; no foreground doctor.
 - **Hard setup signal** → run `doctor --no-repo-writes`, relay `↻` lines, then retry `board read` when appropriate.
 - **`mmi-cli: command not found`** → plugin PATH provisioning has not applied, or the standalone CLI is not installed.

package/skills/mmi-doctor/SKILL.md

@@ -13,10 +13,15 @@ One command. Run it when a session opens messy or before a handoff.
 mmi-cli doctor
 ```
 
-By default this **heals and cleans** (MMI-Hub#3975): CLI/plugin/marketplace 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 doctor — use `mmi-cli vault secrets diff` when you need a catalog gap check.
+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
+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).
 
 ## Flags
 

package/skills/release/SKILL.md

@@ -125,7 +125,7 @@ git rev-list --count origin/main..origin/development
 
 Before local gates or `release --apply`, ensure the repo-local / PATH `mmi-cli` matches the released train
 path — a stale checkout (e.g. 2.32.0 while 2.32.4 is released) fails release gates with opaque errors.
-Self-heal in place without repo writes (heals run by default since #3975; the flag suppresses only
+Read the gap without repo writes (plugin/env repairs run by default since #3975; the flag suppresses only
 mutations of the working tree you are about to release from):
 ```bash
 mmi-cli doctor --no-repo-writes
@@ -136,10 +136,11 @@ inverse is also true: a run can exit **0** while printing ✗ lines (report-only
 direction is a gate. Read the rows.
 
 - **Blocking:** a red `mmi-cli` / `Claude plugin` version line, or a reported `minClientVersion` gap.
-  `--no-repo-writes` does not block the env heals — the step above self-updates the npm global CLI
-  (#3272) and reinstalls the plugin (#3282), suppressing only repo-file writes — so the re-run should clear
-  it. If a gap persists, fix it — `mmi-cli doctor`, or `npm install -g @mutmutco/cli` — before
-  continuing. Do **not** proceed to Step 0b while the installed CLI is behind the Hub's `minClientVersion`.
+  **Doctor does not update the CLI (#4954).** The scheduled `mmi-updater` owns npm installs now; doctor
+  REPORTS the lag (the `mmi-cli` row) and reads the reconciler's journal (the `fleet` row). So the remedy
+  here is the explicit install below — `npm install -g @mutmutco/cli@<released>` — not a doctor re-run.
+  `--no-repo-writes` still heals the plugin install (#3282), suppressing only repo-file writes. Do **not**
+  proceed to Step 0b while the installed CLI is behind the Hub's `minClientVersion`.
 - **Not blocking:** every other red check is hygiene, not a train gate. Stale branches and scratch heal with
   a plain `mmi-cli doctor` (after the release); `plugin cache` needs a different verb,
   `mmi-cli plugin prune --apply` — saying doctor cleared it was wrong. Both still exit 1 until you run the

package/.pi-plugin/package.json

@@ -1,23 +0,0 @@
-{
-  "name": "mmi",
-  "version": "3.131.0",
-  "description": "MMI workflow skills and org gates delivery.",
-  "author": {
-    "name": "MMI Future",
-    "email": "69869555+jervaise@users.noreply.github.com"
-  },
-  "homepage": "https://github.com/mutmutco/MMI-Hub",
-  "private": true,
-  "type": "module",
-  "keywords": [
-    "mmi",
-    "mutmutco",
-    "pi-package",
-    "jervcode"
-  ],
-  "pi": {
-    "skills": [
-      "../skills"
-    ]
-  }
-}