@mutmutco/pi-plugin 4.5.208 → 4.5.209

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/package.json +1 -1
  2. package/skills/bootstrap/seeds/suite-guide.template.md +10 -4
  3. package/skills/org-guide/references/work-and-releases.md +17 -8
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mutmutco/pi-plugin",
3
- "version": "4.5.208",
3
+ "version": "4.5.209",
4
4
  "description": "MMI workflow skills and org gates delivery.",
5
5
  "author": {
6
6
  "name": "MMI Future",
package/skills/bootstrap/seeds/suite-guide.template.md CHANGED
@@ -36,7 +36,7 @@ The bible for the MM open design system; every agent doing UI, design or MM Arti
36
36
  Four owner decisions (2026-10-25T15:35:52Z):
37
37
 
38
38
  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.
39
- 2. **Where to save — local HTML for dev, Live Docs for shared.** Coding agents build and open local `.html` MM Artifacts (`node artifacts/review/review.mjs <folder> --standalone [<out.html>] [--open]`) for fast iteration, and 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.
39
+ 2. **Where to save — local HTML for dev, Live Docs for shared.** Coding agents build and open local `.html` MM Artifacts for fast iteration — interactive owner A/B reviews with `node artifacts/review/review.mjs <folder> --open` on the live loopback HTTP review server (`http://127.0.0.1:<port>/` with `Send answers`), and offline HTML previews/exports or SSR pre-render verification (`impeccable detect --json`) with `node artifacts/review/review.mjs <folder> --standalone [<out.html>]` — and 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.
40
40
  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.
41
41
  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.
42
42
 
@@ -114,11 +114,17 @@ requests like this should follow this structure, not prose guide."
114
114
  Option C, each its own full-resolution `1440x900` live HTML board in one MM Artifact A/B canvas
115
115
  (Part 3 rules: content-only `Ctrl + Mousewheel` zoom, 1:1 or side-by-side live comparison). Open
116
116
  the verified canvas in the browser automatically with
117
- `node artifacts/review/review.mjs <folder> --standalone --open`. Spawn a dedicated, fresh
117
+ `node artifacts/review/review.mjs <folder> --open`, which serves it over the live loopback HTTP
118
+ review server (`http://127.0.0.1:<port>/`) so the owner's `Send answers` posts straight back to
119
+ `POST /answers`. Never open a `--standalone` `file://` export (`Download answers.json`) for an
120
+ interactive owner A/B decision: `--standalone [<out.html>]` is only for offline previews/exports
121
+ and SSR detector checks. Spawn a dedicated, fresh
118
122
  `designer` subagent for each distinct design task (item 3); never reuse a busy designer seat.
119
123
  - **Stage 2 — the owner chooses visually on the A/B canvas.** Wait while the owner inspects the
120
124
  live HTML alternatives, zooms into details and picks the preferred design or asks for
121
- adjustments. Record the canvas choice ID and the owner-decision reference.
125
+ adjustments, then presses `Send answers` on the live review server page; `review.mjs` writes
126
+ `answers.json` into the canvas folder and exits. Record the canvas choice ID and the
127
+ owner-decision reference.
122
128
  - **Stage 3 — atomic replacement in the kit source.** Only AFTER the owner picks on the A/B canvas,
123
129
  build the chosen design into the source folder of packages/mmwork-ds in mutmutco/MM-Work,
124
130
  **atomically replacing** every other legacy or competing variant of that piece across the design
@@ -137,7 +143,7 @@ requests like this should follow this structure, not prose guide."
137
143
 
138
144
  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 A/B choice is needed. Functional journeys, where separately permitted, stay opt-in `workflow_dispatch`-only and never act as design checks.
139
145
 
140
- 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 and opened with one command: `node artifacts/review/review.mjs <folder> --standalone [<out.html>] [--open]`, which runs `check.mjs`, `check-ui.mjs` and `geometry.mjs`, pre-renders the board in `node:vm` (`ReactDOMServer.renderToStaticMarkup` into `#root`), runs `impeccable detect --json` on that rendered HTML, and opens it in the browser with `--open`.
146
+ 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 `node artifacts/review/review.mjs <folder> --open`, which serves the canvas over the live loopback HTTP review server (`http://127.0.0.1:<port>/`) where the owner presses `Send answers`; `--standalone [<out.html>]` is only for offline HTML previews/exports and SSR pre-render verification, never for an interactive owner decision.
141
147
 
142
148
  Impeccable v4.7.0 (engine v0.1.16) workflow; CLI verbs and agent playbooks are distinct:
143
149
 
package/skills/org-guide/references/work-and-releases.md CHANGED
@@ -51,11 +51,14 @@ design work follows one harmonized **Front-Loaded Impeccable v4.7.0 + MM Artifac
51
51
  `DESIGN.md` plus its `design.json` sidecar in `.impeccable`, shared `.impeccable/config.json`
52
52
  (`hook.enabled: true`), `reference/craft-floor.md` + `reference/operate.md`, and
53
53
  `impeccable detect --json <target>`.
54
- - **MM Artifacts** (local/canvas packs in the `mm-artifact` v3 format) use one command:
55
- `node artifacts/review/review.mjs <folder> --standalone [<out.html>] [--open]`. It runs `check.mjs`,
56
- `check-ui.mjs` and `geometry.mjs`, pre-renders the board in `node:vm` via
57
- `ReactDOMServer.renderToStaticMarkup` into `#root`, runs `impeccable detect --json` on that
58
- SSR-rendered HTML, and opens the result in the browser with `--open`.
54
+ - **MM Artifacts** (local/canvas packs in the `mm-artifact` v3 format) use one command,
55
+ `node artifacts/review/review.mjs <folder>`. It runs `check.mjs`, `check-ui.mjs` and
56
+ `geometry.mjs`, pre-renders the board in `node:vm` via `ReactDOMServer.renderToStaticMarkup` into
57
+ `#root` and runs `impeccable detect --json` on that SSR-rendered HTML. Interactive owner A/B
58
+ reviews use `node artifacts/review/review.mjs <folder> --open`: it serves the canvas over the live
59
+ loopback HTTP review server (`http://127.0.0.1:<port>/`) and the owner's `Send answers` posts back
60
+ to `POST /answers`. `--standalone [<out.html>]` is only for offline HTML previews/exports and SSR
61
+ pre-render verification, never for an interactive owner decision.
59
62
  - **Live Docs** (`Canlı belgeler` viewer) carry the living references, including the live
60
63
  design-system artifact `3a5c79df-5274-40ad-a1b5-a75e67a74dac`.
61
64
  - **Atomic Design Kit** (`@mutmutco/mmwork-ds`): kit pieces and tokens only, checked with `mmwork-check-ui`.
@@ -73,7 +76,7 @@ How the five pillars fit together (owner, 2026-10-25):
73
76
  Four owner decisions (2026-10-25T15:35:52Z):
74
77
 
75
78
  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.
76
- 2. **Where to save — local HTML for dev, Live Docs for shared.** Coding agents build and open local `.html` MM Artifacts (`node artifacts/review/review.mjs <folder> --standalone [<out.html>] [--open]`) for fast iteration, and 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.
79
+ 2. **Where to save — local HTML for dev, Live Docs for shared.** Coding agents build and open local `.html` MM Artifacts for fast iteration — interactive owner A/B reviews with `node artifacts/review/review.mjs <folder> --open` on the live loopback HTTP review server (`http://127.0.0.1:<port>/` with `Send answers`), and offline HTML previews/exports or SSR pre-render verification (`impeccable detect --json`) with `node artifacts/review/review.mjs <folder> --standalone [<out.html>]` — and 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.
77
80
  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.
78
81
  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.
79
82
 
@@ -209,11 +212,17 @@ requests like this should follow this structure, not prose guide."
209
212
  Option C, each its own full-resolution `1440x900` live HTML board in one MM Artifact A/B canvas
210
213
  (Part 3 rules: content-only `Ctrl + Mousewheel` zoom, 1:1 or side-by-side live comparison). Open
211
214
  the verified canvas in the browser automatically with
212
- `node artifacts/review/review.mjs <folder> --standalone --open`. Spawn a dedicated, fresh
215
+ `node artifacts/review/review.mjs <folder> --open`, which serves it over the live loopback HTTP
216
+ review server (`http://127.0.0.1:<port>/`) so the owner's `Send answers` posts straight back to
217
+ `POST /answers`. Never open a `--standalone` `file://` export (`Download answers.json`) for an
218
+ interactive owner A/B decision: `--standalone [<out.html>]` is only for offline previews/exports
219
+ and SSR detector checks. Spawn a dedicated, fresh
213
220
  `designer` subagent for each distinct design task (item 3); never reuse a busy designer seat.
214
221
  - **Stage 2 — the owner chooses visually on the A/B canvas.** Wait while the owner inspects the
215
222
  live HTML alternatives, zooms into details and picks the preferred design or asks for
216
- adjustments. Record the canvas choice ID and the owner-decision reference.
223
+ adjustments, then presses `Send answers` on the live review server page; `review.mjs` writes
224
+ `answers.json` into the canvas folder and exits. Record the canvas choice ID and the
225
+ owner-decision reference.
217
226
  - **Stage 3 — atomic replacement in the kit source.** Only AFTER the owner picks on the A/B canvas,
218
227
  build the chosen design into the source folder of packages/mmwork-ds in mutmutco/MM-Work,
219
228
  **atomically replacing** every other legacy or competing variant of that piece across the design