@mutmutco/pi-plugin 4.5.216 → 4.5.218

package/package.json

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

package/skills/bootstrap/seeds/suite-guide.template.md

@@ -36,7 +36,7 @@ The bible for the MM open design system; every agent doing UI, design or MM Arti
 Four owner decisions (2026-10-25T15:35:52Z):
 
 1. **Doc vs. app kit — add a Document Design System too.** Keep the MM-Work Atomic Design System (`3a5c79df-5274-40ad-a1b5-a75e67a74dac`) for MM-Work and module app UI (and as the fallback for now), and add a dedicated Document/Editorial Design System Artifact in Live Docs for reports, checklists, decks and client documents made by Junior or agents.
-2. **Where to save — local HTML for dev, Live Docs for shared.** Coding agents build local `.html` MM Artifacts for fast iteration. Interactive owner A/B reviews use the live loopback HTTP review server (`http://127.0.0.1:<port>/` with `Send answers`); seats send the orchestrator only the review URL and issue number, keep the server running until the owner answers, and never open the owner's browser (#8987, relay wording). Publish to Live Docs only for a shared deliverable, an A/B decision canvas or a Design System. Junior inside MM-Work saves directly to Live Docs.
+2. **Where to save — local HTML for dev, Live Docs for shared.** Coding agents build local `.html` MM Artifacts for fast iteration. Interactive owner A/B reviews use the live loopback HTTP review server (`http://127.0.0.1:<port>/` with `Send answers`); seats send the orchestrator only the review URL and issue number, keep the server running until the owner answers, and never open the owner's browser (#8987, relay wording). A kept-alive canvas review server must stay light (no dev/watch build pinning gigabytes); a seat whose canvas needs a heavy local server flags that to the orchestrator instead of holding the RAM silently, and stops it as soon as the owner has answered. Publish to Live Docs only for a shared deliverable, an A/B decision canvas or a Design System. Junior inside MM-Work saves directly to Live Docs.
 3. **Artifact shape — single HTML by default, Canvas for A/B.** A single self-contained HTML view for documents, checklists and single-screen work; a multi-board spatial Canvas only for A/B choices or `1440`/`1024`/`390` side-by-side comparisons.
 4. **Kit binding — Live Docs hosts kits; npm only for MM-Work.** Every Design System Artifact in Live Docs stores its tokens/CSS/components and `DESIGN.md` so any HTML artifact can bind to it (`kit: { id, version }`); only the MM-Work app design system is also exported as `@mutmutco/mmwork-ds`, because the MM-Work app and the 10 suite modules compile against it.
 
@@ -148,7 +148,7 @@ requests like this should follow this structure, not prose guide."
 
 UI and design verification uses `@mutmutco/mmwork-ds` (`mmwork-check-ui`) plus Impeccable on every design task: inspect the toolkit for applicable capabilities, work directly on the live app, and use our own MM Artifacts A/B canvas only when an owner design A/B choice is needed (approvals for keys, releases, deletions, data access or tooling go to the orchestrator in plain words, never on a canvas; Hub#8986). Functional journeys, where separately permitted, stay opt-in `workflow_dispatch`-only and never act as design checks.
 
-Front-load Impeccable before any UI or MM Artifact authoring: `impeccable context --target <path>`, `DESIGN.md` + the `design.json` sidecar in `.impeccable`, `.impeccable/config.json` (`hook.enabled: true`), `reference/craft-floor.md` + `reference/operate.md`, and `impeccable detect --json <target>`. Local/canvas MM Artifacts (`mm-artifact` v3 format) are checked with one command, `node artifacts/review/review.mjs <folder>`, which runs `check.mjs`, `check-ui.mjs` and `geometry.mjs`, pre-renders the board in `node:vm` (`ReactDOMServer.renderToStaticMarkup` into `#root`) and runs `impeccable detect --json` on that rendered HTML. Interactive owner A/B reviews use the live loopback HTTP review server (`http://127.0.0.1:<port>/`), where the owner presses `Send answers`; seats never open the owner's browser. Once review passes, send the orchestrator only the review URL and issue number, and keep the server running until the owner answers. The orchestrator opens it on the owner's screen (#8987, relay wording). `--standalone [<out.html>]` is only for offline HTML previews/exports and SSR pre-render verification, never for an interactive owner decision.
+Front-load Impeccable before any UI or MM Artifact authoring: `impeccable context --target <path>`, `DESIGN.md` + the `design.json` sidecar in `.impeccable`, `.impeccable/config.json` (`hook.enabled: true`), `reference/craft-floor.md` + `reference/operate.md`, and `impeccable detect --json <target>`. Local/canvas MM Artifacts (`mm-artifact` v3 format) are checked with one command, `node artifacts/review/review.mjs <folder>`, which runs `check.mjs`, `check-ui.mjs` and `geometry.mjs`, pre-renders the board in `node:vm` (`ReactDOMServer.renderToStaticMarkup` into `#root`) and runs `impeccable detect --json` on that rendered HTML. Interactive owner A/B reviews use the live loopback HTTP review server (`http://127.0.0.1:<port>/`), where the owner presses `Send answers`; seats never open the owner's browser. Once review passes, send the orchestrator only the review URL and issue number, and keep the server running until the owner answers. A kept-alive canvas review server must stay light (no dev/watch build pinning gigabytes); a seat whose canvas needs a heavy local server flags that to the orchestrator instead of holding the RAM silently, and stops it as soon as the owner has answered. The orchestrator opens it on the owner's screen (#8987, relay wording). `--standalone [<out.html>]` is only for offline HTML previews/exports and SSR pre-render verification, never for an interactive owner decision.
 
 Impeccable v4.7.0 (engine v0.1.16) workflow; CLI verbs and agent playbooks are distinct:
 

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

@@ -32,7 +32,13 @@ a universal test count. Run only the focused checks the repository policy permit
 substitute a broad local build or full suite. MMI worktrees install vitest under `cli/node_modules`,
 not at the root, so never run `npx vitest` there (#8967): invoke the worktree-local runner directly,
 `node <worktree>/cli/node_modules/vitest/vitest.mjs run <suite>` (or `npm --prefix cli exec -- vitest run <suite>`),
-and run `.mjs` `node:test` suites with `node --test <file>`, never under vitest. Complete the documentation preflight below before pushing.
+and run `.mjs` `node:test` suites with `node --test <file>`, never under vitest. Run `mmi-cli tests policy`
+and every focused test from the assigned issue worktree whose session cwd selects it — policy receipts
+are recorded per worktree, so a receipt from another tree does not clear the guard; never cd-prefix into
+a lane root or sibling worktree (use `git -C` / `npm --prefix` instead, #3187). A historical main-based
+hotfix worktree without test-policy.json chains
+`mmi-cli tests policy --json --base origin/main --policy-ref <current origin/development commit> && <focused test>`
+in one command (#3243). Complete the documentation preflight below before pushing.
 Open a PR through `mmi-cli devops pr create` with a closing issue link, and land through
 `mmi-cli devops pr land`. Verify required checks, merge, issue closure, and cleanup before calling
 the implementation complete. A merged implementation is not a production release.
@@ -72,7 +78,10 @@ design work follows one harmonized **Front-Loaded Impeccable v4.7.0 + MM Artifac
   `Send answers` posts back to `POST /answers`; a seat must not open the owner's browser. An A/B is
   shown as the live canvas link, never as prose (#8987, relay wording). Once the canvas passes review,
   send the orchestrator only the review URL and issue number, and keep the server running until the
-  owner answers. The orchestrator opens it on the owner's screen. `--standalone [<out.html>]` is only
+  owner answers. A kept-alive canvas review server must stay light (no dev/watch build pinning
+  gigabytes); a seat whose canvas needs a heavy local server flags that to the orchestrator instead
+  of holding the RAM silently, and stops it as soon as the owner has answered. The orchestrator opens
+  it on the owner's screen. `--standalone [<out.html>]` is only
   for offline HTML previews/exports and SSR pre-render verification, never for an interactive owner
   decision.
   **Headless seat rule:** `--open` is review.mjs-only; never pass `--open` to `vite`, and never use it from a seat to open the owner's browser for an A/B review.
@@ -95,7 +104,7 @@ How the five pillars fit together (owner, 2026-10-25):
 Four owner decisions (2026-10-25T15:35:52Z):
 
 1. **Doc vs. app kit — add a Document Design System too.** Keep the MM-Work Atomic Design System (`3a5c79df-5274-40ad-a1b5-a75e67a74dac`) for MM-Work and module app UI (and as the fallback for now), and add a dedicated Document/Editorial Design System Artifact in Live Docs for reports, checklists, decks and client documents made by Junior or agents.
-2. **Where to save — local HTML for dev, Live Docs for shared.** Coding agents build local `.html` MM Artifacts for fast iteration. For interactive owner A/B reviews, serve the canvas on the live loopback HTTP review server (`http://127.0.0.1:<port>/` with `Send answers`) without opening the owner's browser; relay the URL and issue number to the orchestrator and keep the server running until the owner answers (#8987, relay wording). Use `node artifacts/review/review.mjs <folder> --standalone [<out.html>]` for offline HTML previews/exports or SSR pre-render verification. Publish to Live Docs only for a shared deliverable, an A/B decision canvas or a Design System. Junior inside MM-Work saves directly to Live Docs.
+2. **Where to save — local HTML for dev, Live Docs for shared.** Coding agents build local `.html` MM Artifacts for fast iteration. For interactive owner A/B reviews, serve the canvas on the live loopback HTTP review server (`http://127.0.0.1:<port>/` with `Send answers`) without opening the owner's browser; relay the URL and issue number to the orchestrator and keep the server running until the owner answers (#8987, relay wording). A kept-alive canvas review server must stay light (no dev/watch build pinning gigabytes); a seat whose canvas needs a heavy local server flags that to the orchestrator instead of holding the RAM silently, and stops it as soon as the owner has answered. Use `node artifacts/review/review.mjs <folder> --standalone [<out.html>]` for offline HTML previews/exports or SSR pre-render verification. Publish to Live Docs only for a shared deliverable, an A/B decision canvas or a Design System. Junior inside MM-Work saves directly to Live Docs.
 3. **Artifact shape — single HTML by default, Canvas for A/B.** A single self-contained HTML view for documents, checklists and single-screen work; a multi-board spatial Canvas only for A/B choices or `1440`/`1024`/`390` side-by-side comparisons.
 4. **Kit binding — Live Docs hosts kits; npm only for MM-Work.** Every Design System Artifact in Live Docs stores its tokens/CSS/components and `DESIGN.md` so any HTML artifact can bind to it (`kit: { id, version }`); only the MM-Work app design system is also exported as `@mutmutco/mmwork-ds`, because the MM-Work app and the 10 suite modules compile against it.