@mutmutco/claude-plugin 4.6.44 → 4.6.45

package/.claude-plugin/plugin.json

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

package/cli/dist/main.cjs

@@ -28556,10 +28556,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.6.44",
-    tag: "v4.6.44",
-    commit: "2ce6b7e5afc3",
-    npm: "@mutmutco/cli@4.6.44"
+    version: "4.6.45",
+    tag: "v4.6.45",
+    commit: "0a8549c195cd",
+    npm: "@mutmutco/cli@4.6.45"
   },
   exitCriterion: "fleet-n-of-n",
   hubOnlyShortcut: "forbidden",
@@ -28576,14 +28576,14 @@ var rollout_plan_default = {
           repo: "mutmutco/mmi-hub",
           role: "canary",
           schedule: "train",
-          v3Target: "v4.6.44"
+          v3Target: "v4.6.45"
         }
       ],
       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.6.44 and redeploy the Hub Lambda from tag v4.6.44 (2ce6b7e5afc3); installed clients repair via `mmi-cli doctor`. No other cohort is touched.",
-        v3Target: "v4.6.44 (@mutmutco/cli@4.6.44, tag commit 2ce6b7e5afc3 \u2014 last known-good release carrying the repo-index v4-only contract)"
+        mechanism: "npm dist-tag latest -> 4.6.45 and redeploy the Hub Lambda from tag v4.6.45 (0a8549c195cd); installed clients repair via `mmi-cli doctor`. No other cohort is touched.",
+        v3Target: "v4.6.45 (@mutmutco/cli@4.6.45, tag commit 0a8549c195cd \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.6.44",
+  "version": "4.6.45",
   "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.6.44",
+  "version": "4.6.45",
   "description": "MMI workflow skills and org gates delivery.",
   "author": {
     "name": "MMI Future",

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

@@ -309,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