@mutmutco/codex-plugin 4.3.20 → 4.3.21

package/.codex-plugin/plugin.json

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

package/skills/bootstrap/SKILL.md

@@ -366,13 +366,9 @@ collaborator list + the per-branch allowlist are the record — no separate rost
   `pytest` / `pip install -e ".[dev]"` with `--var GATE_PY_VERSION=` (3.11 default). The runtime selects
   which setup step (`setup-node` vs `setup-python`) the rendered `if:` fires. The check command runs
   under the org **wall-clock budget** (#3178): the render pins `run-with-budget` to the CLI's blessed SHA
-  (since #6256 that one pin also covers the `zeroci-verify` step — both actions ship from the same Hub commit)
   with `--var GATE_MAX_SECONDS=` (300s onboarding default — tighten once the gate is measured, via
   `--var` or `org project set <repo> --var gate={"maxSeconds":N}`); `ci audit` and the release train
-  both enforce the step, so do not remove it. ZeroCI C3 (#6254): `--var GATE_AFFECTED_CMD=...` (or
-  `gate={"affectedCmd":"..."}`) runs an affected-only selection on pull_request instead of `GATE_CMD`;
-  empty (default) keeps the full suite on PRs. Pushes, tags and the rendered nightly `schedule`
-  (`17 3 * * *` on the default branch) always run the full `GATE_CMD` — that nightly is the drift catcher. `bootstrap apply --execute` installs that JSON as the
+  both enforce the step, so do not remove it. Every trigger runs the full `GATE_CMD`. `bootstrap apply --execute` installs that JSON as the
   repository ruleset itself (#6070) and reports one `product-ruleset` row: `PARK` (the gate file is not on
   the base branch yet — installed disabled), `WAIT` (the gate exists but has not emitted a proven-green
   `gate` context — kept disabled; re-run apply after the gate passes), `ACTIVATE` (gate green — enforcement
@@ -381,13 +377,11 @@ collaborator list + the per-branch allowlist are the record — no separate rost
   $OWNER/$REPO` remains the supported fallback; confirm `product required-check ruleset enforcement active`
   with `bootstrap verify` before reporting bootstrap complete. MMI-Hub keeps its own three-job gate
   (`cli`/`infra`/`docs`) — never apply the product ruleset there.
-- **The ruleset requires an up-to-date head (#6263)** — the seeded reference sets
-  `strict_required_status_checks_policy: true` ("require branches to be up to date before merging"), so the
-  last of several parallel landings re-tests on the real combination instead of a base that lacked the
-  others (Jerv-JervCode#4289). `bootstrap apply --execute` and `ci reconcile --apply` re-PUT an existing
-  non-strict ruleset; `bootstrap verify` reports it as `product required-check ruleset requires an up-to-date
-  branch`. `pr merge` / `pr land` update a BEHIND head from the base with a merge commit and re-wait once —
-  see `docs/Guides/train-troubleshooting.md#head-behind-base`.
+- **The committed ruleset owns its up-to-date policy.** New repositories default to
+  `strict_required_status_checks_policy: false`. Bootstrap and CI reconciliation preserve that policy
+  when updating contexts, and converge the live ruleset to the committed setting. Repositories may
+  explicitly require an up-to-date head. `pr merge` / `pr land` still update a BEHIND head from the base
+  with a merge commit and re-wait once — see `docs/Guides/train-troubleshooting.md#head-behind-base`.
 - **A brand-new repo cannot pass the gate you just installed — its first commit must carry a real project
   (#2928).** The seeded `gate.yml` runs `GATE_INSTALL_CMD` + `GATE_CMD` (`npm ci` + `npm run check` by
   default) **unconditionally**. An empty repo has no `package.json`, so the gate **fails on the seed PR

package/skills/bootstrap/seeds/gate.template.yml

@@ -1,9 +1,6 @@
 name: gate
 # Org-standard green-before-merge gate for product repos (#1333). Runs on PRs, train-branch pushes,
 # and v* tags so /release and /hotfix can discover required contexts on the tagged SHA.
-# ZeroCI C3 (#6254): a nightly `schedule` run on the default branch executes the FULL GATE_CMD even when
-# a signed receipt already proves the tree — the drift catcher for affected-only PR selection
-# (GATE_AFFECTED_CMD) and for stale receipts. The job `if:` below admits `schedule` (it is not a push).
 #
 # Runner: self-hosted mmi-runner (mmi-live) — see docs/Guides/gh-runner-runbook.md in MMI-Hub.
 # #4118: if GATE_CMD runs tsgo or other memory-heavy typecheck / browser work, pin this job to
@@ -14,9 +11,6 @@ name: gate
 # bootstrap with --var):
 #   GATE_RUNTIME       — node | python (selects which setup step fires)
 #   GATE_CMD           — the check command ({{GATE_CMD}})
-#   GATE_AFFECTED_CMD  — affected-only check command run on pull_request instead of GATE_CMD (#6254);
-#                        empty (default) renders GATE_CMD here too, so the PR gate stays the full suite.
-#                        Pushes, tags and the nightly schedule always run GATE_CMD. ({{GATE_AFFECTED_CMD}})
 #   GATE_INSTALL_CMD   — the dependency-install command ({{GATE_INSTALL_CMD}})
 #   GATE_WORKDIR       — app working directory when not the repo root ({{GATE_WORKDIR}})
 #   GATE_CACHE_DEP_PATH— npm lockfile path for runner-checkout heal ({{GATE_CACHE_DEP_PATH}})
@@ -28,27 +22,18 @@ name: gate
 #   GATE_FULL_RUN_BRANCH — train branch whose PUSHES run the full gate job (development on full/direct;
 #                        main on trunk). `main` is ALWAYS included in the job `if:` below so a required-
 #                        checks ruleset on main cannot be silently skipped by a future bootstrap (#4113).
-# GATE_BUDGET_SHA is rendered by the CLI from its blessed run-with-budget pin — not an operator knob. It
-# also pins zeroci-verify (MMI-Hub#6253): both actions ship from the same Hub commit.
+# GATE_BUDGET_SHA is rendered by the CLI from its blessed run-with-budget pin — not an operator knob.
 # GATE_RUNNER_SHA pins the org runner-checkout / runner-node-toolchain actions (#5610).
 # Estate policy 2026-08-23: GitHub-hosted Windows (`windows-latest` / windows-*) is forbidden org-wide.
 # Do not add a windows-compat (or any other) job that runs-on GH-hosted Windows. Linux self-hosted
 # (mmi-live / mmi-heavy) is the only CI merge gate. Rare Windows proof stays on the owner's machine or
 # a future self-hosted Windows runner — never windows-latest.
 # (seed touch: keep BOM digests in lockstep after classifier land.)
-# harbour: unmanaged
-# The nightly `schedule` cron below is GitHub's own clock by design (docs/schedules.md rule 5, #6270): it is
-# the drift catcher for the PR gate (#6254), a required-check workflow that must not become a SCHEDULE# row
-# armed and dispatched by the plane it otherwise never touches — the merge gate stays decoupled from the
-# schedule plane, exactly as the deadman is.
 on:
   pull_request:
   push:
     branches: {{GATE_PUSH_BRANCHES_YAML}}
     tags: ['v*']
-  # #6254: nightly full run on the default branch — catches affected-only drift and stale receipts.
-  schedule:
-    - cron: '17 3 * * *'
 
 env:
   FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true
@@ -63,8 +48,6 @@ concurrency:
 
 permissions:
   contents: read
-  # MMI-Hub#6253: ZeroCI receipts are commit statuses on the PR head; the gate reads them, never writes them.
-  statuses: read
 
 jobs:
   gate:
@@ -132,31 +115,10 @@ jobs:
         if: ${{ '{{GATE_RUNTIME}}' == 'python' }}
         run: |
           python3 --version || { echo "::error title=CI runner toolchain::RUNNER NOT PROVISIONED — python3 not on PATH after setup-python. This is the runner, not your diff; no install or test ran. Re-run the job; if it persists the mmi-runner python toolchain needs attention (docs/Guides/gh-runner-runbook.md in MMI-Hub)."; exit 1; }
-      # MMI-Hub#6253 ZeroCI: skip the install and the budgeted run when a trusted seat already ran this
-      # exact command on this exact tree (receipt = commit status zeroci/<command> on the PR head). It
-      # needs only git and gh, so it sits before the install. Only `verified=true` skips;
-      # absent/stale/unreadable fall through to the install and the budgeted run below.
-      - id: zeroci
-        uses: mutmutco/MMI-Hub/.github/actions/zeroci-verify@{{GATE_BUDGET_SHA}}
-        with:
-          command: {{GATE_CMD}}
-          working-directory: {{GATE_WORKDIR}}
-          head-sha: ${{ github.event.pull_request.head.sha || github.sha }}
       - run: {{GATE_INSTALL_CMD}}
-        if: ${{ steps.zeroci.outputs.verified != 'true' || github.event_name == 'schedule' }}
       # #3178: the check runs under the org wall-clock budget — a hung suite dies at the ceiling instead
       # of squatting a runner lane for GitHub's 6h default. ci-audit + the release train enforce this step.
-      # #6254 (ZeroCI C3): two complementary budget steps. pull_request runs GATE_AFFECTED_CMD (rendered
-      # equal to GATE_CMD until the knob is set); every other trigger runs the full GATE_CMD. The nightly
-      # schedule runs even when the zeroci receipt already proves the tree — that is its whole point.
-      - if: ${{ steps.zeroci.outputs.verified != 'true' && github.event_name == 'pull_request' }}
-        uses: mutmutco/MMI-Hub/.github/actions/run-with-budget@{{GATE_BUDGET_SHA}}
-        with:
-          command: {{GATE_AFFECTED_CMD}}
-          max-seconds: {{GATE_MAX_SECONDS}}
-          working-directory: {{GATE_WORKDIR}}
-      - if: ${{ github.event_name != 'pull_request' && (steps.zeroci.outputs.verified != 'true' || github.event_name == 'schedule') }}
-        uses: mutmutco/MMI-Hub/.github/actions/run-with-budget@{{GATE_BUDGET_SHA}}
+      - uses: mutmutco/MMI-Hub/.github/actions/run-with-budget@{{GATE_BUDGET_SHA}}
         with:
           command: {{GATE_CMD}}
           max-seconds: {{GATE_MAX_SECONDS}}

package/skills/bootstrap/seeds/mmi-product-required-checks.template.json

@@ -1,5 +1,5 @@
 {
-  "_comment": "Repository-level ruleset requiring the product gate job (#1333). Apply via GitHub repo rulesets (master-admin) after bootstrap seeds gate.yml — the job name gate must match this context. strict_required_status_checks_policy=true (#6263): the head must be up to date with the base before merging, so the last of several parallel landings re-tests on the real combination.",
+  "_comment": "Repository-level ruleset requiring the product gate job (#1333). Apply via GitHub repo rulesets (master-admin) after bootstrap seeds gate.yml — the job name gate must match this context.",
   "name": "mmi-product-required-checks",
   "target": "branch",
   "enforcement": "active",
@@ -13,7 +13,7 @@
     {
       "type": "required_status_checks",
       "parameters": {
-        "strict_required_status_checks_policy": true,
+        "strict_required_status_checks_policy": false,
         "required_status_checks": [
           { "context": "gate" }
         ]