@mutmutco/codex-plugin 4.3.13 → 4.3.15

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "mmi",
-  "version": "4.3.13",
+  "version": "4.3.15",
   "mmiCompat": "4.x",
   "description": "MMI workflow skills and org gates delivery.",
   "author": {

package/package.json

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

package/skills/bootstrap/SKILL.md

@@ -550,6 +550,7 @@ Before your final report, answer one question honestly: did **this skill's own i
 this run — ambiguous wording, a misleading message, or an environment failure it should have warned
 about? (Process only — never the user's code or task; e.g. an ambiguous seed, registry, or OIDC step, or
 a guard that fired on a healthy repo.) If yes, file **one** lesson and move on; a clean run is silent
-(hard cap: one per run). It lands on the Hub board (deduped) and is fixed only via a reviewed PR — never
-edit the skill live; the retro is advisory, so if the call fails, note it and continue:
-`mmi-cli learning skill-lesson --skill bootstrap --title "<what misfired>" --body "<what; evidence; proposed amendment>"`
+(hard cap: one per run). It lands on the owning board (deduped) and is fixed only via a reviewed PR — never
+edit the skill live; the retro is advisory, so if the call fails, note it and continue. In-session, call the
+`jerv_learning_note` tool with origin retro; the machine fallback is:
+`jervcode learn --origin retro --surface skills --title "bootstrap: <what misfired>" --body "<what; evidence; proposed amendment>"`

package/skills/epic/SKILL.md

@@ -123,6 +123,7 @@ Before your final report, answer one question honestly: did **this skill's own i
 this run — ambiguous wording, a misleading message, or an environment failure it should have warned
 about? (Process only — never the user's code or task; e.g. a batch schema that rejected a valid row, or a
 link that attached to the wrong parent.) If yes, file **one** lesson and move on; a clean run is silent
-(hard cap: one per run). It lands on the Hub board (deduped) and is fixed only via a reviewed PR — never
-edit the skill live; the retro is advisory, so if the call fails, note it and continue:
-`mmi-cli learning skill-lesson --skill epic --title "<what misfired>" --body "<what; evidence; proposed amendment>"`
+(hard cap: one per run). It lands on the owning board (deduped) and is fixed only via a reviewed PR — never
+edit the skill live; the retro is advisory, so if the call fails, note it and continue. In-session, call the
+`jerv_learning_note` tool with origin retro; the machine fallback is:
+`jervcode learn --origin retro --surface skills --title "epic: <what misfired>" --body "<what; evidence; proposed amendment>"`

package/skills/hotfix/SKILL.md

@@ -95,8 +95,8 @@ Title first, verdict first. Name the resolved tag (never a placeholder like `vX.
 
 ## Retro
 
-Before the final report, answer one question honestly: did this skill's own instructions misfire this run — ambiguous wording, a misleading message, or an environment failure it should have warned about? Process only, never the user's code or task. If yes, file one lesson and move on; a clean run is silent (hard cap: one per run). It lands on the Hub board, deduplicated, and is fixed only through a reviewed PR — never edit the skill live. The retro is advisory: if the call fails, note it and continue. The amendment itself stays reference-free: the skill-drift gate rejects issue references in any section outside Merge floor, so carry the evidence in words or point at the guide entry — never inline reference markers.
+Before the final report, answer one question honestly: did this skill's own instructions misfire this run — ambiguous wording, a misleading message, or an environment failure it should have warned about? Process only, never the user's code or task. If yes, file one lesson and move on; a clean run is silent (hard cap: one per run). It lands on the owning board, deduplicated, and is fixed only through a reviewed PR — never edit the skill live. The retro is advisory: if the call fails, note it and continue. In-session, call the `jerv_learning_note` tool with origin retro and let it queue the lesson; the command below is the machine fallback. The amendment itself stays reference-free: the skill-drift gate rejects issue references in any section outside Merge floor, so carry the evidence in words or point at the guide entry — never inline reference markers.
 
 ```bash
-mmi-cli learning skill-lesson --skill hotfix --title "<what misfired>" --body "<what; evidence; proposed amendment>"
+jervcode learn --origin retro --surface skills --title "hotfix: <what misfired>" --body "<what; evidence; proposed amendment>"
 ```

package/skills/rcand/SKILL.md

@@ -73,8 +73,8 @@ Title first, verdict first. Name the resolved tag (never a placeholder like `vX.
 
 ## Retro
 
-Before the final report, answer one question honestly: did this skill's own instructions misfire this run — ambiguous wording, a misleading message, or an environment failure it should have warned about? Process only, never the user's code or task. If yes, file one lesson and move on; a clean run is silent (hard cap: one per run). It lands on the Hub board, deduplicated, and is fixed only through a reviewed PR — never edit the skill live. The retro is advisory: if the call fails, note it and continue. The amendment itself stays reference-free: the skill-drift gate rejects issue references in any section outside Merge floor, so carry the evidence in words or point at the guide entry — never inline reference markers.
+Before the final report, answer one question honestly: did this skill's own instructions misfire this run — ambiguous wording, a misleading message, or an environment failure it should have warned about? Process only, never the user's code or task. If yes, file one lesson and move on; a clean run is silent (hard cap: one per run). It lands on the owning board, deduplicated, and is fixed only through a reviewed PR — never edit the skill live. The retro is advisory: if the call fails, note it and continue. In-session, call the `jerv_learning_note` tool with origin retro and let it queue the lesson; the command below is the machine fallback. The amendment itself stays reference-free: the skill-drift gate rejects issue references in any section outside Merge floor, so carry the evidence in words or point at the guide entry — never inline reference markers.
 
 ```bash
-mmi-cli learning skill-lesson --skill rcand --title "<what misfired>" --body "<what; evidence; proposed amendment>"
+jervcode learn --origin retro --surface skills --title "rcand: <what misfired>" --body "<what; evidence; proposed amendment>"
 ```

package/skills/release/SKILL.md

@@ -52,7 +52,7 @@ Read the receipt at `$r`, never the exit code (exit `2` = shipped with a follow-
 - `workflowRuns` — every run on the release SHA (deploy-model runs, any `push: main` deploy, the repo's own `gate`). Watch each non-success entry to conclusion: `gh run watch <run-id> --repo {owner}/{repo} --exit-status`. Name which run is red: `deploy.yml` / `publish.yml` / `tenant-deploy.yml` / `jerv-gateway` is a deploy or publish verdict; a `gate` push run is ordinary CI sharing the SHA.
 - An all-green external watch never folds the ledger: publish/deploy/alignment legs stay `pending` in the train's ledger and the NEXT train's doctor refuses with `ledger-pending`. After every watched leg has concluded, fold the ledger live before declaring the cut done or starting any new train: `mmi-cli devops release --resume --watch --json --out <fresh-receipt>`.
 - `announceNote` (Hub) — `announced`, `skipped`, or the failure note.
-- `devRollForward` / `rcAlignment` — `pushed`, or `pr-pending` with the alignment PR to land by true merge (Merge floor).
+- `devRollForward` / `rcAlignment` — `pushed`, or `pr-pending` with the alignment PR to land by true merge (Merge floor). An enqueued auto-merge is not evidence of the method; before reporting, read the enqueued method back — `gh pr view <n> --json autoMergeRequest --jq .autoMergeRequest.mergeMethod` — and prove it is `MERGE`. An enqueued `SQUASH` is a stop under the Merge floor, not something to wait out.
 - `versionFold`, `rcRetirement`, `checkout` — `returned`, or the named reason you are still on `main`.
 - A `private` npm surface (`surfaces.json`): the doctor's `npm-token-rejected` finding comes first. A 401 from `npm whoami` through the `_org` `npm/NPM_TOKEN` vault hop means the token is rejected, and every authenticated `npm view` then 404s exactly like an absent package — rotate the token; only after a login is a restricted 404 "unverifiable from here", never "not published" (`publish-private-package`). On a repo whose workflows publish through Trusted Publishing and name no registry token, that row is `info`, not a warning: no lane consumes the org token, so it constrains your manual read only.
 
@@ -82,8 +82,8 @@ Title first, verdict first. Name the resolved tag (never a placeholder like `vX.
 
 ## Retro
 
-Before the final report, answer one question honestly: did this skill's own instructions misfire this run — ambiguous wording, a misleading message, or an environment failure it should have warned about? Process only, never the user's code or task. If yes, file one lesson and move on; a clean run is silent (hard cap: one per run). It lands on the Hub board, deduplicated, and is fixed only through a reviewed PR — never edit the skill live. The retro is advisory: if the call fails, note it and continue. The amendment itself stays reference-free: the skill-drift gate rejects issue references in any section outside Merge floor, so carry the evidence in words or point at the guide entry — never inline reference markers.
+Before the final report, answer one question honestly: did this skill's own instructions misfire this run — ambiguous wording, a misleading message, or an environment failure it should have warned about? Process only, never the user's code or task. If yes, file one lesson and move on; a clean run is silent (hard cap: one per run). It lands on the owning board, deduplicated, and is fixed only through a reviewed PR — never edit the skill live. The retro is advisory: if the call fails, note it and continue. In-session, call the `jerv_learning_note` tool with origin retro and let it queue the lesson; the command below is the machine fallback. The amendment itself stays reference-free: the skill-drift gate rejects issue references in any section outside Merge floor, so carry the evidence in words or point at the guide entry — never inline reference markers.
 
 ```bash
-mmi-cli learning skill-lesson --skill release --title "<what misfired>" --body "<what; evidence; proposed amendment>"
+jervcode learn --origin retro --surface skills --title "release: <what misfired>" --body "<what; evidence; proposed amendment>"
 ```

package/skills/secrets/SKILL.md

@@ -163,6 +163,7 @@ Before your final report, answer one question honestly: did **this skill's own i
 this run — ambiguous wording, a misleading message, or an environment failure it should have warned
 about? (Process only — never the user's code or task; e.g. a canonical-name or tier mix-up, or a step
 that risked echoing a value.) If yes, file **one** lesson and move on; a clean run is silent (hard cap:
-one per run). It lands on the Hub board (deduped) and is fixed only via a reviewed PR — never edit the
-skill live; the retro is advisory, so if the call fails, note it and continue:
-`mmi-cli learning skill-lesson --skill secrets --title "<what misfired>" --body "<what; evidence; proposed amendment>"`
+one per run). It lands on the owning board (deduped) and is fixed only via a reviewed PR — never edit the
+skill live; the retro is advisory, so if the call fails, note it and continue. In-session, call the
+`jerv_learning_note` tool with origin retro; the machine fallback is:
+`jervcode learn --origin retro --surface skills --title "secrets: <what misfired>" --body "<what; evidence; proposed amendment>"`

package/skills/stage/SKILL.md

@@ -173,6 +173,7 @@ Before your final report, answer one question honestly: did **this skill's own i
 this run — ambiguous wording, a misleading message, or an environment failure it should have warned
 about? (Process only — never the user's code or task; e.g. a teardown that left a port bound, or a
 Playwright output path aimed at the repo root.) If yes, file **one** lesson and move on; a clean run is
-silent (hard cap: one per run). It lands on the Hub board (deduped) and is fixed only via a reviewed PR —
-never edit the skill live; the retro is advisory, so if the call fails, note it and continue:
-`mmi-cli learning skill-lesson --skill stage --title "<what misfired>" --body "<what; evidence; proposed amendment>"`
+silent (hard cap: one per run). It lands on the owning board (deduped) and is fixed only via a reviewed PR —
+never edit the skill live; the retro is advisory, so if the call fails, note it and continue. In-session, call the
+`jerv_learning_note` tool with origin retro; the machine fallback is:
+`jervcode learn --origin retro --surface skills --title "stage: <what misfired>" --body "<what; evidence; proposed amendment>"`