@mutmutco/pi-plugin 4.6.25 → 4.6.27

package/package.json

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

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

@@ -172,11 +172,15 @@ jobs:
       # MMI-Hub#5871: declare the npm MAJOR rather than inheriting whatever the runner's node bundles.
       # A bare major, never an exact patch (it goes stale and then prescribes downgrading operator
       # hosts toward it, #5862) and never `latest` (it takes the next major silently, #4782).
+      # MMI-Hub#9850: this single gate job is the designated hosted npm cache writer (auto saves only on a
+      # default-branch push), keyed on the one lockfile its install uses.
       - if: ${{ steps.development-gate.outputs.reuse != 'true' && ('{{GATE_RUNTIME}}' == 'node') }}
         uses: mutmutco/MMI-Hub/.github/actions/runner-node-toolchain@{{GATE_RUNNER_SHA}}
         with:
           node-version: 24
           npm-version: '12'
+          hosted-npm-cache: auto
+          hosted-npm-cache-lockfiles: {{GATE_CACHE_DEP_PATH}}
       - if: ${{ steps.development-gate.outputs.reuse != 'true' && ('{{GATE_RUNTIME}}' == 'python') }}
         uses: actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065 # v5.6.0
         with: { python-version: '{{GATE_PY_VERSION}}' }

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

@@ -37,11 +37,17 @@ jobs:
       - name: Isolate npm cache
         if: ${{ steps.development-gate.outputs.reuse != 'true' }}
         run: echo "NPM_CONFIG_CACHE=$RUNNER_TEMP/npm-cache" >> "$GITHUB_ENV"
+      # MMI-Hub#9850: the single gate job is the designated hosted npm cache writer (auto saves only on a
+      # default-branch push), keyed on both lockfiles its two installs below use.
       - uses: mutmutco/MMI-Hub/.github/actions/runner-node-toolchain@{{GATE_RUNNER_SHA}}
         if: ${{ steps.development-gate.outputs.reuse != 'true' }}
         with:
           node-version: 24
           npm-version: '12'
+          hosted-npm-cache: auto
+          hosted-npm-cache-lockfiles: |
+            package-lock.json
+            module/package-lock.json
       - run: npm ci --no-audit --no-fund
         if: ${{ steps.development-gate.outputs.reuse != 'true' }}
       - run: npm ci --prefix module --no-audit --no-fund

package/skills/bootstrap/seeds/suite-guide.template.md

@@ -114,7 +114,11 @@ requests like this should follow this structure, not prose guide."
      Before building visual A/B boards, use front-loaded **Impeccable v4.7.0** alongside **21st.dev MCP**
      (`https://21st.dev/api/mcp`; verbatim owner ruling: `"we don't need the mcp better design yet,
      impeccable and 21st is enough"`, dropping Better Design MCP) to study high-craft reference patterns,
-     layout proportions, and interaction details. Always translate inspired patterns into zero-GPU
+     layout proportions, and interaction details. Actually query the 21st.dev MCP; in the Phase 0
+     handoff/A-B brief, report the queries issued and returned component/pattern names and IDs
+     (where provided). If unreachable, report the exact error; if empty, report "no results".
+     Neither case supports a 21st inspiration claim. Never describe patterns as 21st-inspired
+     without this query/result record. Always translate inspired patterns into zero-GPU
      `@mutmutco/mmwork-ds` tokens (`--card-blur: none`, `--card-tint-dark: 0%`, `--card-tint-light: 0%`,
      sleek translucent glass cards) and Atomic Design layers; never copy raw third-party CSS/HTML or
      GPU-heavy effects. `MM-Inspo` is strictly a customer/tenant module inside the MM-Work suite, never

package/skills/org-guide/references/design.md

@@ -56,6 +56,11 @@ design work follows one harmonized **Front-Loaded Impeccable v4.7.0 + MM Artifac
   before choosing pieces; `exists` reports whether the requested guide exists. Never guess
   repo-root `node_modules/@mutmutco/mmwork-ds/docs/components/<Piece>.md`; component guides
   live in `<Piece>/guide.md`. No install/cache means capability remains unknown.
+  **Loading state comes from the content (#9851).** A page or component renders its loading state
+  from the same component tree as its real content: the kit Page `busy` or the component's own
+  loading state, drawing the real rows inert or hidden. Never hand-author a separate placeholder
+  skeleton kept in sync by hand. Every UI change checks the loading and loaded DOM structure match,
+  so an indicator cannot drift from the content it fronts.
 
 How the five pillars fit together (owner, 2026-10-25):
 
@@ -285,7 +290,11 @@ requests like this should follow this structure, not prose guide."
      Before building visual A/B boards, use front-loaded **Impeccable v4.7.0** alongside **21st.dev MCP**
      (`https://21st.dev/api/mcp`; verbatim owner ruling: `"we don't need the mcp better design yet,
      impeccable and 21st is enough"`, dropping Better Design MCP) to study high-craft reference patterns,
-     layout proportions, and interaction details. Always translate inspired patterns into zero-GPU
+     layout proportions, and interaction details. Actually query the 21st.dev MCP; in the Phase 0
+     handoff/A-B brief, report the queries issued and returned component/pattern names and IDs
+     (where provided). If unreachable, report the exact error; if empty, report "no results".
+     Neither case supports a 21st inspiration claim. Never describe patterns as 21st-inspired
+     without this query/result record. Always translate inspired patterns into zero-GPU
      `@mutmutco/mmwork-ds` tokens (`--card-blur: none`, `--card-tint-dark: 0%`, `--card-tint-light: 0%`,
      sleek translucent glass cards) and Atomic Design layers; never copy raw third-party CSS/HTML or
      GPU-heavy effects. `MM-Inspo` is strictly a customer/tenant module inside the MM-Work suite, never

package/skills/org-guide/references/work-and-releases.md

@@ -161,6 +161,8 @@ Production changes require explicit authorization from the authorized human.
 Read the selected release skill before operating the train. Let it choose versions, run gates,
 publish, deploy, and verify the resulting release. A refusal requires fixing its cause; do not
 finish by hand, bypass checks, or start a duplicate release.
+Finish the board before a release cut: every item of this cycle is merged and `Done` first; a queued
+lane is not a landed one.
 Versions: patch is the default for fixes and small compatible additions. Minor is a deliberate call
 for a real feature, with a one-line reason. Major is a new start or direction and needs the owner's
 fresh approval before tagging. A breaking change refuses until it is shimmed or made an approved

package/skills/release/SKILL.md

@@ -15,6 +15,8 @@ Read `mmi-cli oracle org project get {owner}/{repo} --json` and name the lane ([
 
 ## Preflight
 
+Board first: `mmi-cli oracle board read --repo <owner/repo>`; cut only once every in-flight item of this cycle is merged and `Done` ([train-common.md](train-common.md#board-first)).
+
 `mmi-cli devops train doctor --lane release --heal --json`; read it per [train-common.md](train-common.md#doctor).
 
 ## Apply

package/skills/release/train-common.md

@@ -1,7 +1,11 @@
-# Train skills: shared doctor, recovery, merge floor, report and retro
+# Train skills: shared board-first, doctor, recovery, merge floor, report and retro
 
 `/release`, `/rcand` and `/hotfix` read this one file (from a sibling skill: `../release/train-common.md`). Each skill keeps only what differs by lane.
 
+## Board first
+
+Before any release cut, read the repo's own board: `mmi-cli oracle board read --repo <owner/repo>`. Every in-flight item of this cycle — claimed, in review, queued in the autolander, or awaiting landing — must be merged and `Done` first. A queued lane is not a landed one: wait for its landing to report merge and board `Done`. The cut is the last step of a board cycle, never interleaved with pending landings; otherwise the version ships without them and needs a second cut. Standing backlog nobody is working is not in flight and does not block.
+
 ## Doctor
 
 The preflight JSON is on stdout alone: a stale CLI first prints its self-update notice on stderr and re-runs itself, so parse stdout only, never `2>&1`. Read `ready`, then `findings[]`: each carries `code`, `severity` (`blocker` · `warning` · `healed` · `info`), `source` (`local` · `origin`), `remedy` and `anchor`. `ready: false` → stop and quote every blocker's `code` and `remedy`; an unread origin is never green. The apply step (`release --apply`, `rcand --apply`, `hotfix start`, `hotfix release`) re-runs the doctor first, with heal on.