@mutmutco/kilo-plugin 3.139.0 → 3.139.2

package/skills/mmi/SKILL.md

@@ -282,7 +282,7 @@ something else* paths.)
      answers from the dev for each — draft where you can, ask where you can't (the template form is
      interactive and won't drive in a non-TTY agent shell, so collect the fields, then create directly).
   3. **Submit via `mmi-cli oracle issue create`** — the canonical create path. Before filing, read the live
-     `issue create` entry from `mmi-cli commands --json`; flags change, and a missing documented flag means
+     command contract from `mmi-cli explain oracle issue create --json`; flags change, and a missing documented flag means
      the installed CLI is stale until a fresh local build proves otherwise. It maps `--type` to the label,
      `--priority` sets the board Priority **field** (never a `priority:*` label — #416), and `--surface`
      supplies the repository's required single surface label. It always prints `{number,url}` JSON. Never
@@ -326,9 +326,8 @@ Pick up to two, in priority order:
 1. **Split + fan out** — a single item plainly too large for one PR (body is multi-part, an umbrella or
    epic). Offer to slice it into child issues. (First because it *creates* the items the rest act on.)
 2. **Batch** — 2+ claimable items that are one coherent unit (shared title-prefix family, same subsystem)
-   **and** touch overlapping/adjacent paths. Coupled → one worktree, **one PR**.
-3. **Parallel** — 2+ items that are mutually independent and touch **disjoint paths**. Independent → N
-   worktrees, **one PR each**, run concurrently.
+   **and** touch overlapping/adjacent paths. Coupled → **one PR**.
+3. **Parallel** — 2+ items that are mutually independent and touch **disjoint paths**. Independent → **one PR each**, run concurrently.
 4. **Background** — a single long-running item (broad refactor, large build/sweep). Kick it off in the
    background so the dev isn't blocked.
 
@@ -356,27 +355,20 @@ Offer lines — one line each, no UI, no "(Recommended)", phrased as available l
 - **Background** — `#22 looks long-running — I can take it in the background so you're not blocked.`
 - **Split** — `#60 looks large — I can slice it into child issues and fan them out, if you want.`
 
-Act-paths run only on the dev's explicit go. Every path branches from `development` and lands by PR.
-PR land cleans up at the branch boundary (`git worktree remove` + `git worktree prune`); batch/session
-work should keep all related sequential issues in the same branch/PR where possible instead of merging and
-destroying the worktree after each issue:
+Act-paths run only on the dev's explicit go. MMI coordinates board and PR outcomes, while the host owns
+workspace mechanics:
 
-- **PR metadata:** read the live `pr create` or `pr edit` entry from `mmi-cli commands --json` before the
+- **PR metadata:** read `mmi-cli explain devops pr create --json` or `mmi-cli explain devops pr edit --json` before the
   write. For multiline Markdown, materialize a temporary UTF-8 body file, pass its real path with
   `--body-file <path>`, and remove it after the write succeeds. Do not pipe the body to `--body-file -`;
   host prose guards require the materialized-file path.
-- **Batch:** one worktree, claim each item (the Step 5 claim loop), make the coupled edits, open **one** PR
+- **Batch:** claim each item (the Step 5 claim loop), make the coupled edits, and open **one** PR
   (`Closes #…, #…`). When an issue must stay open (HOLD/prep), never write `Does not close #N` — GitHub
   still closes it; use `Part of #N` / `Refs #N` / `leaves #N open` only (JC#495).
-- **Session/sequential:** multiple related same-repo items handled one after another in the same session
-  reuse the active worktree until the session or execution group ends; do not churn one worktree per
-  issue unless a branch/PR boundary, true parallelism, or explicit user ask requires it.
-- **Parallel:** one isolated worktree per item, cut from `development`, run concurrently, **one PR per
-  item**. If two would touch the same file, serialize them or fold into a batch instead.
-- **Background:** run off the hot path (a background task or CI job); poll with `/loop`, test with `/stage`
-  if useful; it still lands via its own worktree + PR. Bound it — never block silently.
-- **Stage/worktree:** a local `/stage` is tied to the worktree that started it. Stop/destroy and recreate
-  it before moving to another worktree, or warn first when intent is unclear.
+- **Parallel:** run independent work concurrently, **one PR per item**. If two would touch the same file,
+  serialize them or fold them into a batch instead.
+- **Background:** run off the hot path (a background task or CI job); poll with `/loop` if useful. Bound it
+  — never block silently.
 - **Split:** keep the original as the umbrella; file each child as a **native sub-issue** of it with
   `mmi-cli oracle issue create --parent <umbrella-ref> …` (or `mmi-cli oracle issue link-child <umbrella> <child>` for a
   child that already exists). The parent then renders a sub-issue checklist with each child's state and the

package/skills/mmi-doctor/SKILL.md

@@ -14,10 +14,10 @@ mmi-cli doctor
 ```
 
 A plain run may repair machine-global plugin wiring and guarded caches, but **never mutates the
-repository** (#5023). It reports managed `.gitignore`, docs-index, board mechanics, merged branches,
-dead worktrees, and aged scratch. Run `mmi-cli doctor --apply` only when the operator explicitly wants
-that guarded full repository cleanup. Secrets stay out of doctor; use `mmi-cli vault secrets diff` for
-a catalog gap check.
+repository** (#5023). It reports managed `.gitignore`, docs-index, board mechanics, and aged scratch.
+Local workspace lifecycle is host-owned; doctor does not relocate or delete worktrees. Run
+`mmi-cli doctor --apply` only when the operator explicitly wants guarded repository maintenance. Secrets
+stay out of doctor; use `mmi-cli vault secrets diff` for a catalog gap check.
 
 Doctor does **not** converge CLI or host versions (MMI-Hub#4954). `mmi-hub update` is the single
 writer of those versions; doctor only reports lag and last-run journal evidence. `mmi-hub status`
@@ -43,22 +43,18 @@ Do **not** chain these as a `/mmi-doctor` substitute:
 mmi-cli doctor --self
 mmi-cli oracle board doctor
 mmi-cli vault secrets diff
-mmi-cli worktree gc
 ```
 
-Plain `mmi-cli doctor` covers safe tooling repair and diagnosis. Explicit `doctor --apply` covers the
-full guarded repository cleanup; reach for individual verbs only when you want one surface alone.
+Plain `mmi-cli doctor` covers safe tooling repair and diagnosis. Explicit `doctor --apply` covers
+repository maintenance; the host owns workspace cleanup. Reach for individual verbs only when you want
+one surface alone.
 
 ## Notes
 
 - `/mmi-doctor` is the hygiene pass; `/mmi-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.
+- The host owns workspace roots, cleanup, and any lease policy. Doctor diagnoses MMI tooling and does
+  not relocate or delete local worktrees.
 
 ## Retro — one check before you finish
 Before your final report, answer one question honestly: did **this skill's own instructions** misfire

package/skills/stage/SKILL.md

@@ -128,7 +128,7 @@ The stage URL, what's running (server + tools), the workspace path (`tmp/stage/`
 
 - `/stage` is local — no AWS, no deploy, no board or version effect. The one cloud exception is
   `--live`: an on-demand **dev** stage of your branch, gated to your IP at the Cloudflare edge (above).
-- `/stage-live` is not an org command: remote rc/live environments move only through `/rcand`, `/release`, and `/hotfix`.
+- Remote rc/live environments move only through `/rcand`, `/release`, and `/hotfix`.
 - Everything is gitignored; `/stage` never produces a tracked change.
 - **Playwright MCP output goes to `tmp/`**, never the repo root: if you drive the Playwright MCP server,
   pass `--output-dir tmp/playwright-mcp` (or point its output there). `.playwright-mcp/` is kept gitignored