@mutmutco/codex-plugin 4.5.206 → 4.5.208
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.
package/cli/dist/main.cjs
CHANGED
|
@@ -15498,12 +15498,13 @@ function laneContestParts(contest) {
|
|
|
15498
15498
|
function isUnknownHold(contest) {
|
|
15499
15499
|
return !contest.marker && contest.live.length === 0 && contest.unverifiable.length > 0;
|
|
15500
15500
|
}
|
|
15501
|
+
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)";
|
|
15501
15502
|
function laneContestMessage(ref, contest, verb) {
|
|
15502
15503
|
const { holder, why } = laneContestParts(contest);
|
|
15503
15504
|
if (isUnknownHold(contest)) {
|
|
15504
|
-
return verb === "claim" ? `${ref} cannot be verified as free: ${holder} (${why}); the liveness reads failed so the claim is refused fail-closed \u2014
|
|
15505
|
+
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)`;
|
|
15505
15506
|
}
|
|
15506
|
-
return verb === "claim" ? `${ref} is already claimed by ${holder} with live evidence of active work (${why});
|
|
15507
|
+
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)`;
|
|
15507
15508
|
}
|
|
15508
15509
|
function ghError(e) {
|
|
15509
15510
|
const err = e;
|
|
@@ -19343,10 +19344,10 @@ var rollout_plan_default = {
|
|
|
19343
19344
|
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)."
|
|
19344
19345
|
},
|
|
19345
19346
|
baseline: {
|
|
19346
|
-
version: "4.5.
|
|
19347
|
-
tag: "v4.5.
|
|
19348
|
-
commit: "
|
|
19349
|
-
npm: "@mutmutco/cli@4.5.
|
|
19347
|
+
version: "4.5.208",
|
|
19348
|
+
tag: "v4.5.208",
|
|
19349
|
+
commit: "86627b6751ed",
|
|
19350
|
+
npm: "@mutmutco/cli@4.5.208"
|
|
19350
19351
|
},
|
|
19351
19352
|
exitCriterion: "fleet-n-of-n",
|
|
19352
19353
|
hubOnlyShortcut: "forbidden",
|
|
@@ -19363,14 +19364,14 @@ var rollout_plan_default = {
|
|
|
19363
19364
|
repo: "mutmutco/mmi-hub",
|
|
19364
19365
|
role: "canary",
|
|
19365
19366
|
schedule: "train",
|
|
19366
|
-
v3Target: "v4.5.
|
|
19367
|
+
v3Target: "v4.5.208"
|
|
19367
19368
|
}
|
|
19368
19369
|
],
|
|
19369
19370
|
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.",
|
|
19370
19371
|
rollback: {
|
|
19371
19372
|
independent: true,
|
|
19372
|
-
mechanism: "npm dist-tag latest -> 4.5.
|
|
19373
|
-
v3Target: "v4.5.
|
|
19373
|
+
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.",
|
|
19374
|
+
v3Target: "v4.5.208 (@mutmutco/cli@4.5.208, tag commit 86627b6751ed \u2014 last known-good release carrying the repo-index v4-only contract)"
|
|
19374
19375
|
}
|
|
19375
19376
|
},
|
|
19376
19377
|
{
|
package/cli/package.json
CHANGED
package/package.json
CHANGED
|
@@ -98,16 +98,15 @@ requests like this should follow this structure, not prose guide."
|
|
|
98
98
|
Card), writing a markdown or prose spec in chat violates Principle 7 ("Choices for Jervaise go only
|
|
99
99
|
on the A/B canvas"). Building one guessed design straight into the kit skips the owner's choice.
|
|
100
100
|
2. **Always follow the visual spec pipeline:**
|
|
101
|
-
- **Phase 0 — Inspiration via
|
|
102
|
-
Before building visual A/B boards,
|
|
103
|
-
|
|
104
|
-
|
|
105
|
-
|
|
106
|
-
|
|
107
|
-
|
|
108
|
-
|
|
109
|
-
|
|
110
|
-
for designing the MM-Work app or its design system.
|
|
101
|
+
- **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).**
|
|
102
|
+
Before building visual A/B boards, use front-loaded **Impeccable v4.7.0** alongside **21st.dev MCP**
|
|
103
|
+
(`https://21st.dev/api/mcp`; verbatim owner ruling: `"we don't need the mcp better design yet,
|
|
104
|
+
impeccable and 21st is enough"`, dropping Better Design MCP) to study high-craft reference patterns,
|
|
105
|
+
layout proportions, and interaction details. Always translate inspired patterns into zero-GPU
|
|
106
|
+
`@mutmutco/mmwork-ds` tokens (`--card-blur: none`, `--card-tint-dark: 0%`, `--card-tint-light: 0%`,
|
|
107
|
+
sleek translucent glass cards) and Atomic Design layers; never copy raw third-party CSS/HTML or
|
|
108
|
+
GPU-heavy effects. `MM-Inspo` is strictly a customer/tenant module inside the MM-Work suite, never
|
|
109
|
+
an internal tool for designing the MM-Work app or its design system.
|
|
111
110
|
- **Stage 1 — a designer subagent builds visual A/B alternatives on an MM Artifact canvas.**
|
|
112
111
|
Dispatch a `designer` subagent with front-loaded Impeccable (`impeccable context`, `craft-floor`,
|
|
113
112
|
`distill`, `typeset`, `layout`, `colorize`, `polish`) to create 2–3 genuinely distinct visual
|
|
@@ -193,16 +193,15 @@ requests like this should follow this structure, not prose guide."
|
|
|
193
193
|
Card), writing a markdown or prose spec in chat violates Principle 7 ("Choices for Jervaise go only
|
|
194
194
|
on the A/B canvas"). Building one guessed design straight into the kit skips the owner's choice.
|
|
195
195
|
2. **Always follow the visual spec pipeline:**
|
|
196
|
-
- **Phase 0 — Inspiration via
|
|
197
|
-
Before building visual A/B boards,
|
|
198
|
-
|
|
199
|
-
|
|
200
|
-
|
|
201
|
-
|
|
202
|
-
|
|
203
|
-
|
|
204
|
-
|
|
205
|
-
for designing the MM-Work app or its design system.
|
|
196
|
+
- **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).**
|
|
197
|
+
Before building visual A/B boards, use front-loaded **Impeccable v4.7.0** alongside **21st.dev MCP**
|
|
198
|
+
(`https://21st.dev/api/mcp`; verbatim owner ruling: `"we don't need the mcp better design yet,
|
|
199
|
+
impeccable and 21st is enough"`, dropping Better Design MCP) to study high-craft reference patterns,
|
|
200
|
+
layout proportions, and interaction details. Always translate inspired patterns into zero-GPU
|
|
201
|
+
`@mutmutco/mmwork-ds` tokens (`--card-blur: none`, `--card-tint-dark: 0%`, `--card-tint-light: 0%`,
|
|
202
|
+
sleek translucent glass cards) and Atomic Design layers; never copy raw third-party CSS/HTML or
|
|
203
|
+
GPU-heavy effects. `MM-Inspo` is strictly a customer/tenant module inside the MM-Work suite, never
|
|
204
|
+
an internal tool for designing the MM-Work app or its design system.
|
|
206
205
|
- **Stage 1 — a designer subagent builds visual A/B alternatives on an MM Artifact canvas.**
|
|
207
206
|
Dispatch a `designer` subagent with front-loaded Impeccable (`impeccable context`, `craft-floor`,
|
|
208
207
|
`distill`, `typeset`, `layout`, `colorize`, `polish`) to create 2–3 genuinely distinct visual
|