@mutmutco/kilo-plugin 3.105.9 → 3.105.11

package/package.json

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

package/skills/hotfix/SKILL.md

@@ -73,9 +73,15 @@ 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`) are auto-resolved and regenerated by the bump step.
-Any other conflict: stop and report. Behavior changes still land on `development` first through a
-normal PR, then start another hotfix port from that merged fix — never hand-resolve onto main.
+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.
+
+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
+prescribes **one** main-clean synthesis development PR for the whole batch (pattern #4467) — not N
+serial ports. Behavior changes still land on `development` first through a normal PR, then rerun hotfix
+start from the port merge SHA(s) — never hand-resolve onto main.
 
 ## 2. Verify the hotfix PR
 

package/skills/worktree/SKILL.md

@@ -115,6 +115,11 @@ mmi-cli next               # the next actionable item
   `.worktrees/` are not the MMI path.
 - Multiple independent items → one worktree each, run in parallel, one PR per item (`/mmi` Leverage).
 - Never land to a protected/release branch here — that is `/rcand` and `/release`.
+- **Open the primary checkout in Cursor before land/gc hygiene (#4489).** If Cursor’s agent workspace is
+  still rooted at the slice worktree, `worktree land` / `worktree gc --apply` / doctor gc **refuse** to
+  delete that directory (and queue deferred removal) so the session is not orphaned. Optional explicit
+  contract: `export MMI_ACTIVE_WORKSPACE_ROOT="<Cursor workspace folder>"`. After switching Cursor to the
+  primary checkout, `mmi-cli worktree gc sweep-deferred` finishes cleanup.
 
 ## Retro — one check before you finish
 Before your final report, answer one question honestly: did **this skill's own instructions** misfire