@mutmutco/pi-plugin 4.5.210 → 4.5.211

package/package.json

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

package/skills/board/SKILL.md

@@ -21,6 +21,8 @@ accepts an incomplete board. The CLI partitions rows into **Yours**, **Free to c
 stamps (4 hours without work) hold nothing. Partition rules, stamp details and `--out` rationale:
 [reference.md](reference.md).
 
+Read single issues/PRs with `MMI_ACTOR=app mmi-cli devops read issue view <n> --repo <owner/repo> --json <fields>` (or `issue list`, `pr view`, `run view`) and filter the JSON locally: under the App pool, gh `--jq`/`-q`/`--template`/`--web` are refused.
+
 ## Step 2 — render it
 
 Plain markdown, never a fenced block. Flat `-` lists under bold heads, never `##` headings, never tables.
@@ -62,6 +64,8 @@ Follow printed owner rulings; record new ones with `mmi-cli oracle issue decisio
 
 With several task lanes in one session, pass `worktree: <the mmi-worktrees/<Repo>/<issue>-<slug> path jerv_worktree_create reported>` to `jerv_worktree_exec` / `jerv_worktree_land` every time; they refuse to guess (#5629).
 
+A fresh mmi worktree has no `.jerv/`: run `mkdir -p .jerv/tmp` before writing scratch files there (PR bodies, batches) or listing it.
+
 ## Step 5 — land one PR per batch
 
 No `--issues` or `--closes` flag; put `Closes #6395, #6396, #6397` in the **body**. After merge, board

package/skills/epic/SKILL.md

@@ -29,7 +29,7 @@ Inspect existing children first:
 mmi-cli oracle issue children <owner/repo#N>
 ```
 
-Write a JSON array, one object per child, to `.jerv/tmp/epic-<parentNumber>-children.json` (unique per epic; a leftover batch from another epic collides with the new rows):
+Write a JSON array, one object per child, to `.jerv/tmp/epic-<parentNumber>-children.json` (unique per epic; a leftover batch from another epic collides with the new rows). A fresh mmi worktree has no `.jerv/`; run `mkdir -p .jerv/tmp` first:
 
 ```json
 [

package/skills/hotfix/SKILL.md

@@ -29,6 +29,8 @@ mmi-cli devops train doctor --lane hotfix --heal --json
 
 Parse stdout only; never `2>&1`. `ready` false → stop and quote every blocker's `code` and `remedy`; an unread origin is never green. Findings carry `code`, `severity`, `source`, `remedy`, `anchor`.
 
+Piping `mmi-cli devops api get` into a JSON parser: a refusal exits 1 with empty stdout, so guard both: `out=$(MMI_ACTOR=app mmi-cli devops api get <path>) && [ -n "$out" ] && printf '%s' "$out" | node -e '…'`. One job's metadata: read the allowlisted `repos/{owner}/{repo}/actions/runs/{id}/jobs` and filter `jobs[]` by `id`; `actions/jobs/{id}` is refused (only its `/logs`, with `--out`).
+
 ## Apply
 
 From the primary checkout.

package/skills/org-guide/references/work-and-releases.md

@@ -19,6 +19,10 @@ Under the App pool,
 `--jq`/`-q`/`--template`/`--web` are refused: use
 `MMI_ACTOR=app mmi-cli devops read issue view <id> --repo <owner/repo> --json comments`
 (or `pr`/`run view` with their fields); filter returned JSON locally.
+For run logs, never native `gh run view --log`/`--log-failed`: use
+`MMI_ACTOR=app mmi-cli devops read run log <runId> --repo <owner/repo> [--failed | --job <name>] [--tail N]`.
+A refused command writes no output, so a `> file` redirect leaves it empty or missing: read the
+refusal, then rerun the typed form.
 
 Read the issue, implementation, callers, and repository policy before editing.
 Run `mmi-cli tests policy --base <comparison-base>` to determine required checks against your target