@mutmutco/pi-plugin 4.6.34 → 4.6.35

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mutmutco/pi-plugin",
-  "version": "4.6.34",
+  "version": "4.6.35",
   "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: