@mutmutco/kilo-plugin 3.105.11 → 3.106.0

package/package.json

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

package/scripts/secret-echo-lint.mjs

@@ -91,21 +91,28 @@ function checkBashPrint(segment) {
 }
 
 function checkPsPrint(segment) {
+  // PowerShell accepts both $env:SECRET_VAR and ${env:SECRET_VAR}; keep one matcher so the braced form
+  // cannot bypass the same output checks as the ordinary form.
+  const envReference = /\$(?:\{env:(\w+)\}|env:(\w+))/gi;
+  const envName = (match) => match[1] ?? match[2];
+
   // Write-Output / Write-Host / echo with $env:SECRET_VAR
   if (/\b(?:Write-Output|Write-Host|echo)\b/i.test(segment)) {
-    for (const m of segment.matchAll(/\$env:(\w+)/gi)) {
-      if (isSecretName(m[1])) {
-        return { block: true, reason: `Write/echo of $env:${m[1]} prints a secret-named env var` };
+    for (const m of segment.matchAll(envReference)) {
+      const name = envName(m);
+      if (isSecretName(name)) {
+        return { block: true, reason: `Write/echo of $env:${name} prints a secret-named env var` };
       }
     }
   }
 
   // $env:SECRET_VAR in output position (start of command or after pipe, not assignment LHS)
-  for (const m of segment.matchAll(/(?:^|[;&|]\s*)\$env:(\w+)/gi)) {
+  for (const m of segment.matchAll(new RegExp(`(?:^|[;&|]\\s*)${envReference.source}`, 'gi'))) {
+    const name = envName(m);
     const after = segment.slice(m.index + m[0].length);
     if (/^\s*=(?!=)/.test(after)) continue; // assignment LHS, not output
-    if (isSecretName(m[1])) {
-      return { block: true, reason: `$env:${m[1]} in output position prints a secret-named env var` };
+    if (isSecretName(name)) {
+      return { block: true, reason: `$env:${name} in output position prints a secret-named env var` };
     }
   }
 

package/skills/hotfix/SKILL.md

@@ -139,6 +139,20 @@ merged into `development`; the fold is regenerated on a branch cut from `develop
 reported `development fold port FAILED`, follow the manual remedy it named; never improvise a merge from
 `main`.
 
+### Catalog-lockstep vs development prepare (#4517)
+
+Hub docs catalog-lockstep refuses PRs into `development` that advance
+`.claude-plugin/marketplace.json` ahead of `origin/main`. That gate is correct for main-anchored catalog
+truth. When Publish-Truth / a version bump must advance the marketplace, do **not** land
+`release-distribution prepare` as a development PR — use this hotfix door:
+
+1. `mmi-cli hotfix start --from <merged-dev-pr-or-sha>` (prepare + distribution bump on `hotfix/vX.Y.Z` from `main`)
+2. merge the hotfix PR → `mmi-cli hotfix release vX.Y.Z` (publish)
+3. land the automatic `hotfix-fold/<tag>` development fold PR (or follow its printed remedy)
+
+A development prepare PR that only exists to move marketplace ahead of main will keep failing
+catalog-lockstep; that is not a false red — switch to the hotfix path above.
+
 ## Retro
 
 If this skill's instructions themselves misfired, file one deduplicated lesson and continue:

package/skills/worktree/SKILL.md

@@ -25,8 +25,9 @@ The issue-ref form derives `<issue-number>-<short-slug>`, assigns the item, and
 
 `worktree create` also leases the tree to the **creating session** (#4328). A later `jerv-cli lane submit
 --dir` (or any governed seat) refuses an already-held host lease and will not commandeer it. Before handing
-the tree to a governed seat, release that lease first: discover it with `jerv-cli lease list`, then
-`jerv-cli lease close <leaseId>`.
+the tree to a governed seat, release that lease first — safe once the session's own edits in that tree are
+committed and pushed: `jerv-cli lease close --ref <worktree path>` (closes every lease on that ref; no id
+lookup needed). To inspect what's held before closing, `jerv-cli lease list` shows id, ref, and owner.
 
 ## Step 2 — claim + work
 
@@ -58,9 +59,14 @@ with it. Stage, commit, and push as separate commands.
 
 ## Step 4 — land + clean up
 
-Under standing go (green CI, CI-gated PR) land to `development`:
+Under standing go (green CI, CI-gated PR) land to `development`. **Invoke `mmi-cli pr land` from the
+primary checkout** (or any cwd that is not the PR worktree) (#4549). Landing while cwd is still inside
+the worktree that cleanup removes can merge successfully and still exit 1 with
+`cleanupError: … Unable to read current working directory` — post-merge `gh`/`git` follow-ups then have
+no readable cwd even when removal itself chdir'd away (#4140).
 
 ```bash
+cd <primary-checkout>   # e.g. the main MMI-Hub clone — not the slice worktree
 mmi-cli pr land <PR-number>
 ```
 
@@ -79,12 +85,11 @@ are standing in):
 mmi-cli worktree land --apply
 ```
 
-**Cwd-safe land (#4140):** `worktree land --apply` (what `pr land` runs) is designed to be invoked from
-inside the worktree you are landing. Before removal it releases the process cwd to the primary checkout
-(#1444/#2747) — on Windows, leaving cwd inside the target tree makes `rmdir` fail with `EBUSY` and leaks
-branch refs. You do not need to `cd` out first; if removal still fails (IDE lock, antivirus), the deferred
-sweep retries from a safe cwd. Prefer the primary checkout cwd only when you are running `worktree land`
-manually outside `pr land`.
+**Cwd-safe removal (#4140):** `worktree land --apply` (what `pr land` runs) releases the process cwd to
+the primary checkout before deleting the tree (#1444/#2747) so Windows `rmdir` is not `EBUSY`. That does
+**not** replace the agent rule above: still start `pr land` from the primary checkout (#4549). Prefer
+primary cwd also when running `worktree land` manually outside `pr land`. If removal still fails (IDE
+lock, antivirus), the deferred sweep retries from a safe cwd.
 
 **No main lineage on a squashable development PR (#4365 / #4371):** never `git merge -s ours` (or otherwise
 merge) a main-parented port commit into a development PR that will squash. Squash folds second-parent