@mutmutco/cli 3.31.0 → 3.33.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 (3) hide show
  1. package/README.md +10 -10
  2. package/dist/main.cjs +809 -1001
  3. package/package.json +2 -2
package/README.md CHANGED
@@ -27,22 +27,22 @@ mmi-cli doctor --json
27
27
 
28
28
  ## Main Commands
29
29
 
30
- - `mmi-cli 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.
30
+ - `mmi-cli 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.
31
31
  - `mmi-cli 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.
32
- - `mmi-cli secrets where|list|get|set|edit|rm|use|grant|revoke` manages two-tier project/org secrets without logging values; `where` prints the vault layout + well-known keys, and values move over TLS in the request body never an argument.
33
- - `mmi-cli project list|get|resolve|doctor|heal|readiness|set` reads and repairs Hub-owned v2 readiness state. `doctor --json` diagnoses central deploy/secrets readiness, `heal --apply` fixes only registry-owned defaults, and `readiness --update-issue` updates the repo's v2 readiness issue; `set` is master-only and supports explicit field unsets.
34
- - `mmi-cli registry org` reads org-level constants from the registry (`ORG#config`).
35
- - `mmi-cli oauth plan|verify` prints a repo's canonical Google OAuth URI set when the registry declares an `oauth` block and verifies the client is port-agnostic.
32
+ - `mmi-cli 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.
33
+ - `mmi-cli 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.
34
+ - `mmi-cli org config get` reads org-level constants from the registry (`ORG#config`).
35
+ - `mmi-cli org oauth plan|verify` prints a repo's canonical Google OAuth URI set when the registry declares an `oauth` block and verifies the client is port-agnostic.
36
36
  - `mmi-cli 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 issue link-child <parent> <child>` links two existing issues the same way.
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
- - `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.
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 worktree gc` dry-runs cleanup of merged/closed PR branches + stale tracking refs.
40
40
  - `mmi-cli board read|claim|show|move|done` reads and moves GitHub Project work.
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 --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).
41
+ - `mmi-cli 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.
42
+ - `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).
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
- - `mmi-cli access audit` checks collaborator roles and train-branch allowlists.
45
+ - `mmi-cli org access audit` checks collaborator roles and train-branch allowlists.
46
46
  - `mmi-cli doctor` checks GitHub auth, repo config, CLI availability, plugin install/config/version state, and stale MMI plugin cache dirs, auto-repairing the safe gaps.
47
47
 
48
48
  Hub API calls do not send the raw GitHub token on every request. The CLI exchanges it at `/auth/session`
@@ -61,7 +61,7 @@ lanes, personal workflow). The 2026-07 audit (#2994) pinned the boundary; these
61
61
  they don't get re-derived or re-litigated per session:
62
62
 
63
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
64
+ `worktree list --stale`, and `worktree gc` own discovery and removal of branches/worktrees/stages. `jerv-cli
65
65
  worktree sweep` touches ONLY worktrees owned by that session's leases — it never classifies or
66
66
  removes org worktrees at large. Never widen either side toward the other.
67
67
  - **Session observability flows org → personal, never back.** `mmi-cli report session` exists to feed