@mutmutco/cli 3.120.0 → 3.121.0

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 (2) hide show
  1. package/dist/main.cjs +13 -7
  2. package/package.json +1 -1
package/dist/main.cjs CHANGED
@@ -10004,6 +10004,12 @@ var MANAGED_GITIGNORE_LINES = [
10004
10004
  // thing blocking the cleanup that gate's own worktree needs. Org-universal: every repo runs the same
10005
10005
  // gate, so this belongs in the managed block rather than in one repo's own ignores.
10006
10006
  ".jerv/",
10007
+ // #4856: the JervCode (pi) host writes its loop journal to `.pi/loops/` in whatever repo it runs in —
10008
+ // the same runtime-state class as `.jerv/` and `.codex/` above, and the one active surface missing from
10009
+ // this list. Left un-ignored it is permanent `?? .pi/` noise that refuses a release clean-tree gate
10010
+ // (measured on the v3.120.0 Hub train), with no legal resolution: committing another host's runtime
10011
+ // state is not an option, so the operator's only move was to park the directory outside the repo.
10012
+ ".pi/",
10007
10013
  // #2321 doctrine: the canonical worktree home is the SIBLING `../mmi-worktrees/<RepoName>/<branch>` (outside the tree,
10008
10014
  // via `mmi-cli worktree create`), so a repo-local `.worktrees/` is NOT un-ignored org-wide — `mmi-cli
10009
10015
  // doctor` flags one explicitly instead (buildRepoLocalWorktreeCheck) rather than baking the fallback path
@@ -15845,10 +15851,10 @@ var rollout_plan_default = {
15845
15851
  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)."
15846
15852
  },
15847
15853
  baseline: {
15848
- version: "3.120.0",
15849
- tag: "v3.120.0",
15850
- commit: "5e8fd4eaab15",
15851
- npm: "@mutmutco/cli@3.120.0"
15854
+ version: "3.121.0",
15855
+ tag: "v3.121.0",
15856
+ commit: "3fc99b89d353",
15857
+ npm: "@mutmutco/cli@3.121.0"
15852
15858
  },
15853
15859
  exitCriterion: "fleet-n-of-n",
15854
15860
  hubOnlyShortcut: "forbidden",
@@ -15865,14 +15871,14 @@ var rollout_plan_default = {
15865
15871
  repo: "mutmutco/mmi-hub",
15866
15872
  role: "canary",
15867
15873
  schedule: "train",
15868
- v3Target: "v3.120.0"
15874
+ v3Target: "v3.121.0"
15869
15875
  }
15870
15876
  ],
15871
15877
  rollbackTrigger: "Any red inside the post-cut soak window: `devops train gate` FAIL attributable to the v4 doors, Hub endpoint health probe failure, a v3 client refused while the compat window must still admit it (SUPPORTED_MINOR_WINDOW=2, MIN_CLIENT_VERSION 0.0.0 \u2014 D6a), or npm consumer install/doctor failure on the v4 dist.",
15872
15878
  rollback: {
15873
15879
  independent: true,
15874
- mechanism: "npm dist-tag latest -> 3.120.0 and redeploy the Hub Lambda from tag v3.120.0 (5e8fd4eaab15); installed clients repair via `mmi-cli doctor`. No other cohort is touched.",
15875
- v3Target: "v3.120.0 (@mutmutco/cli@3.120.0, tag commit 5e8fd4eaab15 \u2014 the preserved latest-v3 distribution, D6b)"
15880
+ mechanism: "npm dist-tag latest -> 3.121.0 and redeploy the Hub Lambda from tag v3.121.0 (3fc99b89d353); installed clients repair via `mmi-cli doctor`. No other cohort is touched.",
15881
+ v3Target: "v3.121.0 (@mutmutco/cli@3.121.0, tag commit 3fc99b89d353 \u2014 the preserved latest-v3 distribution, D6b)"
15876
15882
  }
15877
15883
  },
15878
15884
  {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mutmutco/cli",
3
- "version": "3.120.0",
3
+ "version": "3.121.0",
4
4
  "description": "MMI Future CLI — the org dev toolbox and shared cross-IDE engine for every registry-declared MMI coding surface.",
5
5
  "type": "module",
6
6
  "license": "UNLICENSED",