Codexless Release Supervisor

Codexless Release Supervisor

Run Codexless releases as a fail-closed state machine. The canonical Codexless source repository is the only editable implementation truth. Public candidate/official repositories are downstream release sinks and must not independently evolve release policy or implementation.

Prefer maintained scripts and observable receipts over memory or hand-written test lists. Keep the current release scope fixed; log non-blocking follow-ups instead of expanding the release.

Start

1. Resolve the canonical repository and read its Git state, target version, and current acceptance suite version.
2. Read references/release-gates.md before final release/hotfix gating.
3. Freeze the canonical commit before deterministic public projection or candidate provenance is claimed.
4. Materialize the public projection through the canonical R1 exporter before candidate work. config/public-export-policy.json is the fail-closed file authority; release/public-overlay/ is the only canonical public-only overlay source. The exporter reads canonical bytes from the exact Git source commit and reads the immutable public migration seed only from its pinned Git commit, never from a dirty public working tree.
5. Treat the R1 projection receipt and the older R0 candidate receipt as different evidence. R1 may truthfully report fullDeterministicExporter=true; the R0 candidate gate remains historical candidate-provenance evidence with fullDeterministicExporter=false and must not be rewritten or back-claimed.
6. Build or materialize a release candidate only after the R1 projection is reviewed. Candidate/native-install/publication work is a later gate and is not proven by the exporter.
7. If the user asked only for preparation, stop before git push, tag creation, or GitHub Release publication.

Canonical machine gates

Use the canonical repository's maintained entries:

npm run test:all
npm run test:acceptance:auto
npm run test:public-export
npm run release:public-export -- --base-repo <repo-containing-pinned-public-base> --dry-run
npm run release:candidate-gate -- --candidate <public-candidate-root>

• test:all recursively auto-discovers .mjs regression files and takes manual/helper exclusions from the same Acceptance registry rather than a second list. A discovered required test that reports Node Test SKIP is fail-closed, not PASS. It is a separate release-wide source gate and must run through the maintained prepared harness/environment for tests that require Codex/MCP fixtures. If that harness is unavailable or a required release-wide test cannot run, the release is BLOCKED; test:acceptance:auto does not substitute for it.
• test:acceptance:auto validates the current Acceptance ID registry and runs each registered deterministic AUTO/INTEGRATION/governance evidence file independently with a bounded per-file timeout. AUTOMATED_GREEN is not full release GREEN because required Host/live evidence is intentionally still outstanding.
• test:public-export is the R1 governance regression for deterministic allowlisting, immutable-base reads, exact overlay patches, generated public package rules, provenance semantics, read-only comparison, and _work/-only materialization.
• release:public-export requires a clean canonical source commit; reads all canonical/direct/overlay inputs from that exact Git commit; reads the pinned public migration seed by commit blob rather than public working-tree bytes; rejects undeclared/duplicate/unsafe targets; excludes candidate-generated config/release-manifest.json; and records the exact file list, per-file SHA-256, content tree SHA-256, exporter/policy hashes, source commit, and base commit. Its R1 receipt may report fullDeterministicExporter=true, but explicitly does not prove candidate/native-install/publication acceptance.
• release:candidate-gate remains the R0 downstream candidate gate: it requires a clean canonical HEAD, exact candidate manifest sourceRevision == canonical HEAD, exact Release Supervisor parity, Browser public-export parity, and records a deterministic candidate-content snapshot with explicit local-noise exclusions. Its R0 receipt still says fullDeterministicExporter=false; do not reinterpret that older receipt as R1 or use R1 to claim candidate acceptance.
• Windows and Apple Silicon macOS release installation acceptance is source-based. On each native host, start from a clean checkout/export of the exact frozen public candidate/tag with no pre-existing node_modules, run the documented platform installer (bin\\codexless-install.cmd or bin/codexless-install.sh) in an isolated fresh user/state/install root, then validate installed doctor, exact public stdio tool surface, and Browser status/open/read/close/no-residual. Household/Main Road evidence never substitutes for this native public front-door acceptance.
• Full npm run test:acceptance -- --subject-version <version> --subject-build-id <buildId> --evidence <host-evidence.json> is fail-closed: evidence must match the exact release subject, every PASS must name structured host/platform/front-door + observation time + receipt, and any failed or missing required Host/live item blocks GREEN.