@mutmutco/claude-plugin 3.131.0 → 3.132.1

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.
@@ -1,7 +1,8 @@
1
1
  {
2
2
  "name": "mmi",
3
3
  "displayName": "MMI",
4
- "version": "3.131.0",
4
+ "version": "3.132.1",
5
+ "mmiCompat": "3.x",
5
6
  "description": "MMI workflow skills and org gates delivery.",
6
7
  "author": {
7
8
  "name": "MMI Future",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mutmutco/claude-plugin",
3
- "version": "3.131.0",
3
+ "version": "3.132.1",
4
4
  "description": "MMI workflow skills and org gates delivery.",
5
5
  "author": {
6
6
  "name": "MMI Future",
@@ -13,7 +13,6 @@
13
13
  },
14
14
  "files": [
15
15
  ".claude-plugin/plugin.json",
16
- ".pi-plugin/package.json",
17
16
  "skills",
18
17
  "hooks",
19
18
  "scripts",
@@ -53,16 +53,13 @@ Still run it in the foreground and wait. The lock stops corruption, not confusio
53
53
  that reports "skipped — lock busy" has healed nothing, and an agent that does not read that line will
54
54
  carry on believing its tooling was fixed.
55
55
 
56
- `doctor --no-repo-writes` heals a stale npm global or a stale/unresolved plugin install (the **env**
57
- half of the interactive doctor, #3485/#3975) — it never touches the repo working tree. When it prints
56
+ `doctor --no-repo-writes` heals a stale/unresolved plugin install (the **env** half of the interactive
57
+ doctor, #3485/#3975) — it never touches the repo working tree. When it prints
58
58
  `↻ Updating mmi tooling, one moment…`, relay that before waiting; when it prints `↻ MMI tooling
59
59
  updated — …`, relay the reload/restart guidance.
60
60
 
61
61
  What the env half heals:
62
62
 
63
- - a behind npm global → `npm install -g @mutmutco/cli@<released version>`, pinned, never the floating
64
- `@latest`, which npm can resolve off a cached packument and reinstall the stale version right after a
65
- publish (#3422). Effective on the next invocation.
66
63
  - a stale or unresolved Claude plugin → `claude plugin marketplace remove mmi` → `… remove mutmutco` →
67
64
  `claude plugin marketplace add mutmutco/MMI-Hub` → `claude plugin install mmi@mutmutco`. A fresh
68
65
  reinstall, never `claude plugin update`, which nests into itself past MAX_PATH on Windows and wipes the
@@ -72,6 +69,10 @@ What the env half heals:
72
69
  docs/doctor-contract.md § Guarded cache prune): never the running/newest/installed version, a cache a
73
70
  live session holds is named "still held" and never forced.
74
71
 
72
+ What it does **not** do since #4954: install anything. A behind npm global is REPORTED (the `mmi-cli`
73
+ row names `npm install -g @mutmutco/cli@<released>`) and the `fleet` row reads the scheduled
74
+ `mmi-updater`'s journal — that reconciler is the single writer of CLI and plugin versions.
75
+
75
76
  - **Fast path** → `whoami` then `board read`; no foreground doctor.
76
77
  - **Hard setup signal** → run `doctor --no-repo-writes`, relay `↻` lines, then retry `board read` when appropriate.
77
78
  - **`mmi-cli: command not found`** → plugin PATH provisioning has not applied, or the standalone CLI is not installed.
@@ -13,10 +13,15 @@ One command. Run it when a session opens messy or before a handoff.
13
13
  mmi-cli doctor
14
14
  ```
15
15
 
16
- By default this **heals and cleans** (MMI-Hub#3975): CLI/plugin/marketplace env repairs, managed
17
- `.gitignore`, merged-branch / dead-worktree reap (including deferred IDE-locked removals), light board
18
- mechanical fixes, docs-index working-tree heal, and related full-lane checks. Secrets stay **out** of
19
- default doctor — use `mmi-cli vault secrets diff` when you need a catalog gap check.
16
+ By default this **heals and cleans** (MMI-Hub#3975): plugin env repairs, managed `.gitignore`,
17
+ merged-branch / dead-worktree reap (including deferred IDE-locked removals), light board mechanical
18
+ fixes, docs-index working-tree heal, and related full-lane checks. Secrets stay **out** of default
19
+ doctor — use `mmi-cli vault secrets diff` when you need a catalog gap check.
20
+
21
+ Doctor does **not** update the CLI or the host plugins (MMI-Hub#4954). The scheduled `mmi-updater`
22
+ reconciler is the single writer of those versions; doctor only REPORTS — the `mmi-cli` row names the
23
+ version gap and the `npm install -g @mutmutco/cli@<released>` that closes it, and the `fleet` row reads
24
+ the reconciler's journal (installed / expected / drift per surface).
20
25
 
21
26
  ## Flags
22
27
 
@@ -44,7 +49,7 @@ that surface alone (e.g. a secrets catalog review, or an interactive `board doct
44
49
 
45
50
  ## Notes
46
51
 
47
- - `/mmi-doctor` is the hygiene pass; `/resume` is the lighter read-only session open.
52
+ - `/mmi-doctor` is the hygiene pass; `/mmi-resume` is the lighter read-only session open.
48
53
  - Prefer one doctor run over hand-editing board items, gitignore blocks, or marketplace pins.
49
54
  - Doctor / `worktree list --stale` / `worktree gc` name the clone they audited. A green
50
55
  "no leaks" / "nothing to clean" is refused when another primary checkout of the same remotes
@@ -1,15 +1,15 @@
1
1
  ---
2
- name: resume
2
+ name: mmi-resume
3
3
  description: Open a session — self-check, repo status, and the next actionable board item in one pass.
4
4
  ---
5
5
 
6
- **Host-native invocation:** Claude `/mmi:resume` · Codex `$mmi:resume` · jervcode/Kimi `/skill:resume` · Kilo `skill` tool. A backticked `/name` in this doc names the matching workflow (this skill or a sibling), not a literal command.
6
+ **Host-native invocation:** Claude `/mmi:mmi-resume` · Codex `$mmi:mmi-resume` · jervcode/Kimi `/skill:mmi-resume` · Kilo `skill` tool. A backticked `/name` in this doc names the matching workflow (this skill or a sibling), not a literal command.
7
7
 
8
- # /resume — start of session
8
+ # /mmi-resume — start of session
9
9
 
10
10
  One flow to re-anchor at the top of a session: is the toolchain sound, what does this repo/worktree look
11
11
  like right now, and what is the single next thing worth doing. Read-only — it renders the picture and gets
12
- out of the way. `/mmi` is the board-only hello-to-work; `/resume` is the wider session open that folds in
12
+ out of the way. `/mmi` is the board-only hello-to-work; `/mmi-resume` is the wider session open that folds in
13
13
  the toolchain self-check and the current-branch snapshot.
14
14
 
15
15
  ## Step 0 — toolchain self-check
@@ -75,7 +75,7 @@ janitor prose. Catalog: `docs/Architecture/compute-at-read.md` (in MMI-Hub).
75
75
 
76
76
  ## Notes
77
77
 
78
- - `/resume` is read-only session orientation. It never claims, moves, or writes.
78
+ - `/mmi-resume` is read-only session orientation. It never claims, moves, or writes.
79
79
  - Board status moves are automatic (claim, PR open, merge). Never suggest a manual status move.
80
80
  - Slower, board-partition view → `/mmi`. Readiness-gate view for a new repo/first session → `/onboard`.
81
81
 
@@ -86,5 +86,5 @@ about? (Process only — never the user's code or task; e.g. a self-check that r
86
86
  snapshot that named the wrong branch.) If yes, file **one** lesson and move on; a clean run is silent
87
87
  (hard cap: one per run). It lands on the Hub board (deduped) and is fixed only via a reviewed PR — never
88
88
  edit the skill live; the retro is advisory, so if the call fails, note it and continue:
89
- `mmi-cli learning skill-lesson --skill resume --title "<what misfired>" --body "<what; evidence; proposed amendment>"`
89
+ `mmi-cli learning skill-lesson --skill mmi-resume --title "<what misfired>" --body "<what; evidence; proposed amendment>"`
90
90
  (never the retired flat `mmi-cli skill-lesson`).
@@ -70,7 +70,7 @@ Living current-state still comes from live verbs (`org schedules`, `board read`,
70
70
 
71
71
  ## Notes
72
72
 
73
- - `/onboard` is the first-session, readiness-first wrapper. Once a repo is known-good, `/resume` is the
73
+ - `/onboard` is the first-session, readiness-first wrapper. Once a repo is known-good, `/mmi-resume` is the
74
74
  faster daily open and `/mmi` is the board.
75
75
  - Everything here is read-only. The heavier setup (`/bootstrap`) is master-admin only.
76
76
 
@@ -125,7 +125,7 @@ git rev-list --count origin/main..origin/development
125
125
 
126
126
  Before local gates or `release --apply`, ensure the repo-local / PATH `mmi-cli` matches the released train
127
127
  path — a stale checkout (e.g. 2.32.0 while 2.32.4 is released) fails release gates with opaque errors.
128
- Self-heal in place without repo writes (heals run by default since #3975; the flag suppresses only
128
+ Read the gap without repo writes (plugin/env repairs run by default since #3975; the flag suppresses only
129
129
  mutations of the working tree you are about to release from):
130
130
  ```bash
131
131
  mmi-cli doctor --no-repo-writes
@@ -136,10 +136,11 @@ inverse is also true: a run can exit **0** while printing ✗ lines (report-only
136
136
  direction is a gate. Read the rows.
137
137
 
138
138
  - **Blocking:** a red `mmi-cli` / `Claude plugin` version line, or a reported `minClientVersion` gap.
139
- `--no-repo-writes` does not block the env heals the step above self-updates the npm global CLI
140
- (#3272) and reinstalls the plugin (#3282), suppressing only repo-file writes so the re-run should clear
141
- it. If a gap persists, fix it — `mmi-cli doctor`, or `npm install -g @mutmutco/cli`before
142
- continuing. Do **not** proceed to Step 0b while the installed CLI is behind the Hub's `minClientVersion`.
139
+ **Doctor does not update the CLI (#4954).** The scheduled `mmi-updater` owns npm installs now; doctor
140
+ REPORTS the lag (the `mmi-cli` row) and reads the reconciler's journal (the `fleet` row). So the remedy
141
+ here is the explicit install below — `npm install -g @mutmutco/cli@<released>`not a doctor re-run.
142
+ `--no-repo-writes` still heals the plugin install (#3282), suppressing only repo-file writes. Do **not**
143
+ proceed to Step 0b while the installed CLI is behind the Hub's `minClientVersion`.
143
144
  - **Not blocking:** every other red check is hygiene, not a train gate. Stale branches and scratch heal with
144
145
  a plain `mmi-cli doctor` (after the release); `plugin cache` needs a different verb,
145
146
  `mmi-cli plugin prune --apply` — saying doctor cleared it was wrong. Both still exit 1 until you run the
@@ -1,23 +0,0 @@
1
- {
2
- "name": "mmi",
3
- "version": "3.131.0",
4
- "description": "MMI workflow skills and org gates delivery.",
5
- "author": {
6
- "name": "MMI Future",
7
- "email": "69869555+jervaise@users.noreply.github.com"
8
- },
9
- "homepage": "https://github.com/mutmutco/MMI-Hub",
10
- "private": true,
11
- "type": "module",
12
- "keywords": [
13
- "mmi",
14
- "mutmutco",
15
- "pi-package",
16
- "jervcode"
17
- ],
18
- "pi": {
19
- "skills": [
20
- "../skills"
21
- ]
22
- }
23
- }