@mutmutco/codex-plugin 4.3.12 → 4.3.14

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (6) hide show
  1. package/.codex-plugin/plugin.json +1 -1
  2. package/package.json +1 -1
  3. package/skills/epic/SKILL.md +4 -2
  4. package/skills/hotfix/SKILL.md +1 -1
  5. package/skills/rcand/SKILL.md +1 -1
  6. package/skills/release/SKILL.md +3 -2
package/.codex-plugin/plugin.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "mmi",
3
- "version": "4.3.12",
3
+ "version": "4.3.14",
4
4
  "mmiCompat": "4.x",
5
5
  "description": "MMI workflow skills and org gates delivery.",
6
6
  "author": {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mutmutco/codex-plugin",
3
- "version": "4.3.12",
3
+ "version": "4.3.14",
4
4
  "description": "MMI workflow skills and org gates delivery.",
5
5
  "author": {
6
6
  "name": "MMI Future",
package/skills/epic/SKILL.md CHANGED
@@ -37,7 +37,9 @@ Before drafting, inspect the umbrella's existing children:
37
37
  mmi-cli oracle issue children <owner/repo#N> # each child: number/title/state/repo/boardStatus/linkedPrs
38
38
  ```
39
39
 
40
- Write a JSON array (one object per child) to a scratch path under `.jerv/tmp/`. Each row:
40
+ Write a JSON array (one object per child) to a scratch path under `.jerv/tmp/`, named uniquely for this
41
+ epic — `.jerv/tmp/epic-<parentNumber>-children.json` (never reuse the file between epics: a previous
42
+ epic's leftover batch collides with the new rows, silently on an unguarded host). Each row:
41
43
 
42
44
  ```json
43
45
  [
@@ -67,7 +69,7 @@ set before writing.
67
69
  ## Step 2 — create the children
68
70
 
69
71
  ```bash
70
- mmi-cli oracle issue create --type task --batch .jerv/tmp/epic-children.json --surface cli
72
+ mmi-cli oracle issue create --type task --batch .jerv/tmp/epic-42-children.json --surface cli
71
73
  ```
72
74
 
73
75
  `--type` is required by the create command but each row's own `type` governs; pass any valid type as the
package/skills/hotfix/SKILL.md CHANGED
@@ -95,7 +95,7 @@ Title first, verdict first. Name the resolved tag (never a placeholder like `vX.
95
95
 
96
96
  ## Retro
97
97
 
98
- 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.
98
+ 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.
99
99
 
100
100
  ```bash
101
101
  mmi-cli learning skill-lesson --skill hotfix --title "<what misfired>" --body "<what; evidence; proposed amendment>"
package/skills/rcand/SKILL.md CHANGED
@@ -73,7 +73,7 @@ Title first, verdict first. Name the resolved tag (never a placeholder like `vX.
73
73
 
74
74
  ## Retro
75
75
 
76
- 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.
76
+ 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.
77
77
 
78
78
  ```bash
79
79
  mmi-cli learning skill-lesson --skill rcand --title "<what misfired>" --body "<what; evidence; proposed amendment>"
package/skills/release/SKILL.md CHANGED
@@ -50,8 +50,9 @@ Read the receipt at `$r`, never the exit code (exit `2` = shipped with a follow-
50
50
  - `releaseVerdict.releaseStatus` + `followUpStatus` — `succeeded` + `pending` is shipped with the follow-up unresolved: neither failed nor done.
51
51
  - `deployStatus` — `pending` is never terminal; `promoted: true` holds even when a deploy failed.
52
52
  - `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.
53
+ - 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>`.
53
54
  - `announceNote` (Hub) — `announced`, `skipped`, or the failure note.
54
- - `devRollForward` / `rcAlignment` — `pushed`, or `pr-pending` with the alignment PR to land by true merge (Merge floor).
55
+ - `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.
55
56
  - `versionFold`, `rcRetirement`, `checkout` — `returned`, or the named reason you are still on `main`.
56
57
  - 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.
57
58
 
@@ -81,7 +82,7 @@ Title first, verdict first. Name the resolved tag (never a placeholder like `vX.
81
82
 
82
83
  ## Retro
83
84
 
84
- 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.
85
+ 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.
85
86
 
86
87
  ```bash
87
88
  mmi-cli learning skill-lesson --skill release --title "<what misfired>" --body "<what; evidence; proposed amendment>"