@mutmutco/kimi-plugin 4.1.20 → 4.2.0

package/.kimi-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "mmi",
-  "version": "4.1.20",
+  "version": "4.2.0",
   "description": "MMI workflow skills and org gates delivery.",
   "author": {
     "name": "MMI Future",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mutmutco/kimi-plugin",
-  "version": "4.1.20",
+  "version": "4.2.0",
   "description": "MMI workflow skills and org gates delivery.",
   "author": {
     "name": "MMI Future",

package/skills/bootstrap/SKILL.md

@@ -429,9 +429,10 @@ collaborator list + the per-branch allowlist are the record — no separate rost
   central workflows, so `MMI_APP_ID` / `MMI_APP_PRIVATE_KEY` live only on the Hub — a product repo seeds no
   App var/secret.
 - **Issue templates** — seed `.github/ISSUE_TEMPLATE/` (Bug · Feature · Task + `config.yml`).
-- **Merge settings (org canon)** — every repo: auto-merge on, squash on, delete-branch-on-merge on, so a
-  green allowlisted PR can land itself and never leaves a dead branch:
-  `gh api -X PATCH repos/$OWNER/$REPO -f allow_auto_merge=true -f allow_squash_merge=true -f delete_branch_on_merge=true`
+- **Merge settings (org canon)** — every repo: auto-merge on, squash on, automatic merged-branch deletion
+  off. A merged remote branch survives until delayed cleanup proves no open PR still uses it as a base
+  (#5789); deleting it at merge can irreversibly close stacked PRs:
+  `gh api -X PATCH repos/$OWNER/$REPO -f allow_auto_merge=true -f allow_squash_merge=true -F delete_branch_on_merge=false`
 - **Cursor environment** — `.cursor/environment.json` is retired org-wide (#2501): it caused Cursor to
   auto-spawn cloud agents nobody asked for. Bootstrap no longer seeds it and no
   repo should carry a tracked copy.

package/skills/release/SKILL.md

@@ -191,8 +191,9 @@ before any branch/tag mutation (#5666).** They read the repo's expected CI npm f
 (when the infra gate's exact node pin maps to a bundled npm, e.g. node 24.19.0 → npm 11.17.0) or, when
 gate.yml only declares a floating node major with no bundled npm, from the publish workflow's explicit npm pin
 (e.g. `npx --yes npm@11.17.0 pack` in `publish.yml`). Local `npm -v` must match that npm **major**; a
-mismatch refuses `--apply` with an align-local-npm remedy — the same class of failure the fold-failure notes
-below describe, but caught before a wasted apply.
+mismatch refuses `--apply` before any repository write. The receipt gives the supported npm-only repair
+(`npm install -g npm@<exact CI version>`), the `node -v && npm -v` verification, and tells you to rerun the
+same release command. This preserves Node and avoids routing a machine-global mutation through the train.
 
 **A local `npm ci` failure during the fold on a lockfile CI already accepted is an npm-major mismatch, not a
 bad lockfile (#4578).** Before touching the lockfile, compare toolchains:
@@ -624,8 +625,9 @@ mmi-cli oracle org project sync-info --apply   # omit --apply for the read-only
   - `checkout restoration failed while returning to …` / `origin/<branch> fast-forward failed` — the
     checkout or the pull errored. Read the appended git message; the release is unaffected.
 
-  `--resume` prints no `checkout:` clause at all, so after a resumed release check `git branch
-  --show-current` rather than assuming you were moved back.
+  `--resume` uses the same `checkout:` clause after every branch-mutating terminal path. Direct-track
+  resumes return to `development`; full-track resumes return to `rc`. A skipped restoration names the
+  dirty tree, checkout failure, or fast-forward failure and still leaves the shipped release intact.
 
 ## Step 6 — collect deploy verdict + report