@mutmutco/kimi-plugin 4.1.7 → 4.1.9

package/.kimi-plugin/plugin.json

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

package/skills/bootstrap/seeds/gate.template.yml

@@ -13,7 +13,7 @@ name: gate
 #   GATE_CMD           — the check command ({{GATE_CMD}})
 #   GATE_INSTALL_CMD   — the dependency-install command ({{GATE_INSTALL_CMD}})
 #   GATE_WORKDIR       — app working directory when not the repo root ({{GATE_WORKDIR}})
-#   GATE_CACHE_DEP_PATH— npm lockfile path for the setup-node cache ({{GATE_CACHE_DEP_PATH}})
+#   GATE_CACHE_DEP_PATH— npm lockfile path for runner-checkout heal ({{GATE_CACHE_DEP_PATH}})
 #   GATE_PY_VERSION    — Python version for setup-python ({{GATE_PY_VERSION}})
 #   GATE_MAX_SECONDS   — run-with-budget wall-clock ceiling in seconds ({{GATE_MAX_SECONDS}}); 300 default,
 #                        tighten per repo (org project set --var gate={"maxSeconds":N}) once measured (#3178)
@@ -65,9 +65,9 @@ jobs:
       # #5427: per-job npm cache under $RUNNER_TEMP — never the shared ~/.npm. Twelve mmi-live lanes
       # share the gha-runner home; npm hardlinks from that cache into node_modules, so one job's
       # `npm ci` can make another job's vitest/dist/workers/forks.js vanish mid-suite (Cannot find
-      # module). Job-local cache ⇒ no cross-job hardlinks. Must land BEFORE setup-node (`cache: npm`
-      # follows `npm config get cache`). Job-level `env:` cannot use the `runner` context — write
-      # via GITHUB_ENV from the shell `$RUNNER_TEMP` instead.
+      # module). Job-local cache ⇒ no cross-job hardlinks. Must land BEFORE setup-node (which reads
+      # `npm config get cache` for any explicit cache restore). Job-level `env:` cannot use the
+      # `runner` context — write via GITHUB_ENV from the shell `$RUNNER_TEMP` instead.
       - name: Isolate npm cache (per-job)
         shell: bash
         run: echo "NPM_CONFIG_CACHE=$RUNNER_TEMP/npm-cache" >> "$GITHUB_ENV"
@@ -93,12 +93,14 @@ jobs:
             done < "$offenders"
             exit 1
           fi
+      # #5660: self-hosted gates opt OUT of setup-node automatic npm cache restore unless a bounded
+      # cache policy is declared on runner-node-toolchain (cache + cache-restore-max-mb). Per-job
+      # NPM_CONFIG_CACHE above is the org default; unbounded Actions cache blobs can exhaust mmi-live
+      # disks mid-extract before the real check runs (Jerv-Hub SQLCipher gate, ~4.3GB restore).
       - if: ${{ '{{GATE_RUNTIME}}' == 'node' }}
         uses: mutmutco/MMI-Hub/.github/actions/runner-node-toolchain@{{GATE_RUNNER_SHA}}
         with:
           node-version: 24
-          cache: npm
-          cache-dependency-path: {{GATE_CACHE_DEP_PATH}}
       - if: ${{ '{{GATE_RUNTIME}}' == 'python' }}
         uses: actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065 # v5.6.0
         with: { python-version: '{{GATE_PY_VERSION}}' }