@mutmutco/kilo-plugin 3.80.0 → 3.82.0

package/package.json

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

package/skills/hotfix/SKILL.md

@@ -34,7 +34,7 @@ and CLI health before starting:
 
 ```bash
 mmi-cli org access role <owner/repo> --json
-mmi-cli doctor --apply --no-repo-writes
+mmi-cli doctor --no-repo-writes
 ```
 
 Stop on a red authority or CLI-version result. The worktree must be clean; move scratch into `tmp/` or

package/skills/mmi/SKILL.md

@@ -52,7 +52,7 @@ preflight that reports "skipped — lock busy" has healed nothing, and an agent
 line will carry on believing its tooling was fixed.
 
 `doctor --preflight` detects a stale npm global or a stale/unresolved plugin install and runs the **env**
-half of the interactive `doctor --apply` self-heal (#3485) — it never touches the repo working tree, and
+half of the interactive doctor self-heal (#3485/#3975) — it never touches the repo working tree, and
 never pays the train-branch sync or the gc sweep. It still belongs off the critical board path unless it
 has proof it must heal. When it prints `↻ Updating mmi tooling, one moment…`, relay that before waiting;
 when it prints `↻ MMI tooling updated — …`, relay the reload/restart guidance.

package/skills/rcand/SKILL.md

@@ -30,7 +30,7 @@ never proceed unverified.
 **CLI freshness (#2562):** check the running CLI is current BEFORE step 1 — `mmi-cli rcand --apply` refuses
 a stale CLI at its own step 0 (pre-mutation), but the manual steps below mutate local state earlier, so a
 stale CLI discovered late reads as a mid-train abort. When another train just published a new CLI (e.g. a
-Hub release), run `mmi-cli doctor --apply --no-repo-writes` first. A stale-CLI refusal itself changes
+Hub release), run `mmi-cli doctor --no-repo-writes` first. A stale-CLI refusal itself changes
 nothing; after updating, the rerun resumes any partial train state safely.
 
 **Run from the checkout that already has `development` — never a fresh isolated worktree (#2770).** This is
@@ -51,7 +51,7 @@ git rev-list --count origin/rc..origin/development
 ```
 Dirty → stop. Count `0` → stop ("nothing to promote"). `>0` → capture the commit list for the report.
 
-> Verifying CLI/plugin-health before a train? Use `mmi-cli doctor --apply --no-repo-writes`: it runs the
+> Verifying CLI/plugin-health before a train? Use `mmi-cli doctor --no-repo-writes`: it runs the
 > env/plugin repairs but never mutates the working tree, so a pending org-managed `.gitignore` repair is
 > reported with its follow-up command instead of dirtying the product checkout right before promotion.
 > Apply that follow-up after the train.

package/skills/release/SKILL.md

@@ -93,28 +93,25 @@ 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:
+Self-heal in place without repo writes (heals run by default since #3975; the flag suppresses only
+mutations of the working tree you are about to release from):
 ```bash
-mmi-cli doctor --apply --no-repo-writes
+mmi-cli doctor --no-repo-writes
 ```
 **Read the checks, not the exit code.** `doctor` exits non-zero on any failed check it could have healed —
 not just a version gap — so a red exit here does not by itself mean the train is blocked (#2962). The
-inverse is also true since #3485: a run can exit **0** while printing ✗ lines, because three rows
-(`worktree roots`, `schedules`, `docs-audit`) are ruled report-only — real faults the design deliberately
-declines to gate on, since their remedy is a human review or lives in the owning repo. Neither direction
-is a gate. Read the rows.
+inverse is also true: a run can exit **0** while printing ✗ lines (report-only rows, #3485). Neither
+direction is a gate. Read the rows.
 
-- **Blocking:** a red `mmi-cli` / `Claude plugin` version line, or a reported `minClientVersion` gap. Since
-  #3485 `--no-repo-writes` no longer blocks the env heals — the step above self-updates the npm global CLI
+- **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 --apply`, or `npm install -g @mutmutco/cli` — before
+  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`.
 - **Not blocking:** every other red check is hygiene, not a train gate. Stale branches and scratch heal with
-  `mmi-cli doctor --apply`; `plugin cache` needs a different verb, `mmi-cli plugin prune --apply` — saying
-  `doctor --apply` cleared it was wrong. All three still exit 1 until you run the right verb. The three
-  report-only rows (`worktree roots`, `schedules`, `docs-audit`) print ✗ without moving the exit code
-  since #3485 — not because no verb exists, but because the design refuses to gate on a human review or
-  on a fault owned by another repo. Read them, then proceed.
+  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
+  right verb. Read them, then proceed.
 
 Treating doctor's exit code as the gate halts a healthy train on cosmetic drift — or, worse, teaches an
 operator to ignore doctor's exit code entirely.