@mutmutco/cli 3.139.0 → 3.139.2

package/README.md

@@ -1,6 +1,6 @@
 # @mutmutco/cli
 
-The command-line engine for MMI Future org tooling. It delivers the org-managed `.gitignore` block, reads and claims GitHub Project work, and exposes the model-agnostic commands used by the MMI plugin and non-Claude agents. (Personal agent guides — `AGENTS.md` / `CLAUDE.md` — are developer-owned and gitignored; the CLI does not deliver, overwrite, or fan them out — the whole-spine fanout is retired.)
+The command-line engine for MMI Future org tooling. It delivers the org-managed `.gitignore` block, reads and claims GitHub Project work, and exposes the model-agnostic commands used by the MMI plugin and non-Claude agents. Personal agent guides (`AGENTS.md` / `CLAUDE.md`) are developer-owned and gitignored.
 
 This package is published from [mutmutco/MMI-Hub](https://github.com/mutmutco/MMI-Hub). The release train derives its version, publication target, and artifact identity from the shared surface registry and bill of materials alongside every active host adapter.
 
@@ -27,7 +27,7 @@ mmi-cli doctor --json
 
 ## Main Commands
 
-- `mmi-cli devops org rules gitignore [--write]` verifies (or heals) this repo's org-managed `.gitignore` block. The retired `rules sync` no longer exists — personal agent guides (`AGENTS.md` / `CLAUDE.md`) are developer-owned and gitignored, never org-delivered.
+- `mmi-cli devops org rules gitignore [--write]` verifies or updates this repo's org-managed `.gitignore` block; personal agent guides remain developer-owned.
 - `mmi-cli devops bootstrap org-ruleset` drift-checks the codified org no-agent-files push ruleset (`mmi-no-agent-files-org`) against the live org config; read-only, never mutates.
 - `mmi-cli vault secrets where|list|set|rm|use` manages the full own-project vault for project-admins without logging values; org-infra remains master-gated and exactly grantable. `where` prints the layout, and values move only through stdin/TLS/keyless command injection—never an argument or stdout. Operational grant/catalog commands are available through all-command discovery.
 - `mmi-cli oracle org project list|get|doctor|heal|set` reads and repairs the Hub v3 registry; `org project deploy get` resolves deploy coordinates. `doctor --json` diagnoses central deploy/secrets readiness, `heal --apply` fixes only registry-owned defaults, and `set` is master-only except for the explicit project-admin self-service routes.
@@ -36,10 +36,10 @@ mmi-cli doctor --json
 - `mmi-cli oracle issue create` creates typed, prioritized GitHub issues (priority sets the board field, not a label) and queues related-issue discovery. `--parent <ref>` files the new issue as a native GitHub sub-issue of a parent (works cross-repo); `mmi-cli oracle issue link-child <parent> <child>` links two existing issues the same way.
 - `mmi-cli learning 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.
 - `mmi-cli learning 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.
-- `mmi-cli devops 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 devops ci audit`** / **`ci reconcile`** scan fleet merge-readiness; `mmi-cli worktree gc` dry-runs cleanup of merged/closed PR branches + stale tracking refs.
+- `mmi-cli devops pr create`, `pr merge`, and **`pr land`** (train probe → checks-wait → merge --auto — #1440) create and land PRs. **`mmi-cli devops ci audit`** / **`ci reconcile`** scan fleet merge-readiness. Local workspace lifecycle is host-owned.
 - `mmi-cli oracle board read|claim|show|move|done` reads and moves GitHub Project work.
 - `mmi-cli devops runtime 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.
-- `mmi-cli stage`, `stage start`, `stage stop`, `stage run`, and `stage 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).
+- `mmi-cli stage`, `stage start`, `stage stop`, `stage run`, and `stage 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`.
 - `mmi-cli devops 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`.
 - `mmi-cli devops bootstrap`, `bootstrap verify`, and `bootstrap apply` plan, audit, and seed repo onboarding.
 - `mmi-cli oracle org access audit` checks collaborator roles and train-branch allowlists.
@@ -51,16 +51,10 @@ registry, secrets, train-authority, and tenant-control calls until it nears expi
 The cache is bound to the current local GitHub token fingerprint, so switching `gh auth` users forces a
 new Hub session instead of reusing the previous user's bearer credential.
 
-Run `mmi-cli --help` or `mmi-cli <command> --help` for the full command reference.
-The machine manifest (`mmi-cli commands --json`) also names the implementation module and consumer for
-every command. That inventory is checked when the runtime tree is assembled, so a sixth command domain
-cannot land as an ownerless block in the registration entrypoint.
-
-## Removed compatibility aliases
-
-- `mmi-cli board open` is retired; use `mmi-cli oracle board show`.
-- `mmi-cli org schedules lift` is retired after its one-release migration window; use
-  `mmi-cli harbour org schedules register`.
+Run `mmi-cli --help` for the task map, `mmi-cli commands --json` for bounded machine routes, and
+`mmi-cli explain <command> --json` for exact arguments/options/examples. The exhaustive
+`mmi-cli commands --all --json` manifest names every implementation module and consumer. That inventory
+is checked when the runtime tree is assembled, so a sixth command domain cannot land ownerless.
 
 ## Capability seams — mmi-cli vs jerv-cli (#3000)
 
@@ -69,16 +63,14 @@ deploy plane). `jerv-cli` is Suphi's **personal** power-tools CLI (Jerv's Memory
 lanes, personal workflow). The 2026-07 audit (#2994) pinned the boundary; these are the seams, so
 they don't get re-derived or re-litigated per session:
 
-- **Worktree cleanup ownership.** mmi-cli is the SSOT for the git worktree lifecycle: `worktree land`,
-  `worktree list --stale`, and `worktree gc` own discovery and removal of branches/worktrees/stages. `jerv-cli
-  worktree sweep` touches ONLY worktrees owned by that session's leases — it never classifies or
-  removes org worktrees at large. Never widen either side toward the other.
+- **Workspace ownership.** The agent and host own local worktree lifecycle. MMI carries issue, PR, CI,
+  merge, and board facts only; its retained worktree verbs are legacy compatibility and never set the
+  workspace policy.
 - **Session observability flows org → personal, never back.** `mmi-cli learning report session` exists to feed
   `jerv-cli save` (a machine summary of touched issues/PRs/worktrees/deploys for a memory save or
   handoff). jerv-cli never writes org state; mmi-cli never writes Jerv's Memory.
 - **Intentional duplicates — keep both.** `skill-lesson` exists in both CLIs by design: each files to
-  its own owning board (mmi-cli/MMI plugin → MMI-Hub; jerv-cli/PowerTools plugin → Jerv-PowerTools),
-  per the friction-routing rule. `doctor`, `whoami`, `commands`, and `explain` are per-CLI meta
+  its own owning board. `doctor`, `whoami`, `commands`, and `explain` are per-CLI meta
   infrastructure; a shared library across the two repos is not worth the version churn.
 
 ## Repo-Local Fallback