@mutmutco/cli 3.27.1 → 3.29.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.
- package/README.md +21 -2
- package/dist/main.cjs +7626 -6631
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -37,9 +37,9 @@ mmi-cli doctor --json
|
|
|
37
37
|
- `mmi-cli report` files a friction report on the Hub board with your GitHub identity, deduping against the open `report`-labeled issues (a confident duplicate becomes a +1 comment, not a new issue). No repo-local `.env`, no API key, no copied report script.
|
|
38
38
|
- `mmi-cli skill-lesson --skill <name>` files a **skill-lesson** on the Hub board when a skill's own instructions misfire — the cross-skill generalization of grind's Retro. GitHub identity, its own `skill-lesson` label + dedup pool (a confident duplicate becomes a +1 comment), and a footer pinning the source checkout + plugin SHA. Advisory: the fix lands via a reviewed PR to the skill in MMI-Hub, never a live edit.
|
|
39
39
|
- `mmi-cli pr create`, `pr merge`, and **`pr land`** (train probe → checks-wait → merge --auto — #1440) create/land PRs with branch/worktree cleanup; `--preserve-worktree` keeps the local worktree/stage/branch for explicit active batches (#1888). **`mmi-cli ci audit`** / **`ci reconcile`** scan fleet merge-readiness; `mmi-cli gc` dry-runs cleanup of merged/closed PR branches + stale tracking refs.
|
|
40
|
-
- `mmi-cli board read|claim|show|move|done
|
|
40
|
+
- `mmi-cli board read|claim|show|move|done` reads and moves GitHub Project work.
|
|
41
41
|
- `mmi-cli tenant control <owner/repo> <stage> <status|start|stop|restart>` runs bounded dev/rc box control for project-admins through the Hub API; main remains master-only.
|
|
42
|
-
- `mmi-cli stage`, `stage start`, `stage stop`, `stage run`, and `port-range <repo>` manage the local gitignored stage and its port block; `stage
|
|
42
|
+
- `mmi-cli stage`, `stage start`, `stage stop`, `stage run`, and `port-range <repo>` manage the local gitignored stage and its port block; `stage --live` is the personal IP-gated cloud dev stage. Remote rc/live environments move only via `/rcand` · `/release` · `/hotfix` (the old `stage-live` explainer command is retired, #2997).
|
|
43
43
|
- `mmi-cli rcand`, `release`, and `hotfix` render guarded train plans; product trains trigger the Hub's central tenant deployer, while MMI-Hub releases directly from `development` to `main`.
|
|
44
44
|
- `mmi-cli bootstrap`, `bootstrap verify`, and `bootstrap apply` plan, audit, and seed repo onboarding.
|
|
45
45
|
- `mmi-cli access audit` checks collaborator roles and train-branch allowlists.
|
|
@@ -53,6 +53,25 @@ new Hub session instead of reusing the previous user's bearer credential.
|
|
|
53
53
|
|
|
54
54
|
Run `mmi-cli --help` or `mmi-cli <command> --help` for the full command reference.
|
|
55
55
|
|
|
56
|
+
## Capability seams — mmi-cli vs jerv-cli (#3000)
|
|
57
|
+
|
|
58
|
+
`mmi-cli` is the **org** CLI (rules delivery, board/issue/PR work, registry, secrets, release train,
|
|
59
|
+
deploy plane). `jerv-cli` is Suphi's **personal** power-tools CLI (Jerv's Memory continuity, fusion
|
|
60
|
+
lanes, personal workflow). The 2026-07 audit (#2994) pinned the boundary; these are the seams, so
|
|
61
|
+
they don't get re-derived or re-litigated per session:
|
|
62
|
+
|
|
63
|
+
- **Worktree cleanup ownership.** mmi-cli is the SSOT for the git worktree lifecycle: `worktree land`,
|
|
64
|
+
`worktree list --stale`, and `gc` own discovery and removal of branches/worktrees/stages. `jerv-cli
|
|
65
|
+
worktree sweep` touches ONLY worktrees owned by that session's leases — it never classifies or
|
|
66
|
+
removes org worktrees at large. Never widen either side toward the other.
|
|
67
|
+
- **Session observability flows org → personal, never back.** `mmi-cli report session` exists to feed
|
|
68
|
+
`jerv-cli save` (a machine summary of touched issues/PRs/worktrees/deploys for a memory save or
|
|
69
|
+
handoff). jerv-cli never writes org state; mmi-cli never writes Jerv's Memory.
|
|
70
|
+
- **Intentional duplicates — keep both.** `skill-lesson` exists in both CLIs by design: each files to
|
|
71
|
+
its own owning board (mmi-cli/MMI plugin → MMI-Hub; jerv-cli/PowerTools plugin → Jerv-PowerTools),
|
|
72
|
+
per the friction-routing rule. `doctor`, `whoami`, `commands`, and `explain` are per-CLI meta
|
|
73
|
+
infrastructure; a shared library across the two repos is not worth the version churn.
|
|
74
|
+
|
|
56
75
|
## Repo-Local Fallback
|
|
57
76
|
|
|
58
77
|
When working inside an `MMI-Hub` checkout before npm is available, use the committed bundle directly:
|