@mutmutco/pi-plugin 4.6.0 → 4.6.2

package/package.json

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

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

@@ -151,9 +151,11 @@ Impeccable **v4.7.0 / engine v0.1.16** details:
   `NODE_AUTH_TOKEN=$(gh auth token) npm view @mutmutco/mmwork-ds@<v> version --registry https://npm.pkg.github.com`;
   from a root without that line, pass the token directly —
   `npm view @mutmutco/mmwork-ds@<v> version --registry https://npm.pkg.github.com --//npm.pkg.github.com/:_authToken=$(gh auth token)`.
-  To see **which** kit versions are actually published, list the scope's GitHub Packages versions instead
-  of deriving it — `gh api '/orgs/mutmutco/packages/npm/mmwork-ds/versions?per_page=3' --jq '.[]|.name+" "+.created_at'`
-  (newest first, no npm token; #9264). That is the supported listing read:
+  To see **which** kit versions are actually published, run MMI-Hub's
+  `node scripts/kit-adopt.mjs --list-versions [--limit 5] [--json]` (#9426) instead of deriving it: it reads GitHub
+  Packages `/orgs/mutmutco/packages/npm/mmwork-ds/versions` (newest first, falling back to `npm view` against
+  `https://npm.pkg.github.com` with `GH_PACKAGES_READ_TOKEN`/`NODE_AUTH_TOKEN`), reports the local cache's latest
+  version, and never hits the `registry.npmjs.org` 404 of a bare `npm view @mutmutco/mmwork-ds` (#9264). That is the supported listing read:
   `mmi-cli devops packages` covers consumer adoption (`adopt-export`) only, so it never names a published
   version — never carry the packages API as a stopgap.
 - Boot once: `impeccable context --target <path>`; `init` captures PRODUCT.md, `document` maintains