@mutmutco/codex-plugin 4.3.44 → 4.3.46

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "mmi",
-  "version": "4.3.44",
+  "version": "4.3.46",
   "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.44",
+  "version": "4.3.46",
   "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

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

@@ -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

@@ -128,12 +128,12 @@ file (#6351). A vault-native repo with no `.env` gets `PORT` defaulted to the bo
 
 ## /stage --live — personal cloud dev stage
 
-dev.x stages are **not standing environments**: without `--live` the dev stage is dark. `--live`
-deploys the **current branch** to the project's dev runtime and serves it **only to your public IP** —
-gated at the **Cloudflare edge** (#1761). The CLI detects your IP, dispatches the central
-`tenant-deploy.yml` (stage=dev), then `tenant-control.yml` `cf-gate-allow` (an ephemeral Cloudflare WAF
-rule scoped to your dev host + IP). The box no longer IP-gates dev. No SSH from your machine; everything
-moves through the central workflows.
+Project admins can deploy the **current branch** to their project's dev runtime without an IP
+restriction. The CLI dispatches legacy gate cleanup, then the dev deploy through the Hub backend.
+Cleanup removes only that project's old stage rules and creates no Cloudflare rules, so rule-slot
+quotas do not block staging. It still reads Cloudflare to detect old gates; cleanup failures stay visible.
+The stage is accessible from any IP after both workflows succeed. The app's own sign-in still applies.
+No SSH from your machine; project authorization remains enforced by the Hub.
 
 **Deploy-model preflight (#5466 / #5467).** `/stage --live` is **not** generally available. Read
 `deployModel` first (`mmi-cli oracle org project get {owner}/{repo}` → `deployModel`, or the dry
@@ -141,15 +141,15 @@ moves through the central workflows.
 model the Hub tenant-deploy + tenant-control gates require). **`registry-publish` is not applicable**
 for live stages — nor are hub-serverless, solo-container, static-cdn, content, or none. For an
 unsupported model the dry plan refuses **before** offering `--apply` / `--down`; do not invent a
-tenant deploy or gate.
+tenant deploy.
 
 ```bash
 mmi-cli stage --live           # dry-run plan (refuses when deployModel is not tenant-container)
-mmi-cli stage --live --apply   # deploy + gate your IP at the Cloudflare edge
+mmi-cli stage --live --apply   # clear legacy gates + deploy without an IP restriction
 ```
 
-Tear it down when done — **only when `--apply` actually created a runtime or gate**. The runtime stops
-and the Cloudflare edge gate is removed:
+Tear it down when done — **only when `--apply` actually created a runtime**. This stops the runtime
+without Cloudflare work:
 
 ```bash
 mmi-cli stage --live --down --apply
@@ -166,8 +166,8 @@ The stage URL, what's running (server + tools), the workspace path (`tmp/stage/`
 ## Notes
 
 - `/stage` is local — no AWS, no deploy, no board or version effect. The one cloud exception is
-  `--live`: an on-demand **dev** stage of your branch for **`tenant-container`** repos only, gated to
-  your IP at the Cloudflare edge (above). Preflight `deployModel` before offering it; `registry-publish`
+  `--live`: an on-demand **dev** stage of your branch for **`tenant-container`** repos only, without
+  a stage IP restriction (above). Preflight `deployModel` before offering it; `registry-publish`
   and other models have no live stage.
 - Remote rc/live environments move only through `/rcand`, `/release`, and `/hotfix`.
 - Everything is gitignored; `/stage` never produces a tracked change.
@@ -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>"`