@mutmutco/codex-plugin 4.3.12 → 4.3.13
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.
package/package.json
CHANGED
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
|
|
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,6 +50,7 @@ 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
55
|
- `devRollForward` / `rcAlignment` — `pushed`, or `pr-pending` with the alignment PR to land by true merge (Merge floor).
|
|
55
56
|
- `versionFold`, `rcRetirement`, `checkout` — `returned`, or the named reason you are still on `main`.
|
|
@@ -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>"
|