@mutmutco/kimi-plugin 4.0.18 → 4.1.1

package/.kimi-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "mmi",
-  "version": "4.0.18",
+  "version": "4.1.1",
   "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.0.18",
+  "version": "4.1.1",
   "description": "MMI workflow skills and org gates delivery.",
   "author": {
     "name": "MMI Future",

package/skills/epic/SKILL.md

@@ -99,8 +99,11 @@ part of the batch), use the inverse-friendly single link:
 mmi-cli oracle issue link-child <parent> <child>
 ```
 
-Each child is now a parallel item — fan them out one worktree + PR each. **When the last child merges,
-close the umbrella** (its board `Done` follows automatically).
+Each child is now a parallel item — fan them out one worktree + PR each. On Windows, set
+`git config core.longpaths true` on the main checkout before the first `git worktree add` (#5499). When
+several linked worktrees belong to the same clone, serialize `git branch -m` / other ref renames (or retry
+serially on `.tmp-renamed-log`) so parallel agents do not race the shared ref log (#5485). **When the last
+child merges, close the umbrella** (its board `Done` follows automatically).
 
 ## Notes
 

package/skills/hotfix/SKILL.md

@@ -83,9 +83,9 @@ the main-base PR. Do not duplicate those steps with raw branch commands, manual
 GitHub PR creation.
 
 Conflicts confined to regenerable distribution / version-fold paths (e.g. Hub `distribution-bom.json`,
-locked plugin manifests, consumer `package.json`) — and, for hub-serverless + registry-publish, shipped
-skill roots `skills/` and `.kilo-plugin/skills/` (#4363 / #4471) — are auto-resolved (take the picked
-side) and regenerated by the bump/fold step. Source TS under `src/` / `cli/src/` is never auto-resolved.
+locked plugin manifests, consumer `package.json`) — and, for hub-serverless + registry-publish, the
+canonical skill root `skills/` (#4363 / #4471) — are auto-resolved (take the picked side) and regenerated
+by the bump/fold step. Source TS under `src/` / `cli/src/` is never auto-resolved.
 
 Before cutting the hotfix branch, `hotfix start` preflights every `--from` pick on an accumulating
 `origin/main` tree (#4472). If any pick would hard-stop, it refuses with every failing pick and path and

package/skills/mmi/SKILL.md

@@ -403,7 +403,11 @@ workspace mechanics:
   (`Closes #…, #…`). When an issue must stay open (HOLD/prep), never write `Does not close #N` — GitHub
   still closes it; use `Part of #N` / `Refs #N` / `leaves #N open` only (JC#495).
 - **Parallel:** run independent work concurrently, **one PR per item**. If two would touch the same file,
-  serialize them or fold them into a batch instead.
+  serialize them or fold them into a batch instead. On Windows, set `git config core.longpaths true` on the
+  main checkout before the first `git worktree add` (#5499; see `docs/Architecture/worktrees.md`). Linked
+  worktrees of one clone still share `.git`: serialize `git branch -m` / other ref renames across those
+  worktrees, or retry serially when the error names `.git/logs/refs/.tmp-renamed-log` (#5485; see
+  `docs/Architecture/worktrees.md`).
 - **Background:** run off the hot path (a background task or CI job); poll with `/loop` if useful. Bound it
   — never block silently.
 - **Split:** keep the original as the umbrella; file each child as a **native sub-issue** of it with

package/skills/onboard/SKILL.md

@@ -61,7 +61,7 @@ Before treating `docs/**` as current-state, teach the Hub door (Hub#4133 / #4148
 
 ```bash
 mmi-cli oracle repo-index search <path-or-symbol-or-meaning>   # Hub cloud pointers (default)
-mmi-cli oracle repo-index search "where …" --semantic          # Titan meaning over embeddings
+mmi-cli oracle repo-index search "where …" --semantic          # BGE meaning over embeddings
 mmi-cli oracle repo-index status --cloud                        # is the estate index live?
 ```
 

package/skills/stage/SKILL.md

@@ -116,18 +116,29 @@ gated at the **Cloudflare edge** (#1761). The CLI detects your IP, dispatches th
 rule scoped to your dev host + IP). The box no longer IP-gates dev. No SSH from your machine; everything
 moves through the central workflows.
 
+**Deploy-model preflight (#5466 / #5467).** `/stage --live` is **not** generally available. Read
+`deployModel` first (`mmi-cli oracle org project get {owner}/{repo}` → `deployModel`, or the dry
+`mmi-cli stage --live --json` refusal). It applies only to **`tenant-container`** repos (the same
+model the Hub tenant-deploy + tenant-control gates require). **`registry-publish` is not applicable**
+for live stages — nor are hub-serverless, solo-container, static-cdn, content, or none. For an
+unsupported model the dry plan refuses **before** offering `--apply` / `--down`; do not invent a
+tenant deploy or gate.
+
 ```bash
-mmi-cli stage --live           # dry-run plan
+mmi-cli stage --live           # dry-run plan (refuses when deployModel is not tenant-container)
 mmi-cli stage --live --apply   # deploy + gate your IP at the Cloudflare edge
 ```
 
-Tear it down when done — the runtime stops and the Cloudflare edge gate is removed:
+Tear it down when done — **only when `--apply` actually created a runtime or gate**. The runtime stops
+and the Cloudflare edge gate is removed:
 
 ```bash
 mmi-cli stage --live --down --apply
 ```
 
-Personal dev stages only — rc/live environments still move exclusively through the promotion train.
+If apply never landed (unsupported model, failed dispatch, or you never ran `--apply`), `--down` is a
+**safe no-op** — do not promise teardown of a stage that was never created. Personal dev stages only —
+rc/live environments still move exclusively through the promotion train.
 
 ## Step 3 — report
 
@@ -136,7 +147,9 @@ The stage URL, what's running (server + tools), the workspace path (`tmp/stage/`
 ## Notes
 
 - `/stage` is local — no AWS, no deploy, no board or version effect. The one cloud exception is
-  `--live`: an on-demand **dev** stage of your branch, gated to your IP at the Cloudflare edge (above).
+  `--live`: an on-demand **dev** stage of your branch for **`tenant-container`** repos only, gated to
+  your IP at the Cloudflare edge (above). Preflight `deployModel` before offering it; `registry-publish`
+  and other models have no live stage.
 - Remote rc/live environments move only through `/rcand`, `/release`, and `/hotfix`.
 - Everything is gitignored; `/stage` never produces a tracked change.
 - **Playwright MCP output goes to `tmp/`**, never the repo root: if you drive the Playwright MCP server,