@mutmutco/codex-plugin 4.5.207 → 4.5.209

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "mmi",
-  "version": "4.5.207",
+  "version": "4.5.209",
   "mmiCompat": "4.x",
   "description": "MMI workflow skills and org gates delivery.",
   "author": {

package/cli/dist/main.cjs

@@ -1598,13 +1598,15 @@ __export(index_exports, {
   commandOwnLongFlags: () => commandOwnLongFlags,
   envHealLockPath: () => envHealLockPath,
   isOrgRegisteredRepo: () => isOrgRegisteredRepo,
+  normalizeBoardClaimIssueArgv: () => normalizeBoardClaimIssueArgv,
   parseInvalidChoiceError: () => parseInvalidChoiceError,
   positionalTargetForm: () => positionalTargetForm,
   registryClientDeps: () => registryClientDeps,
   repoSlug: () => repoSlug,
   suggestCommandPath: () => suggestCommandPath,
   unknownCommandCandidates: () => unknownCommandCandidates,
-  unknownCommandTail: () => unknownCommandTail
+  unknownCommandTail: () => unknownCommandTail,
+  workboardClaimRecovery: () => workboardClaimRecovery
 });
 module.exports = __toCommonJS(index_exports);
 
@@ -6350,6 +6352,81 @@ function boardClaimStatusFlagRecovery(flag, canonicalPath, argv) {
     corrected: `mmi-cli ${kept.join(" ")}`
   };
 }
+var BOARD_CLAIM_OWN_FLAGS = ["--repo", "--for", "--force", "--check", "--allow-partial", "--json"];
+function splitInlineSelectors(argv, flags) {
+  const out = [];
+  for (const tok of argv) {
+    const eq = tok.indexOf("=");
+    if (tok.startsWith("--") && eq > 0 && flags.includes(tok.slice(0, eq))) {
+      out.push(tok.slice(0, eq), tok.slice(eq + 1));
+    } else {
+      out.push(tok);
+    }
+  }
+  return out;
+}
+function workboardClaimRecovery(unknownToken, argv, paths, ownFlags = BOARD_CLAIM_OWN_FLAGS) {
+  if (unknownToken !== "workboard") return void 0;
+  const catalog = [...paths];
+  if (!catalog.includes("oracle board claim") && !catalog.includes("board claim")) return void 0;
+  const tail = unknownCommandTail(argv, "workboard");
+  if (tail[0] !== "claim") return void 0;
+  const canonicalPath = "oracle board claim";
+  const positionals = tail.slice(1);
+  let corrected;
+  if (positionals.length > 0) {
+    corrected = [`mmi-cli ${canonicalPath}`, ...positionals, ...survivingFlagArgs(argv, "", ownFlags)].join(" ");
+  } else {
+    const normalized = splitInlineSelectors(argv, ["--issue", "--number"]);
+    const usedFlag = normalized.includes("--issue") ? "--issue" : normalized.includes("--number") ? "--number" : "--issue";
+    corrected = formatPositionalTarget(canonicalPath, "issues", { flag: usedFlag, argv: normalized, ownFlags });
+  }
+  return { canonicalPath, corrected, hint: `did you mean \`${corrected}\`?` };
+}
+var BOARD_CLAIM_VALUE_FLAGS = /* @__PURE__ */ new Set(["--repo", "--for", "--status"]);
+var BOARD_CLAIM_BOOLEAN_FLAGS = /* @__PURE__ */ new Set(["--json", "--force", "--check", "--allow-partial", "--help", "-h"]);
+function normalizeBoardClaimIssueArgv(argv) {
+  let claimAt;
+  if (argv[2] === "board" && argv[3] === "claim") claimAt = 3;
+  else if (argv[2] === "oracle" && argv[3] === "board" && argv[4] === "claim") claimAt = 4;
+  else return false;
+  let issueAt = -1;
+  let issueSpan = 0;
+  let value;
+  for (let i = claimAt + 1; i < argv.length; i += 1) {
+    const tok = argv[i];
+    if (tok === "--issue" || tok.startsWith("--issue=")) {
+      if (issueAt >= 0) return false;
+      issueAt = i;
+      if (tok === "--issue") {
+        const next = argv[i + 1];
+        if (next === void 0 || next === "" || next.startsWith("-")) return false;
+        value = next;
+        issueSpan = 2;
+        i += 1;
+      } else {
+        value = tok.slice("--issue=".length);
+        if (value === "" || value.startsWith("-")) return false;
+        issueSpan = 1;
+      }
+      continue;
+    }
+    if (tok.startsWith("-")) {
+      const name = tok.includes("=") ? tok.slice(0, tok.indexOf("=")) : tok;
+      if (BOARD_CLAIM_VALUE_FLAGS.has(name)) {
+        if (!tok.includes("=") && argv[i + 1] !== void 0 && !argv[i + 1].startsWith("-")) i += 1;
+        continue;
+      }
+      if (BOARD_CLAIM_BOOLEAN_FLAGS.has(tok)) continue;
+      return false;
+    }
+    return false;
+  }
+  if (issueAt < 0 || value === void 0) return false;
+  argv.splice(issueAt, issueSpan);
+  argv.splice(claimAt + 1, 0, value);
+  return true;
+}
 function classifyParseError(plain) {
   if (/unknown command/i.test(plain)) return "unknown-command";
   if (/unknown option|missing required argument|too many arguments|argument missing|is invalid\. Allowed choices are|cannot be used with/i.test(plain)) {
@@ -15498,12 +15575,13 @@ function laneContestParts(contest) {
 function isUnknownHold(contest) {
   return !contest.marker && contest.live.length === 0 && contest.unverifiable.length > 0;
 }
+var CONTESTED_CLAIM_RECOVERY = "leave the holder's work untouched and choose another unclaimed item or coordinate a handoff (use --force only for an intentional takeover)";
 function laneContestMessage(ref, contest, verb) {
   const { holder, why } = laneContestParts(contest);
   if (isUnknownHold(contest)) {
-    return verb === "claim" ? `${ref} cannot be verified as free: ${holder} (${why}); the liveness reads failed so the claim is refused fail-closed \u2014 re-run with --force to take it anyway` : `refusing to unclaim ${ref}: ${holder} (${why}); the liveness reads failed so the unclaim is refused fail-closed \u2014 re-run with --force --holder-dead once you have evidence the holder lane is dead, or wait for it to go stale (#6625)`;
+    return verb === "claim" ? `${ref} cannot be verified as free: ${holder} (${why}); the liveness reads failed so the claim is refused fail-closed \u2014 ${CONTESTED_CLAIM_RECOVERY}` : `refusing to unclaim ${ref}: ${holder} (${why}); the liveness reads failed so the unclaim is refused fail-closed \u2014 re-run with --force --holder-dead once you have evidence the holder lane is dead, or wait for it to go stale (#6625)`;
   }
-  return verb === "claim" ? `${ref} is already claimed by ${holder} with live evidence of active work (${why}); re-run with --force to take it anyway` : `refusing to unclaim ${ref}: ${holder} shows live evidence of active work (${why}); re-run with --force --holder-dead once you have evidence the holder lane is dead, or wait for it to go stale (#6625)`;
+  return verb === "claim" ? `${ref} is already claimed by ${holder} with live evidence of active work (${why}); ${CONTESTED_CLAIM_RECOVERY}` : `refusing to unclaim ${ref}: ${holder} shows live evidence of active work (${why}); re-run with --force --holder-dead once you have evidence the holder lane is dead, or wait for it to go stale (#6625)`;
 }
 function ghError(e) {
   const err = e;
@@ -19343,10 +19421,10 @@ var rollout_plan_default = {
     note: "The v4.0.0 stamp happens at cut time (D6e #4463); until then the candidate is the origin/development head artifacts (built cli/dist + npm pack), identity proven by dist content hash (D6a)."
   },
   baseline: {
-    version: "4.5.207",
-    tag: "v4.5.207",
-    commit: "55e3ac7b8df0",
-    npm: "@mutmutco/cli@4.5.207"
+    version: "4.5.209",
+    tag: "v4.5.209",
+    commit: "2449709d554c",
+    npm: "@mutmutco/cli@4.5.209"
   },
   exitCriterion: "fleet-n-of-n",
   hubOnlyShortcut: "forbidden",
@@ -19363,14 +19441,14 @@ var rollout_plan_default = {
           repo: "mutmutco/mmi-hub",
           role: "canary",
           schedule: "train",
-          v3Target: "v4.5.207"
+          v3Target: "v4.5.209"
         }
       ],
       rollbackTrigger: "Any red inside the post-contract soak window: `devops train gate` FAIL attributable to the v4 doors, Hub endpoint health probe failure, a pre-v4 client admitted instead of receiving actionable HTTP 426, or npm consumer install/doctor failure on the v4-only dist.",
       rollback: {
         independent: true,
-        mechanism: "npm dist-tag latest -> 4.5.207 and redeploy the Hub Lambda from tag v4.5.207 (55e3ac7b8df0); installed clients repair via `mmi-cli doctor`. No other cohort is touched.",
-        v3Target: "v4.5.207 (@mutmutco/cli@4.5.207, tag commit 55e3ac7b8df0 \u2014 last known-good release carrying the repo-index v4-only contract)"
+        mechanism: "npm dist-tag latest -> 4.5.209 and redeploy the Hub Lambda from tag v4.5.209 (2449709d554c); installed clients repair via `mmi-cli doctor`. No other cohort is touched.",
+        v3Target: "v4.5.209 (@mutmutco/cli@4.5.209, tag commit 2449709d554c \u2014 last known-good release carrying the repo-index v4-only contract)"
       }
     },
     {
@@ -58008,6 +58086,7 @@ var STALE_HINT = `(${DISCOVERY_HINT}). If you expected this command to exist, yo
 var lastParseErrorKind = "other";
 var lastUnknownCommand;
 var lastParseErrorConflict = false;
+var lastParseHintOwnsGuess = false;
 function parseInvalidChoiceError(plain) {
   const m = /option '([^']+)' argument '([^']*)' is invalid\. Allowed choices are ([^.]+)\./.exec(plain);
   if (!m) return void 0;
@@ -58076,6 +58155,12 @@ function resolveParseHint() {
     const parentPath = parent ? canonicalPathFor(commandPath3(parent)) ?? commandPath3(parent) : void 0;
     const guide = unknownCommandDomainGuide(parentPath, lastUnknownCommand);
     if (guide) return `(${guide.hint}. ${DISCOVERY_HINT})`;
+    const claimCmd = resolveCommandFromArgv(program2, ["board", "claim"]);
+    const workboard = claimCmd ? workboardClaimRecovery(lastUnknownCommand, process.argv.slice(2), allCommandPaths(), commandOwnLongFlags(claimCmd)) : void 0;
+    if (workboard) {
+      lastParseHintOwnsGuess = true;
+      return `(${workboard.hint} ${DISCOVERY_HINT})`;
+    }
     const candidates = unknownCommandCandidates(parent, allCommandPaths());
     const tail = unknownCommandTail(process.argv.slice(2), lastUnknownCommand);
     const path3 = lastUnknownCommand ? suggestCommandPath(lastUnknownCommand, candidates, tail) : void 0;
@@ -58134,7 +58219,7 @@ function envelopeAwareWriteErr(str2) {
       return;
     }
     const resolvedHint = resolveParseHint();
-    if (lastParseErrorKind === "unknown-command" && (resolvedHint === STALE_HINT || resolvedHint === `(${DISCOVERY_HINT})`)) {
+    if (lastParseErrorKind === "unknown-command" && (lastParseHintOwnsGuess || resolvedHint === STALE_HINT || resolvedHint === `(${DISCOVERY_HINT})`)) {
       pendingHumanParseError = pendingHumanParseError?.replace(/\n\(Did you mean [^)]+\?\)/g, "");
     }
     const hint = str2.replace(PARSE_HINT_SENTINEL, resolvedHint);
@@ -59427,6 +59512,7 @@ function printHouseRootHelp(house) {
 }
 resolveVerbAliasShim(process.argv);
 resolveHouseShim(process.argv);
+normalizeBoardClaimIssueArgv(process.argv);
 program2.parseAsync(process.argv).then(() => finishCliRun()).catch((e) => failGraceful(e.message));
 // Annotate the CommonJS export names for ESM import in node:
 0 && (module.exports = {
@@ -59437,11 +59523,13 @@ program2.parseAsync(process.argv).then(() => finishCliRun()).catch((e) => failGr
   commandOwnLongFlags,
   envHealLockPath,
   isOrgRegisteredRepo,
+  normalizeBoardClaimIssueArgv,
   parseInvalidChoiceError,
   positionalTargetForm,
   registryClientDeps,
   repoSlug,
   suggestCommandPath,
   unknownCommandCandidates,
-  unknownCommandTail
+  unknownCommandTail,
+  workboardClaimRecovery
 });

package/cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mutmutco/cli",
-  "version": "4.5.207",
+  "version": "4.5.209",
   "description": "MMI Future CLI — the org dev toolbox and shared cross-IDE engine for every registry-declared MMI coding surface.",
   "type": "module",
   "license": "UNLICENSED",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mutmutco/codex-plugin",
-  "version": "4.5.207",
+  "version": "4.5.209",
   "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 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.
+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.
 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.
 
@@ -114,11 +114,17 @@ 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). Open
      the verified canvas in the browser automatically with
-     `node artifacts/review/review.mjs <folder> --standalone --open`. Spawn a dedicated, fresh
+     `node artifacts/review/review.mjs <folder> --open`, which serves it over the live loopback HTTP
+     review server (`http://127.0.0.1:<port>/`) so the owner's `Send answers` posts straight back to
+     `POST /answers`. Never open a `--standalone` `file://` export (`Download answers.json`) for an
+     interactive owner A/B decision: `--standalone [<out.html>]` is only for offline previews/exports
+     and SSR detector checks. Spawn a dedicated, fresh
      `designer` subagent for each distinct design task (item 3); never reuse a busy designer seat.
    - **Stage 2 — the owner chooses visually on the A/B canvas.** Wait while the owner inspects the
      live HTML alternatives, zooms into details and picks the preferred design or asks for
-     adjustments. Record the canvas choice ID and the owner-decision reference.
+     adjustments, then presses `Send answers` on the live review server page; `review.mjs` writes
+     `answers.json` into the canvas folder and exits. Record the canvas choice ID and the
+     owner-decision reference.
    - **Stage 3 — atomic replacement in the kit source.** Only AFTER the owner picks on the A/B canvas,
      build the chosen design into the source folder of packages/mmwork-ds in mutmutco/MM-Work,
      **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."
 
 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.
 
-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`.
+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.
 
 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

@@ -51,11 +51,14 @@ design work follows one harmonized **Front-Loaded Impeccable v4.7.0 + MM Artifac
   `DESIGN.md` plus its `design.json` sidecar in `.impeccable`, shared `.impeccable/config.json`
   (`hook.enabled: true`), `reference/craft-floor.md` + `reference/operate.md`, and
   `impeccable detect --json <target>`.
-- **MM Artifacts** (local/canvas packs in the `mm-artifact` v3 format) use one command:
-  `node artifacts/review/review.mjs <folder> --standalone [<out.html>] [--open]`. It runs `check.mjs`,
-  `check-ui.mjs` and `geometry.mjs`, pre-renders the board in `node:vm` via
-  `ReactDOMServer.renderToStaticMarkup` into `#root`, runs `impeccable detect --json` on that
-  SSR-rendered HTML, and opens the result in the browser with `--open`.
+- **MM Artifacts** (local/canvas packs in the `mm-artifact` v3 format) use one command,
+  `node artifacts/review/review.mjs <folder>`. It runs `check.mjs`, `check-ui.mjs` and
+  `geometry.mjs`, pre-renders the board in `node:vm` via `ReactDOMServer.renderToStaticMarkup` into
+  `#root` and runs `impeccable detect --json` on that SSR-rendered HTML. Interactive owner A/B
+  reviews use `node artifacts/review/review.mjs <folder> --open`: it serves the canvas over the live
+  loopback HTTP review server (`http://127.0.0.1:<port>/`) and the owner's `Send answers` posts back
+  to `POST /answers`. `--standalone [<out.html>]` is only for offline HTML previews/exports and SSR
+  pre-render verification, never for an interactive owner decision.
 - **Live Docs** (`Canlı belgeler` viewer) carry the living references, including the live
   design-system artifact `3a5c79df-5274-40ad-a1b5-a75e67a74dac`.
 - **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):
 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 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.
+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.
 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.
 
@@ -209,11 +212,17 @@ 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). Open
      the verified canvas in the browser automatically with
-     `node artifacts/review/review.mjs <folder> --standalone --open`. Spawn a dedicated, fresh
+     `node artifacts/review/review.mjs <folder> --open`, which serves it over the live loopback HTTP
+     review server (`http://127.0.0.1:<port>/`) so the owner's `Send answers` posts straight back to
+     `POST /answers`. Never open a `--standalone` `file://` export (`Download answers.json`) for an
+     interactive owner A/B decision: `--standalone [<out.html>]` is only for offline previews/exports
+     and SSR detector checks. Spawn a dedicated, fresh
      `designer` subagent for each distinct design task (item 3); never reuse a busy designer seat.
    - **Stage 2 — the owner chooses visually on the A/B canvas.** Wait while the owner inspects the
      live HTML alternatives, zooms into details and picks the preferred design or asks for
-     adjustments. Record the canvas choice ID and the owner-decision reference.
+     adjustments, then presses `Send answers` on the live review server page; `review.mjs` writes
+     `answers.json` into the canvas folder and exits. Record the canvas choice ID and the
+     owner-decision reference.
    - **Stage 3 — atomic replacement in the kit source.** Only AFTER the owner picks on the A/B canvas,
      build the chosen design into the source folder of packages/mmwork-ds in mutmutco/MM-Work,
      **atomically replacing** every other legacy or competing variant of that piece across the design