@mutmutco/pi-plugin 4.6.43 → 4.6.45

package/package.json

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

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

@@ -1,7 +1,7 @@
 {
   ".github/workflows/agent-pr.yml": {
-    "blob": "a99d0be49e66423dfbafb9db6273a6b841752972",
-    "reason": "train-only markers around the release-align replay and its comment, stripped for single-track repos (#10076); the #7717 note says it applies only on repos with a release train (#10071); guarded paths, permissions and operator responsibilities unchanged"
+    "blob": "228f2f3289b187e47c91d88c8582c7d856708a3b",
+    "reason": "train-only markers around the release-align replay, its comment and the scripts/next-version.mjs org-owned entry, stripped for single-track repos (#10076, #10085); the #7717 note says it applies only on repos with a release train (#10071); guarded paths for train repos, permissions and operator responsibilities unchanged"
   },
   "scripts/next-version.mjs": {
     "blob": "7faba0bb3ee48074702da48d149657820d74de1a",

package/skills/org-guide/references/design.md

@@ -164,8 +164,11 @@ Craft essentials every agent applies (owner, 2026-10-25, #8839):
   it serves `<pack-dir>` on `127.0.0.1`, measures each named board per width and theme, runs
   `impeccable detect --json` over the board files and writes `check.json`. `--boards` takes one
   comma-separated list (an unquoted shell glob passes only its first match); the server serves only
-  files directly inside `<pack-dir>`; and the run always exits 2 because rhythm and alignment stay
-  unmeasured, so it is not a full kit pass on its own. Boards that load `/kit/kit.css` and
+  files directly inside `<pack-dir>`; BRP rhythm and sibling alignment are measured against the kit
+  space scale read live from the page's `:root` `--space-*` / `--mm-space-*` tokens (kit 4px fallback
+  steps when a board defines none), so off-scale padding/gap/sibling-margin values and 1–3px sibling
+  edge near-misses are named in `check.json` `detail.rhythm` / `detail.align` and fail the run
+  (exit 0 clean, 2 with faults — no standing caveat). Boards that load `/kit/kit.css` and
   `/kit/kit.js` are canvas boards: use `review.mjs <folder> --no-open`, which serves the kit beside
   each board on `127.0.0.1` and runs live-DOM `impeccable detect` per board.
   `artifacts/review/kit-assets.mjs`, `review.mjs`'s kit and board serving, and
@@ -306,7 +309,10 @@ requests like this should follow this structure, not prose guide."
      Option C, each its own full-resolution `1440x900` live HTML board in one MM Artifact A/B canvas
      (Part 3 rules: content-only `Ctrl + Mousewheel` zoom, 1:1 or side-by-side live comparison). Serve
      the verified canvas on the live loopback HTTP review server without opening a browser from the
-     seat, so the owner's `Send answers` posts straight back to `POST /answers`. Once review passes,
+     seat, so the owner's `Send answers` posts straight back to `POST /answers`. Set `artifact.json`
+     `review: { issue, requester }` first: without it the page still opens, but shows the owner a red
+     routing alert and answers reach only the serving session. Confirm no routing warning renders
+     before sending the URL. Once review passes,
      send the orchestrator only the review URL and issue number, and keep the server running through
      Stage 2; the orchestrator opens it on the owner's screen (#8987, relay wording). Never open a
      `--standalone` `file://` export (`Download answers.json`) for an