@mutmutco/pi-plugin 3.139.0 → 3.139.2

package/skills/bootstrap/seeds/manifest.json

@@ -11,6 +11,7 @@
     { "target": ".github/workflows/agent-pr.yml", "source": "self", "ownership": "org", "classes": ["deployable"], "waivers": { "jerv-jervcode": "pins this workflow's EXACT step shapes in its own scripts/workflow-boundary-core.mjs — a literal repositories: Jerv-JervCode token scope, and whole-step equality for the surface and verdict legs. #4040 widened the org seed to the same hardened boundary (pull_request_target off the trusted base, an immutable BASE..HEAD compare with a file-count equality wall, a per-repo App token scope, and a certified-head merge), so the two now agree on substance. They cannot agree on bytes: a seed serving 16 repos resolves its token scope and its required contexts at run time, which exact-step equality rejects by construction. The waiver is permanent by design, not a deferral — lifting it would mean weakening the strictest repo to match a fleet file." } },
     { "target": ".github/rulesets/mmi-product-required-checks.json", "source": "seed:mmi-product-required-checks.template.json", "ownership": "org", "classes": ["deployable"] },
     { "target": ".gitignore", "source": "managed-block", "ownership": "org", "classes": ["deployable", "content"] },
+    { "target": ".gitattributes", "source": "seed:gitattributes.template", "ownership": "repo", "classes": ["deployable", "content"] },
     { "target": "README.md", "source": "seed:README.template.md", "ownership": "repo", "classes": ["deployable", "content"], "managedBlock": { "source": "seed:readme-mmi-developer-environment.block.md", "begin": "<!-- mmi-developer-environment:start -->", "end": "<!-- mmi-developer-environment:end -->" } },
     { "target": "architecture.md", "source": "seed:architecture.template.md", "ownership": "repo", "classes": ["deployable", "content"] },
     { "target": "docs/decisions/README.md", "source": "seed:decisions-readme.template.md", "ownership": "repo", "classes": ["deployable", "content"] },

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

package/skills/worktree/SKILL.md

@@ -1,151 +0,0 @@
----
-name: worktree
-description: Orchestrate a worktree from create to landed PR, tied to board status.
----
-
-**Host-native invocation:** Claude `/mmi:worktree` · Codex `$mmi:worktree` · jervcode/Kimi `/skill:worktree` · Kilo `skill` tool. A backticked `/name` in this doc names the matching workflow (this skill or a sibling), not a literal command.
-
-# /worktree — create → work → land
-
-Drive an item through an isolated worktree: cut it from latest `development`, claim the board item, do the
-work, open and land the PR, and clean up — with the board moving automatically at each boundary. One
-worktree per session; everything under `../mmi-worktrees/` is ephemeral and sweepable.
-
-## Step 1 — create + provision
-
-```bash
-mmi-cli worktree create <owner/repo#N> --claim --from origin/development
-```
-
-`worktree create` cuts the branch from `origin/development` (fetched first) and provisions it: installs
-deps (`npm ci`) and copies local-only config (`.claude/settings.local.json`) a fresh checkout lacks. Use
-`--from <ref>` for a non-default base, `--path <path>` to override the location. An existing worktree that
-lost its deps re-provisions with `mmi-cli worktree setup [path]` (the SessionStart hook fires this
-automatically).
-
-The issue-ref form derives `<issue-number>-<short-slug>`, assigns the item, and moves it to In Progress.
-
-`worktree create` also leases the tree to the **creating session** (#4328). A later `jerv-cli lane submit
---dir` (or any governed seat) refuses an already-held host lease and will not commandeer it. Before handing
-the tree to a governed seat, release that lease first — safe once the session's own edits in that tree are
-committed and pushed: `jerv-cli lease close --ref <worktree path>` (closes every lease on that ref; no id
-lookup needed). To inspect what's held before closing, `jerv-cli lease list` shows id, ref, and owner.
-
-## Step 2 — claim + work
-
-Work in the provisioned worktree. Exercise the change with `/stage` (a local stage is bound to the worktree that
-started it — stop it before switching worktrees). Sequential related items in one session reuse the active
-worktree; do not churn one worktree per issue unless a true parallel or PR boundary needs it.
-
-## Step 3 — open the PR
-
-Push the branch and open the PR against `development`. The board moves to In Review automatically on PR
-open — never move it by hand.
-
-```bash
-git push origin <branch>:<branch>              # explicit feature refspec — see below
-mmi-cli devops pr create --title "<title>" --body-file .jerv/PR_BODY.md --base development
-mmi-cli devops pr checks-wait <PR-number>              # wait for required CI to go green
-```
-
-Write the PR body under `.jerv/` (#4405), never at the worktree root. `.jerv/` is the agent-artifact
-prefix `worktree land` treats as removable; a stray untracked `PR_BODY.md` anywhere else classifies the
-tree as `untracked-files` and Step 4 then skips cleanup entirely.
-
-The push must be the explicit `<branch>:<branch>` refspec (the branch Step 1 derived, e.g.
-`git push origin 3795-my-slice:3795-my-slice`). The #1660 protected-push gate denies the
-`HEAD`/remote-only form (`git push -u origin HEAD`) — its target cannot be proven safe. And never
-share the push with staging or commit verbs in one compound command: the deny applies to the whole
-command, so a refused `git add … && git commit … && git push …` chain discards the add and commit
-with it. Stage, commit, and push as separate commands.
-
-If the branch adds, removes, or renames any `docs/` file, `pr create` refuses with a stale
-`docs/index.md` (#4092) — run `mmi-cli oracle docs index --write`, commit `docs/index.md`, and push again
-before retrying.
-
-## Step 4 — land + clean up
-
-Under standing go (green CI, CI-gated PR) land to `development`. **Invoke `mmi-cli devops pr land` from the
-primary checkout** (or any cwd that is not the PR worktree) (#4549). Landing while cwd is still inside
-the worktree that cleanup removes can merge successfully and still exit 1 with
-`cleanupError: … Unable to read current working directory` — post-merge `gh`/`git` follow-ups then have
-no readable cwd even when removal itself chdir'd away (#4140).
-
-```bash
-cd <primary-checkout>   # e.g. the main MMI-Hub clone — not the slice worktree
-mmi-cli devops pr land <PR-number>
-```
-
-`pr land` waits for checks, squash-merges, and does the full cleanup at the branch boundary: removes the
-worktree, deletes the merged branch (local + origin), and prunes tracking refs. A worktree the IDE has
-locked is queued and retried by `mmi-cli worktree gc sweep-deferred`. Self-authored merges need an explicit
-per-session merge grant — ask early if you don't have one.
-
-**`not-attempted (untracked-files)` (#3500 / #4405):** the usual cause of a merged PR that left its
-worktree behind. Any untracked path outside `.jerv/` — a hand-written `PR_BODY.md`, notes, a scratch
-script — makes removal refuse, because an unadded file can be real work. Delete or move the file, then
-re-run cleanup **from inside the worktree** (`worktree land` has no `--path`; it acts on the tree you
-are standing in):
-
-```bash
-mmi-cli worktree land --apply
-```
-
-**Cwd-safe removal (#4140):** `worktree land --apply` (what `pr land` runs) releases the process cwd to
-the primary checkout before deleting the tree (#1444/#2747) so Windows `rmdir` is not `EBUSY`. That does
-**not** replace the agent rule above: still start `pr land` from the primary checkout (#4549). Prefer
-primary cwd also when running `worktree land` manually outside `pr land`. If removal still fails (IDE
-lock, antivirus), the deferred sweep retries from a safe cwd.
-
-**No main lineage on a squashable development PR (#4365 / #4371):** never `git merge -s ours` (or otherwise
-merge) a main-parented port commit into a development PR that will squash. Squash folds second-parent
-trailers — including foreign `Closes #N` — into the development squash body, closes the wrong issues, and
-trips the closing-keyword land guard. Keep the cherry-pick / main-clean source on a separate branch or ref;
-land only development-tree changes on the development PR. To record a pushed main-clean SHA for a later
-`/hotfix --from` without polluting squash parents, prefer a marker-only commit on the development branch
-that references that SHA in the message — do not pull the main commit into the squashable parent list.
-This does not weaken the `#3167` merge floor on `/hotfix` and `/release` (never squash a tagged commit;
-alignment / roll-forward stays a true merge).
-
-**Stay-open phrasing (JC#495 / #3718):** GitHub's closing-keyword parser is negation-blind. `Does not
-close #N` still contains `close #N` and **closes the issue** on merge/squash (measured: Jerv-JervCode
-PR #493 closed #487). When an issue must stay open, never put `close`/`closes`/`fix`/`resolve` + `#N`
-in the PR body, commit message, or merge message — use `Part of #N`, `Refs #N`, or `leaves #N open` only.
-`mmi-cli devops pr create` rewrites common negated phrases; `pr land` / `pr merge` still refuse any remaining
-negation-blind close. `--force` only when those targets should actually close.
-
-If a PR already inherited closed-issue `Closes` keywords from that anti-pattern and `pr land` / `pr merge`
-refuses, land with `--force` only when those inherited targets are already closed — prefer preventing the
-pollution above over relying on `--force`.
-
-## Step 5 — record + next
-
-Record durable decisions on the issue or PR, then check the board again:
-
-```bash
-mmi-cli oracle wave status        # remaining worktrees, open PRs, local stages at a glance
-mmi-cli oracle next               # the next actionable item
-```
-
-## Notes
-
-- Cut worktrees only at `../mmi-worktrees/<RepoName>/<branch>` (#3471) — generic helpers that force `.claude/worktrees/` or
-  `.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`.
-- **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
-this run — ambiguous wording, a misleading message, or an environment failure it should have warned
-about? (Process only — never the user's code or task; e.g. a create that branched from a stale base, or a
-land that left a worktree behind.) If yes, file **one** lesson and move on; a clean run is silent (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 worktree --title "<what misfired>" --body "<what; evidence; proposed amendment>"`