@mutmutco/pi-plugin 4.6.34 → 4.6.36

package/package.json

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

package/skills/board/SKILL.md

@@ -20,12 +20,16 @@ One call; `--flat` gives one array of rows to iterate. A routine read already ex
 items, so no status post-filter is needed. The detailed form (`--json` without `--flat`) carries `viewer`,
 `repo` and the project title; use its `primary` for this repo and `secondary` for other repos on the
 Project. Without `--flat`, `board read --json` returns an object
-`{project, viewer, repo, primary, secondary, warnings, partial}` whose `primary` and `secondary` are bucket
-objects `{userOwned, claimable, taken, unownedInFlight}` of item arrays (no top-level `items` array), so filter
-a bucket (e.g. `report.primary.claimable`) or pass `--json --flat`, never `(j.items||j).filter`. Never sniff
-for the list (`j.items ?? j.rows ?? j`, `Object.values`, any generic "find the list" wrapper): it throws
-`items is not iterable` before any row is read. For a number|status|claim|title projection across non-Done
-rows, run `mmi-cli oracle board read --json --flat --out .jerv/tmp/board.json` and filter that array locally.
+`{project, viewer, repo, primary, secondary, items, warnings, partial}` whose `primary` and `secondary` are bucket
+objects `{userOwned, claimable, taken, unownedInFlight}` of item arrays, and whose top-level `items` (#9974) is
+the flat row array — the same rows `--flat` prints — so a number|status|title projection can iterate
+`report.items` without a second read. Filter a bucket (`report.primary.claimable`) when ownership context
+matters, or `report.items` / `--json --flat` for a projection. Never sniff
+for the list (`j.items ?? j.rows ?? j`, `Object.values`, any generic "find the list" wrapper): `j.rows` is not a
+key, and on an older report it threw
+`items is not iterable` before any row was read. For a number|status|claim|title projection across non-Done
+rows, read `report.items` or run `mmi-cli oracle board read --json --flat --out .jerv/tmp/board.json` and filter
+that array locally.
 `--flat` rows are `{ref,number,title,status,assignees,labels,bucket,claim,openPullRequests}` (`claim` is the
 parsed mmi-claim evidence object, null when unclaimed; `openPullRequests` lists the OPEN PRs whose
 closing-issue body links name the item — on the full JSON object that list lives at `report.pullRequests`,

package/skills/board/reference.md

@@ -21,9 +21,12 @@ rows to iterate. A routine read already excludes Done and closed items, so no st
 One call. The detailed form (`--json` without `--flat`) carries `viewer`, `repo` and the project title — do not spend extra calls on
 `gh api user` or `gh repo view`. Use `primary` for this repo and `secondary` for other repos on the same
 Project. Without `--flat`, `board read --json` returns an object
-`{project, viewer, repo, primary, secondary, warnings, partial}` whose `primary` and `secondary` are bucket
-objects `{userOwned, claimable, taken, unownedInFlight}` of item arrays (no top-level `items` array), so filter
-a bucket (e.g. `report.primary.claimable`) or pass `--json --flat`, never `(j.items||j).filter`. Partial reads
+`{project, viewer, repo, primary, secondary, items, warnings, partial}` whose `primary` and `secondary` are bucket
+objects `{userOwned, claimable, taken, unownedInFlight}` of item arrays, and whose top-level `items` (#9974) holds
+the flat rows — exactly what `--flat` prints — so iterate `report.items` instead of spending a second read.
+Filter a bucket (`report.primary.claimable`) when ownership context matters. Never sniff for the list
+(`j.items ?? j.rows ?? j` is only coincidentally safe now, `Object.values` is not): `j.rows` is not a key.
+Partial reads
 exit nonzero; pass `--allow-partial` only when the dev accepts an incomplete board.
 
 Partition, as the CLI computes it:

package/skills/bootstrap/seeds/readme-mmi-developer-environment.block.md

@@ -2,4 +2,7 @@
 ## MMI developer environment
 
 Use the [canonical MMI developer-environment guide](https://github.com/mutmutco/MMI-Hub/blob/main/docs/Architecture/agentic-dev-environment.md) for shared setup and daily agent work.
+
+Daily loop: `mmi-cli oracle issue create` → `mmi-cli oracle board claim <n>` (stamps the mmi-claim lease) → `mmi-cli devops pr create` → `mmi-cli devops pr land <pr>`.
+Any org member with repository write (developer) or repository admin (project admin) can run it, with no vault access; release trains stay org-owner only.
 <!-- mmi-developer-environment:end -->

package/skills/bootstrap/seeds/runbook-unaffected.json

@@ -6,5 +6,9 @@
   "scripts/next-version.mjs": {
     "blob": "2c1985b59edc779695479559074e7654c1574a11",
     "reason": "comment-only note that rc/release modes are unused in dev-only MM suite repos (#8282), no runtime or operator behaviour change"
+  },
+  "README.md": {
+    "blob": "768c5e35cdb48849c77bce6b334658adefe6a5d8",
+    "reason": "the developer-environment seed block now states the concrete mmi-cli loop (issue create, board claim, PR create, PR land) and who may run it — the README propagation is intended (#9987); no runbook step changes"
   }
 }

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

@@ -13,6 +13,23 @@ our self-hosted runners, dispatched by an org owner, never on a workstation (#91
 A 503 `github-rate-limited` answer means the org App's hourly GitHub allowance is used up. It is
 not a denial: wait for the reset time it names, then retry.
 
+## Developer and project-admin access
+
+A developer is an org member with GitHub write on a product repository. A project admin is that
+repository's admin. Both run the full loop with mmi-cli and need no MMI-Hub vault access:
+
+```sh
+mmi-cli oracle issue create --title "<title>" --body-file <path>   # files and attaches the board card
+mmi-cli oracle board claim <n>                                     # stamps the mmi-claim lease
+mmi-cli devops pr create --title "<title>" --base development
+mmi-cli devops pr land <pr-number>
+```
+
+Board writes (attach, claim stamp, status move) gate on org owner, repo admin or repository write, so
+these roles pass. Where the GitHub App route is absent the writes go as the person's own GitHub login
+(one note says so); an agent host with the App route writes as the App. MMI-Hub's own merges and all
+release trains stay org-owner only.
+
 Start with `mmi-cli onboard` and the [board skill](../../board/SKILL.md).
 Reading or discussing the board is read-only until the developer authorizes work.
 Claim approved work with `mmi-cli oracle board claim <issue>`, then prepare an isolated task