@mutmutco/kilo-plugin 3.127.0 → 3.129.0

package/package.json

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

package/skills/mmi-doctor/SKILL.md

@@ -46,6 +46,12 @@ that surface alone (e.g. a secrets catalog review, or an interactive `board doct
 
 - `/mmi-doctor` is the hygiene pass; `/resume` is the lighter read-only session open.
 - Prefer one doctor run over hand-editing board items, gitignore blocks, or marketplace pins.
+- Doctor / `worktree list --stale` / `worktree gc` name the clone they audited. A green
+  "no leaks" / "nothing to clean" is refused when another primary checkout of the same remotes
+  exists, or when the jerv lease ledger points at another `mmi-worktrees` root (#4900 / #4897).
+  Run hygiene from the canonical `E:\AI Projects\Mutatis Mutandis\` primary — not from
+  `C:\Users\ssari\Projects\`. Treat a non-empty jerv worktree-lease ledger as a leak even if
+  this clone's `git worktree list` is empty.
 
 ## Retro — one check before you finish
 Before your final report, answer one question honestly: did **this skill's own instructions** misfire

package/skills/release/SKILL.md

@@ -70,7 +70,8 @@ mean "unverified", never an authority verdict:**
 
 Then
 preconditions: clean tree; full-track repos run from `rc` (or from `development` with `--dev`), while
-direct-track repos run from `development`.
+direct-track repos run from `development`. Ordinary `/release` also needs `MMI_BUMP_INTENT=minor|major`
+exported in the apply environment (patch is `/hotfix`); the train does not infer an open cycle.
 
 **Run from the checkout that already has that branch — never a fresh isolated worktree (#2770).** This is
 a shared-branch train operation (merge/tag/push against origin's protected `main`/`rc`), not an isolated
@@ -547,15 +548,12 @@ deploy run + URL + **green/red** · branch-alignment note · npm publish run + C
 
 - PATCH-level releases are `/hotfix` only (a hotfix always skips rc — it cherry-picks `development → main`
   directly); planned releases are MINOR or MAJOR. Never force-push `main`.
-- **`MMI_BUMP_INTENT=major|minor|patch` is required for direct-track's `next-version.mjs cycle`** (Step 2)
-  — it selects the increment for an ordinary release and is never inferred; absence is a hard refusal
-  (`MMI_BUMP_INTENT must be one of major|minor|patch`), not a default. **Export it for the whole run, not
-  just the tag line:** `mmi-cli devops release --apply` resolves the intent itself and refuses mid-train
-  with the same message, so a value passed only as a one-off prefix on the `next-version.mjs` command
-  leaves the apply to fail after the preflight has already passed. The same holds for
-  `mmi-cli devops rcand --apply`. This is a different knob from
-  `MMI_RELEASE_VERSION` below: `MMI_BUMP_INTENT` picks the increment, `MMI_RELEASE_VERSION` overrides the
-  computed version entirely and is for the exceptional case only.
+- **`MMI_BUMP_INTENT=major|minor` is required in the apply environment for ordinary `/release`** (patch is
+  `/hotfix`). Absence is a hard refusal — the train never infers an open cycle. Export it for the whole
+  run, not a one-off prefix on `next-version.mjs cycle`: `mmi-cli devops release --apply` (and `rcand
+  --apply`) resolve intent themselves and refuse mid-train if the env is missing. `MMI_RELEASE_VERSION`
+  below is a different knob: it overrides the computed version; it does not replace the intent export
+  unless you set that exact-target env instead.
 - **`--dev` (full-track only):** releases `development → main` skipping rc, with the same fold/tag/Release/
   deploy machinery plus the post-release rc retirement and rc alignment. Refuses (fail closed) when
   `origin/rc` carries commits not in `development`; on direct-track repos it's a no-op (they already
@@ -563,7 +561,8 @@ deploy run + URL + **green/red** · branch-alignment note · npm publish run + C
 - **MAJOR / exact-target release:** to ship a version the tag math can't derive (a MAJOR like `2.0.0`, or
   skipping a version already on npm), product repos export `MMI_RELEASE_VERSION=X.Y.Z` for **both** `/rcand`
   and `/release`; MMI-Hub exports it for `/release` only. Steps 1b/2 then fold and tag exactly that
-  version. Unset, the train ships the open cycle.
+  version. Unset, the train uses the declared `MMI_BUMP_INTENT` increment — it does not infer an open
+  cycle, and apply fail-closes if that env is also missing.
 
 ## Retro — one check before you finish
 Before your final report, answer one question honestly: did **this skill's own instructions** misfire

package/skills/resume/SKILL.md

@@ -46,9 +46,12 @@ workspace identity the next step must use (for example `mutmutco/MMC-ZuberShade`
 mmi-cli oracle next --repo <repo reported by status>
 ```
 
-Pass the repository from `status` explicitly; never reconstruct it by changing case or punctuation.
-`next` recommends the single most actionable claimable board item (unblocked, priority-ranked) and prints
-the exact `mmi-cli oracle board claim <n>` to take it. Offer it; do not claim on the user's behalf without a go.
+Never the retired flat `mmi-cli next` — Wave 3 (#4316) removed that alias; a `flat 'next' alias was
+removed` exit means follow the printed `oracle next` path (and `mmi-cli plugin heal` when
+`doctor --self` says the plugin is behind). Pass the repository from `status` explicitly; never
+reconstruct it by changing case or punctuation. `next` recommends the single most actionable
+claimable board item (unblocked, priority-ranked) and prints the exact
+`mmi-cli oracle board claim <n>` to take it. Offer it; do not claim on the user's behalf without a go.
 For the full board partition (yours / claimable / taken) run `/mmi`.
 
 ## Step 3 — render, then stop
@@ -84,3 +87,4 @@ snapshot that named the wrong branch.) If yes, file **one** lesson and move on;
 (hard cap: one per run). It lands on the Hub board (deduped) and is fixed only via a reviewed PR — never
 edit the skill live; the retro is advisory, so if the call fails, note it and continue:
 `mmi-cli learning skill-lesson --skill resume --title "<what misfired>" --body "<what; evidence; proposed amendment>"`
+(never the retired flat `mmi-cli skill-lesson`).

package/skills/worktree/SKILL.md

@@ -133,11 +133,13 @@ mmi-cli oracle next               # the next actionable item
   `.worktrees/` are not the MMI path.
 - Multiple independent items → one worktree each, run in parallel, one PR per item (`/mmi` Leverage).
 - Never land to a protected/release branch here — that is `/rcand` and `/release`.
-- **Open the primary checkout in Cursor before land/gc hygiene (#4489).** If Cursor’s agent workspace is
-  still rooted at the slice worktree, `worktree land` / `worktree gc --apply` / doctor gc **refuse** to
-  delete that directory (and queue deferred removal) so the session is not orphaned. Optional explicit
-  contract: `export MMI_ACTIVE_WORKSPACE_ROOT="<Cursor workspace folder>"`. After switching Cursor to the
-  primary checkout, `mmi-cli worktree gc sweep-deferred` finishes cleanup.
+- **Keep Cursor on the primary checkout (#4489 / #4901).** Edit the worktree without
+  `move_agent_to_root` into the slice — moving the workspace root pins the session so land/gc
+  refuse forever. If Cursor’s agent workspace is still rooted at the slice, `worktree land` /
+  `worktree gc --apply` / doctor gc **refuse** to delete that directory (and queue deferred
+  removal). On a Cursor agent host, land/gc fail closed when the active root cannot be resolved:
+  open the primary first, or set `MMI_ACTIVE_WORKSPACE_ROOT` to the primary path. After Cursor is
+  on the primary, `mmi-cli worktree gc sweep-deferred` finishes cleanup.
 
 ## Retro — one check before you finish
 Before your final report, answer one question honestly: did **this skill's own instructions** misfire