@mutmutco/claude-plugin 4.5.206 → 4.5.208

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "mmi",
   "displayName": "MMI",
-  "version": "4.5.206",
+  "version": "4.5.208",
   "mmiCompat": "4.x",
   "description": "MMI workflow skills and org gates delivery.",
   "author": {

package/cli/dist/main.cjs

@@ -15498,12 +15498,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 +19344,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.206",
-    tag: "v4.5.206",
-    commit: "8031f7a9a4a8",
-    npm: "@mutmutco/cli@4.5.206"
+    version: "4.5.208",
+    tag: "v4.5.208",
+    commit: "86627b6751ed",
+    npm: "@mutmutco/cli@4.5.208"
   },
   exitCriterion: "fleet-n-of-n",
   hubOnlyShortcut: "forbidden",
@@ -19363,14 +19364,14 @@ var rollout_plan_default = {
           repo: "mutmutco/mmi-hub",
           role: "canary",
           schedule: "train",
-          v3Target: "v4.5.206"
+          v3Target: "v4.5.208"
         }
       ],
       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.206 and redeploy the Hub Lambda from tag v4.5.206 (8031f7a9a4a8); installed clients repair via `mmi-cli doctor`. No other cohort is touched.",
-        v3Target: "v4.5.206 (@mutmutco/cli@4.5.206, tag commit 8031f7a9a4a8 \u2014 last known-good release carrying the repo-index v4-only contract)"
+        mechanism: "npm dist-tag latest -> 4.5.208 and redeploy the Hub Lambda from tag v4.5.208 (86627b6751ed); installed clients repair via `mmi-cli doctor`. No other cohort is touched.",
+        v3Target: "v4.5.208 (@mutmutco/cli@4.5.208, tag commit 86627b6751ed \u2014 last known-good release carrying the repo-index v4-only contract)"
       }
     },
     {

package/cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mutmutco/cli",
-  "version": "4.5.206",
+  "version": "4.5.208",
   "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/claude-plugin",
-  "version": "4.5.206",
+  "version": "4.5.208",
   "description": "MMI workflow skills and org gates delivery.",
   "author": {
     "name": "MMI Future",

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

@@ -98,16 +98,15 @@ requests like this should follow this structure, not prose guide."
    Card), writing a markdown or prose spec in chat violates Principle 7 ("Choices for Jervaise go only
    on the A/B canvas"). Building one guessed design straight into the kit skips the owner's choice.
 2. **Always follow the visual spec pipeline:**
-   - **Phase 0 — Inspiration via Better Design MCP (`https://better-design.com/api/mcp`) and 21st.dev MCP (`https://21st.dev/api/mcp`) (owner ruling 2026-10-25T16:48:00Z, #8848).**
-     Before building visual A/B boards, query the two owner-selected prebuilt design inspiration MCP
-     servers — **Better Design MCP** (`https://better-design.com/api/mcp`) and **21st.dev MCP**
-     (`https://21st.dev/api/mcp`, verbatim selection: `"21st.dev MCP Better Design MCP"`) — alongside
-     front-loaded Impeccable to study high-craft reference patterns, layout proportions, and interaction
-     details. Always translate inspired patterns into zero-GPU `@mutmutco/mmwork-ds` tokens
-     (`--card-blur: none`, `--card-tint-dark: 0%`, `--card-tint-light: 0%`, sleek translucent glass
-     cards) and Atomic Design layers; never copy raw third-party CSS/HTML or GPU-heavy effects.
-     `MM-Inspo` is strictly a customer/tenant module inside the MM-Work suite, never an internal tool
-     for designing the MM-Work app or its design system.
+   - **Phase 0 — Inspiration via front-loaded Impeccable v4.7.0 and 21st.dev MCP (`https://21st.dev/api/mcp`) only (owner ruling 2026-10-25T21:37:00+03:00, #8854; superseding #8848).**
+     Before building visual A/B boards, use front-loaded **Impeccable v4.7.0** alongside **21st.dev MCP**
+     (`https://21st.dev/api/mcp`; verbatim owner ruling: `"we don't need the mcp better design yet,
+     impeccable and 21st is enough"`, dropping Better Design MCP) to study high-craft reference patterns,
+     layout proportions, and interaction details. Always translate inspired patterns into zero-GPU
+     `@mutmutco/mmwork-ds` tokens (`--card-blur: none`, `--card-tint-dark: 0%`, `--card-tint-light: 0%`,
+     sleek translucent glass cards) and Atomic Design layers; never copy raw third-party CSS/HTML or
+     GPU-heavy effects. `MM-Inspo` is strictly a customer/tenant module inside the MM-Work suite, never
+     an internal tool for designing the MM-Work app or its design system.
    - **Stage 1 — a designer subagent builds visual A/B alternatives on an MM Artifact canvas.**
      Dispatch a `designer` subagent with front-loaded Impeccable (`impeccable context`, `craft-floor`,
      `distill`, `typeset`, `layout`, `colorize`, `polish`) to create 2–3 genuinely distinct visual

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

@@ -193,16 +193,15 @@ requests like this should follow this structure, not prose guide."
    Card), writing a markdown or prose spec in chat violates Principle 7 ("Choices for Jervaise go only
    on the A/B canvas"). Building one guessed design straight into the kit skips the owner's choice.
 2. **Always follow the visual spec pipeline:**
-   - **Phase 0 — Inspiration via Better Design MCP (`https://better-design.com/api/mcp`) and 21st.dev MCP (`https://21st.dev/api/mcp`) (owner ruling 2026-10-25T16:48:00Z, #8848).**
-     Before building visual A/B boards, query the two owner-selected prebuilt design inspiration MCP
-     servers — **Better Design MCP** (`https://better-design.com/api/mcp`) and **21st.dev MCP**
-     (`https://21st.dev/api/mcp`, verbatim selection: `"21st.dev MCP Better Design MCP"`) — alongside
-     front-loaded Impeccable to study high-craft reference patterns, layout proportions, and interaction
-     details. Always translate inspired patterns into zero-GPU `@mutmutco/mmwork-ds` tokens
-     (`--card-blur: none`, `--card-tint-dark: 0%`, `--card-tint-light: 0%`, sleek translucent glass
-     cards) and Atomic Design layers; never copy raw third-party CSS/HTML or GPU-heavy effects.
-     `MM-Inspo` is strictly a customer/tenant module inside the MM-Work suite, never an internal tool
-     for designing the MM-Work app or its design system.
+   - **Phase 0 — Inspiration via front-loaded Impeccable v4.7.0 and 21st.dev MCP (`https://21st.dev/api/mcp`) only (owner ruling 2026-10-25T21:37:00+03:00, #8854; superseding #8848).**
+     Before building visual A/B boards, use front-loaded **Impeccable v4.7.0** alongside **21st.dev MCP**
+     (`https://21st.dev/api/mcp`; verbatim owner ruling: `"we don't need the mcp better design yet,
+     impeccable and 21st is enough"`, dropping Better Design MCP) to study high-craft reference patterns,
+     layout proportions, and interaction details. Always translate inspired patterns into zero-GPU
+     `@mutmutco/mmwork-ds` tokens (`--card-blur: none`, `--card-tint-dark: 0%`, `--card-tint-light: 0%`,
+     sleek translucent glass cards) and Atomic Design layers; never copy raw third-party CSS/HTML or
+     GPU-heavy effects. `MM-Inspo` is strictly a customer/tenant module inside the MM-Work suite, never
+     an internal tool for designing the MM-Work app or its design system.
    - **Stage 1 — a designer subagent builds visual A/B alternatives on an MM Artifact canvas.**
      Dispatch a `designer` subagent with front-loaded Impeccable (`impeccable context`, `craft-floor`,
      `distill`, `typeset`, `layout`, `colorize`, `polish`) to create 2–3 genuinely distinct visual