@mutmutco/kilo-plugin 3.119.0 → 3.121.0

package/package.json

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

package/skills/release/SKILL.md

@@ -145,6 +145,15 @@ A different npm MAJOR (e.g. local 12 vs. CI's 11) resolves the same lockfile dif
 <pkg> from lock file` on a lockfile that is not actually broken. Align the local npm major
 (`npm install -g npm@<CI major>`) and re-run `npm ci` before rewriting or regenerating the lockfile.
 
+**A `npm ci was killed (signal SIGTERM)` failure during the fold is a cold npm cache, not a lockfile or
+toolchain problem (#4841).** The signature is the kill, not error text: no `Missing:` line, no lockfile
+complaint at all — the fold's child-process budget expired while a cold cache installed the full tree.
+The npm-major note above is inert here (majors match, the lockfile is fine), and following it tempts the
+one thing it warns against — regenerating the lockfile for a problem that has nothing to do with it.
+Warm the cache with a plain `npm ci` in the release checkout, then rerun the identical train command; the
+rollback the failed fold already ran makes the rerun clean. Never regenerate or rewrite the lockfile in
+response to a SIGTERM kill.
+
 **Then check the version yourself — do not rely on doctor having printed a row (#3674).** "Read the rows"
 resolves to "proceed" when the row is *absent*, and doctor's version row is conditional. On 2026-07-27 this
 step reported healthy with no version line while the installed CLI was 3.70.0 against a released 3.71.0;