@mutmutco/codex-plugin 4.3.43 → 4.3.45

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "mmi",
-  "version": "4.3.43",
+  "version": "4.3.45",
   "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.43",
+  "version": "4.3.45",
   "description": "MMI workflow skills and org gates delivery.",
   "author": {
     "name": "MMI Future",

package/skills/board/SKILL.md

@@ -151,6 +151,5 @@ run — ambiguous wording, a misleading message, or an environment failure it sh
 out to conflict, or a board read that misreported what was claimable.) If yes, file **one** lesson and
 move on; a clean run is 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 "board: <what misfired>" --body "<what; evidence; proposed amendment>"`
+note it and continue. File through MMI:
+`mmi-cli learning skill-lesson --skill board --title "<what misfired>" --body "<what; evidence; proposed amendment>"`

package/skills/bootstrap/SKILL.md

@@ -544,6 +544,5 @@ this run — ambiguous wording, a misleading message, or an environment failure
 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 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>"`
+edit the skill live; the retro is advisory, so if the call fails, note it and continue. File through MMI:
+`mmi-cli learning skill-lesson --skill bootstrap --title "<what misfired>" --body "<what; evidence; proposed amendment>"`

package/skills/bootstrap/seeds/README.template.md

@@ -18,7 +18,7 @@ access runbook → [repo-access](https://github.com/mutmutco/MMI-Hub/blob/develo
 
 Read this section at the start of agent work in this repo.
 
-- **Structure search:** JervCode indexes locally (Jerv-JervCode#2506). Verify results against cited source before acting.
+- **Structure search:** Use available code search tools. Verify results against cited source before acting.
 - **Durable WHY:** `docs/decisions/` — one file per decision, prose only for what was chosen and
   rejected; never a description of current state. Do not maintain living current-state under `docs/`.
 - **Current state:** code + live CLI (`mmi-cli oracle org project get`, `board`, `status`,

package/skills/epic/SKILL.md

@@ -124,6 +124,5 @@ this run — ambiguous wording, a misleading message, or an environment failure
 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 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>"`
+edit the skill live; the retro is advisory, so if the call fails, note it and continue. File through MMI:
+`mmi-cli learning skill-lesson --skill epic --title "<what misfired>" --body "<what; evidence; proposed amendment>"`

package/skills/hotfix/SKILL.md

@@ -94,8 +94,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 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.
+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. File through MMI with the command below. 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
-jervcode learn --origin retro --surface skills --title "hotfix: <what misfired>" --body "<what; evidence; proposed amendment>"
+mmi-cli learning skill-lesson --skill hotfix --title "<what misfired>" --body "<what; evidence; proposed amendment>"
 ```

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

@@ -12,6 +12,8 @@ The two tiers describe authority and blast radius, not separate storage products
 Read `mmi-cli oracle org access role <owner/repo> --json` and
 `mmi-cli oracle org access capabilities` for your actual authority.
 Installing MMI does not confer that authority. The server checks the caller and target scope.
+An empty result describes only your visible MMI scope. Check your MMI access and catalog;
+it does not require installing or querying a personal vault product.
 
 The registry catalog declares secret names before values are set. A shared, stageless value is
 the canonical default; a declared stage override wins for that stage. Avoid accidental duplicate

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

@@ -5,6 +5,11 @@ Reading or discussing the board is read-only until the developer authorizes work
 Claim approved work with `mmi-cli oracle board claim <issue>`, then prepare an isolated task
 workspace through the host. Preserve other developers' work.
 
+MMI workflows require no personal Jerv installation. Use Git or your chosen host for worktree
+creation; MMI performs its own guarded cleanup. Report a skill misfire with
+`mmi-cli learning skill-lesson --skill <name> --title <summary> --body-file <path>`.
+Feedback belongs on the MMI Hub board and never requires another developer's personal tooling.
+
 Read the issue, implementation, callers, and repository policy before editing.
 Run `mmi-cli tests policy --base <comparison-base>` to determine required checks against your target
 branch (normally origin/development for train repositories). The repository's policy decides, not
@@ -34,8 +39,10 @@ Read the selected release skill before operating the train. Let it choose versio
 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.
 A release announces itself in Slack: the Hub to the org alerts channel, a product to its own
-project channel when the project vault declares `SLACK_RELEASE_CHANNEL`; never post release notes
-by hand.
+project channel when the project's registry META sets `releaseChannel`; never post release notes
+by hand. The Hub always needs a curated `--announce-summary-file`, and so does any product whose
+META sets `releaseChannel` — 3–6 plain lines in the project's `releaseLanguage` (default `en`),
+written for that project's audience, never the raw PR titles.
 
 For local or private live testing, read [stage](../../stage/SKILL.md).
 For a new product repository, use [bootstrap](../../bootstrap/SKILL.md).

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 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.
+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. File through MMI with the command below. 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
-jervcode learn --origin retro --surface skills --title "rcand: <what misfired>" --body "<what; evidence; proposed amendment>"
+mmi-cli learning skill-lesson --skill rcand --title "<what misfired>" --body "<what; evidence; proposed amendment>"
 ```

package/skills/release/SKILL.md

@@ -33,7 +33,7 @@ Read `ready`, then `findings[]`: each carries `code`, `severity` (`blocker` · `
 
 Run from the primary checkout on the lane's start branch (`rc`; `development` for direct-track and `--dev`). Export the bump intent once from the bare argument — `MMI_BUMP_INTENT=minor|major|patch`, unset → `patch`; `MMI_RELEASE_VERSION=X.Y.Z` only for an exact target the tag math cannot derive.
 
-MMI-Hub only: write a fresh 3–6 line neutral summary to `f=$(mktemp tmp/release-summary.XXXXXX)` — sourced from Hub PR titles only (`origin/main..origin/development`), rewritten in Hub-subsystem terms, never a product or brand name. Hub scope is only `mutmutco/MMI-Hub`: never a product's board, `ds-propagate.yml`, or a product's deploy state. A product repo may pass `--announce-summary-file` too (optional): its notes post to the project's own release channel from the declared `SLACK_RELEASE_CHANNEL` vault key, in that product's own names — with no key declared the announcement is `skipped` and nothing else changes.
+Two cases need a summary file. (1) **MMI-Hub** — always: write a fresh 3–6 line neutral summary to `f=$(mktemp tmp/release-summary.XXXXXX)` — sourced from Hub PR titles only (`origin/main..origin/development`), rewritten in Hub-subsystem terms, never a product or brand name. Hub scope is only `mutmutco/MMI-Hub`: never a product's board, `ds-propagate.yml`, or a product's deploy state. (2) **Any product repo whose META carries `releaseChannel`** (`mmi-cli oracle org project get {owner}/{repo} --json`) — required too: read `releaseLanguage` (default `en`) and write 3–6 lines IN THAT LANGUAGE, in plain words for the project's audience: what changed and why it matters to a user; no commit prefixes, no issue or PR numbers, no file names, no product-internal jargon. The train refuses `--apply` without the file, and raw release notes are never posted to a project channel. A repo with no `releaseChannel` announces nothing and needs no file.
 
 ```bash
 r=$(mktemp tmp/release-receipt.XXXXXX)
@@ -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 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.
+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. File through MMI with the command below. 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
-jervcode learn --origin retro --surface skills --title "release: <what misfired>" --body "<what; evidence; proposed amendment>"
+mmi-cli learning skill-lesson --skill release --title "<what misfired>" --body "<what; evidence; proposed amendment>"
 ```

package/skills/secrets/SKILL.md

@@ -164,6 +164,5 @@ this run — ambiguous wording, a misleading message, or an environment failure
 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 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>"`
+skill live; the retro is advisory, so if the call fails, note it and continue. File through MMI:
+`mmi-cli learning skill-lesson --skill secrets --title "<what misfired>" --body "<what; evidence; proposed amendment>"`

package/skills/stage/SKILL.md

@@ -190,6 +190,5 @@ this run — ambiguous wording, a misleading message, or an environment failure
 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 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>"`
+never edit the skill live; the retro is advisory, so if the call fails, note it and continue. File through MMI:
+`mmi-cli learning skill-lesson --skill stage --title "<what misfired>" --body "<what; evidence; proposed amendment>"`