fix: reject malformed generated roots

.woodpecker/ci.yml

@@ -68,25 +68,15 @@ steps:
       - bash packages/mosaic/framework/tools/quality/scripts/test-upgrade-durable-snapshot.sh
       - bash packages/mosaic/framework/tools/quality/scripts/test-install-migration.sh
 
-  # Anti-inert-gate registry. Deliberately unconditional: no path filter and no
-  # step-level `when`, because a gate can be disabled by changes outside its own path.
-  gate-verify:
-    image: *node_image
-    commands:
-      - *enable_pnpm
-      - pnpm gate:verify
-    depends_on:
-      - install
-      - sanitization
-      - upgrade-guard
-
   typecheck:
     image: *node_image
     commands:
       - *enable_pnpm
       - pnpm typecheck
     depends_on:
-      - gate-verify
+      - install
+      - sanitization
+      - upgrade-guard
 
   # lint, format, and test are independent — run in parallel after typecheck
   lint:

docs/ADMIN-GUIDE/README.md

@@ -1,3 +0,0 @@
-# Administrator Guide
-
-- [Gate registry operations](quality-gate-registry.md)

docs/ADMIN-GUIDE/quality-gate-registry.md

@@ -1,35 +0,0 @@
-# Gate Registry Operations
-
-## Routine verification
-
-Run `pnpm gate:verify` from a dependency-installed checkout. Exit zero means registry observations matched their declared `actual` values; it does **not** assert required-behavior conformance while deltas remain. Open `DEFECT` records are checked descriptions of current behavior with tracked owners, never successful gate outcomes.
-
-Investigate any of these immediately:
-
-- `GATE VERIFY FAILED` — registry structure, observed behavior, provenance, claim binding, source/deployment identity, or negative-control detection changed. The verifier aggregates independent phase failures, so repair the responsible stable-ID diagnostics as well as any accompanying stale-fixture error; do not treat the generic error as a substitute.
-- `unregistered gate` — an executable appeared under a declared gate root without a registry entry.
-- `no negative control` — a gate has no must-fail case.
-- `DEPLOYED IDENTITY UNAVAILABLE` — the runner cannot reach the installed enforcing copy. The pinned observation is checked, but live equality is not asserted.
-- `HISTORY_PROVENANCE_FORBIDDEN` — a history assertion path was reintroduced at the repository layer; remove it and keep RM-60 as the tracked external-boundary owner.
-
-## Updating a gate
-
-1. Add or change the criterion, its exact criterion-side `caseRefs`, and matching case-side `criterionIds`. Preserve recursive closed-schema validation for every nested object; new fields require explicit key and type handling.
-2. Observe the must-fail case fail for its own stated reason; moving the binding to any undeclared case must fail verification.
-3. Declare an exact inerting mutation and observe the verifier detect it.
-4. If required and actual behavior differ, add a tracked remediation owner and justification.
-5. If meaning changed, append provenance; never replace the original silently.
-6. For an installed counterpart, verify live byte identity and update the observed digest only from measured evidence.
-7. Run focused verifier tests, `pnpm gate:verify`, and the repository baseline gates.
-
-Do not add an ownerless exception or describe an open delta as pass/green/OK.
-
-## CI behavior
-
-Woodpecker runs `gate-verify` on every pull request and protected-main push without path filtering. This is deliberate: changes outside gate files can make a gate inert. The step needs no local history preparation because RM-02 asserts no history-provenance property.
-
-**DOES:** PR CI executes current-tree verification unprivileged and fail-closed. It compares the manifest and verifier inventory separately with `gates/required-gates.baseline.json`, and consumed case evidence carries a subject checked against its gate definition. **Detects accidental and incompetent inventory drift within a checkout; does NOT survive an adversary who rewrites baseline, manifest, and verifier consistently — that guarantee requires RM-60's external boundary.** The registered shrink-both, overclaim, and per-gate evidence-subject controls must remain red for their stated reasons.
-
-**DOES NOT:** No local git state in the PR checkout is trustworthy as a history anchor because PR-controlled lifecycle code executes before the gate. The verifier has no history-verification path, and its closed current-tree observation renderer has no history/ancestry/lineage success class. Do not add a local ref, config, remote URL, source constant, or author-positioned path as a replacement anchor.
-
-`scripts/gate-history-exclusion-control.mjs` enforces the output incapacity by testing alternate success wording and production renderer wiring; its registered fixture proves adding a prohibited success class goes red. RM-60 is the tracked owner of the provider-controlled/protected pre-execution boundary. If a bootstrap override is ever proposed before RM-60, it requires a separate explicit, loud, audited, retiring, negative-controlled design; RM-02 contains no override.

docs/DEVELOPER-GUIDE/README.md

@@ -1,3 +0,0 @@
-# Developer Guide
-
-- [Gate registry and negative controls](quality-gate-registry.md)

docs/DEVELOPER-GUIDE/quality-gate-registry.md

@@ -1,43 +0,0 @@
-# Gate Registry and Negative Controls
-
-`gates/gates.manifest.json` is the machine-readable registry for the initial RM-02 gate slice. Run:
-
-```bash
-pnpm gate:verify
-```
-
-## Registered slice
-
-The registry covers root typecheck, lint, and format checks; RM-01 checkout preflight; the Mosaic CI queue guard; and root Husky pre-commit/pre-push hooks. It does not imply repository-wide coverage. Framework scripts, package-local build/test scripts, templates, and deployment/release scripts remain assigned to RM-54.
-
-Every gate declares exact invocations, observed and required outcomes, criterion bindings, and a single exact inerting mutation. Every case result carries an evidence-side subject that is compared with the gate definition when the result is consumed; the population control mutates that evidence-side subject independently for every required gate. Every must-fail case requires a non-empty reason diagnostic. The verifier rejects a stale, ambiguous, crashing, or ineffective mutation. Fixture and mutation writes reject path traversal and final-component symlinks. Every nested manifest object used by outcomes, mutations, fixtures, deployments, defects, compatibility, provenance, coverage, and merge assertions has closed keys and strict field types; a misspelling cannot silently turn a required comparison into an absent optional field. Independent validation phases collect labeled failures instead of letting one thrown fixture, claim, discovery, deployment, mutation, or compatibility error mask already-known stable-ID diagnostics. This proves detection of the **declared** inerting mutation, not every possible semantic weakening.
-
-## Required versus actual
-
-A case may record different `required` and `actual` outcomes only with a tracked owner. The verifier checks current reality against `actual`, prints each difference as `DEFECT (owner: ...)`, and fails when behavior changes without a matching registry update. A defect is never described as passing, green, or OK.
-
-The queue guard currently has RM-03-owned deltas. In particular, its stdin/heredoc classifier does not consume piped status JSON, so terminal-success, no-status, and terminal-failure payloads become `unknown`; unknown and malformed states exit zero; push purpose defaults to `main`. RM-02 records these observations and does not edit the guard.
-
-## Criteria, prose, and compatibility
-
-Each criterion declares exact `caseRefs`; the verifier compares those semantic declarations bidirectionally with case-side `criterionIds` and requires at least one must-fail case. Moving a criterion ID to an unrelated case therefore fails as both a missing declared exercising case and an undeclared binding. Registered meta-negative controls misbind a criterion, remove meaning provenance, and misbind a prose claim, and each must make structure verification red for its stated reason.
-
-Designated governing prose uses `GATE-CLAIM:<id>` markers. Each claim also names the exact must-fail `caseRef` that exercises its criterion; unknown, positive-only, unrelated, unbound, or registered-but-missing claims fail. Orchestrator-owned claims from `TASKS.md` are bound through `docs/remediation/GATE-CLAIMS.md`, which records source headings and anchored text without changing task tracking. Marker completeness still requires RM-54 review because arbitrary English claims cannot be inferred safely.
-
-Compatibility checks detect direct contradictions in declared finite constructions. The verifier combines referenced case fixtures and environments in one isolated tree, rejects conflicting fixture/environment values, executes the construction's exact invocation, and checks its exact outcome. They do not prove semantic consistency of arbitrary natural language.
-
-Restatements preserve original text, current text, reason, finding/task, and date.
-
-## Source and deployed identity
-
-A gate with an external installed counterpart declares it explicitly. When the installed queue guard is reachable, its bytes must equal repository source and an internal drift control is observed red. In CI the operator-home installation may be outside the container; the verifier checks the pinned observed source digest, reports `DEPLOYED IDENTITY UNAVAILABLE (owner: RM-04)`, and does not infer live equality.
-
-## Current-tree and history-provenance boundary
-
-**DOES:** Every PR evaluates the current checkout's registered gates and declared inerting mutations directly, unprivileged and fail-closed. The seven-gate population, verifier inventory, and `gates/required-gates.baseline.json` are compared inside the checkout. Evidence-side subjects are consumed and compared with gate definitions for every gate. **Detects accidental and incompetent inventory drift within a checkout; does NOT survive an adversary who rewrites baseline, manifest, and verifier consistently — that guarantee requires RM-60's external boundary.**
-
-**DOES NOT:** This repository layer establishes history provenance at all. `pnpm install` executes PR-controlled lifecycle code before `gate:verify`, so no local ref, git config, remote URL, constant, or author-positioned path in the checkout can anchor a history claim. An observation saying “unverifiable” while returning zero would be a green wearing a disclaimer, so the claim and history verifier path are removed.
-
-The production output path uses a closed current-tree observation renderer; history, ancestry, and provider-lineage success are not representable observation classes. `scripts/gate-history-exclusion-control.mjs` exercises alternate success wording and production renderer wiring. Its registered must-fail case turns red if a prohibited success class is added or renderer consumption is bypassed. RM-60 owns the provider-controlled/protected pre-execution boundary needed before history provenance can be asserted. No bootstrap override exists in RM-02.
-
-Universal checks first prove populations non-empty. The production profile reads the same-checkout baseline before comparing the verifier inventory and manifest separately, while `gateRefs` on the D-38/D-40 criteria must exactly span every registered gate. Population controls mutate evidence-side subjects and type-strict comparison inputs one gate at a time and require rejection across the complete inventory. A registered prose-claim control fails when the same-checkout mechanism is described as an adversarial protection.

docs/PRD.md

@@ -14,63 +14,6 @@
 
 ---
 
-## RM-02 Gate Registry and Negative-Control Verifier (#1029)
-
-### Problem and objective
-
-Existing deterministic gates can return success without enforcing their stated property. RM-02 introduces a machine-readable registry and an unconditional CI verifier that distinguishes required behavior from observed behavior, proves every registered negative control can detect its own failure reason, and makes source/deployment drift visible.
-
-### Scope
-
-**In scope:** root typecheck, lint, and format gates; RM-01 checkout preflight; the Mosaic CI queue guard; root Husky pre-commit and pre-push hooks; criterion bindings; modeled compatibility; meaning-change provenance; security/integrity prose claim markers; source-versus-deployed identity; unprivileged current-tree PR verification; independent required-inventory comparison; evidence-side subject consumption; and enforced structural exclusion of history provenance until RM-60 provides protected external authority.
-
-**Out of scope:** fixing the queue guard (RM-03); exhaustive registration of every repository executable (RM-54); semantic proof that arbitrary English criteria are mutually satisfiable (RM-54/RM-55); history provenance before RM-60's provider-controlled/protected execution boundary; and a same-authority trust anchor for repository-authored evidence (RM-25/RM-59).
-
-### Normative requirements
-
-1. `RM02-REQ-01`: The JSON registry SHALL give every gate and criterion a stable ID and SHALL declare exact invocation, input classes, cases, exact observed and required exit codes, reason diagnostics, and criterion bindings.
-2. `RM02-REQ-02`: Every gate SHALL have at least one observed-red must-fail case. The verifier SHALL reject missing, stale, ambiguous, or ineffective declared inert mutations and SHALL name an externally inerted gate.
-3. `RM02-REQ-03`: Every acceptance criterion SHALL declare exact criterion-side `caseRefs` that match case-side `criterionIds` bidirectionally and include a case that can fail for that criterion's stated reason. Moving a binding to an unrelated case SHALL fail verification. Security/integrity prose claims in the designated governing documents SHALL carry bound `GATE-CLAIM:<id>` markers and declare the exact must-fail case exercising the claim criterion.
-4. `RM02-REQ-04`: Declared finite compatibility scenarios SHALL execute together and direct modeled contradictions SHALL fail. This does not claim semantic consistency of arbitrary English.
-5. `RM02-REQ-05`: Restated criteria SHALL retain original text, current text, reason, finding/task, and dated meaning-change history.
-6. `RM02-REQ-06`: An observed behavior differing from required behavior SHALL be reported as `DEFECT` with a tracked owner; an ownerless delta SHALL fail verification. Such a gate SHALL never be described as passing, green, or OK.
-7. `RM02-REQ-07`: Executables under declared gate roots SHALL fail with `unregistered gate` when absent from the registry. The initial coverage boundary SHALL explicitly list exclusions and bind the broader inventory to RM-54.
-8. `RM02-REQ-08`: Every gate with a deployed counterpart SHALL register source/deployed byte identity and a must-fail drift control. Gates without a deployed counterpart SHALL say so explicitly.
-9. `RM02-REQ-09`: CI SHALL run `pnpm gate:verify` on every pull request without path filtering and on protected-main pushes.
-10. `RM02-REQ-10` (restated): PR CI SHALL perform unprivileged, fail-closed current-tree verification only. The production observation renderer SHALL be a closed current-tree-only output type with no representable history-provenance success state. A registered must-fail control SHALL turn red if history/ancestry/lineage success is added to that renderer or if production output bypasses the renderer. RM-60 owns the provider-controlled/protected pre-execution boundary required to establish history provenance.
-11. `RM02-REQ-11` (`D-46`): The required seven-gate inventory SHALL be read from a same-checkout baseline and compared separately with both the verifier inventory and manifest. Shrinking the verifier inventory and manifest together while leaving the baseline intact SHALL fail for the removed gate. **Detects accidental and incompetent inventory drift within a checkout; does NOT survive an adversary who rewrites baseline, manifest, and verifier consistently — that guarantee requires RM-60's external boundary.**
-12. `RM02-REQ-12` (`D-38`): Every consumed case result SHALL carry an evidence-side subject independently declared from the gate definition. The verifier SHALL compare that evidence subject with the gate definition when consuming the result. A population control SHALL mutate the evidence-side subject independently for every required gate and observe rejection for every gate.
-13. `RM02-REQ-13` (`D-40`): For every gate listed in the required inventory baseline, each discriminator and comparison input SHALL have a recursively closed, type-strict schema. Unknown, misspelled, wrong-type, or present-but-empty nested assertion fields SHALL fail rather than disabling an assertion.
-14. `RM02-REQ-14` (`D-46`): No universally quantified registry check SHALL run until its population is proven non-empty and compared with the same-checkout baseline. The required seven-gate inventory, criteria, prose claims, and compatibility scenarios SHALL reject empty populations before reporting that all registered cases ran.
-
-#### RM02-REQ-10 meaning-change provenance
-
-- **Original:** “assert that every merged commit passed every required gate, evaluated AGAINST THAT COMMIT'S OWN TREE — not against current main.”
-- **Restatement:** The repository verifier performs current-tree verification and is structurally incapable of asserting history provenance. RM-60 supplies the provider-controlled/protected pre-execution boundary before any repository-controlled lifecycle code executes.
-- **Reason:** `pnpm install` executes PR-controlled lifecycle code before `gate:verify`; therefore no local ref, git config, remote URL, constant, or author-positioned path in the checkout is a trustworthy history anchor. A local disclaimer would be a green wearing a note, not a property. The history-provenance claim is removed rather than weakened.
-
-### Acceptance criteria
-
-1. `RM02-AC-01`: A healthy current tree returns zero while prominently reporting the queue guard's required-versus-actual `DEFECT (owner: RM-03)` delta.
-2. `RM02-AC-02`: Externally mutate any registered gate at its declared inerting point so its failure path succeeds; verification returns nonzero and names that gate. The verifier's internal meta-control is observed red before its healthy result is trusted.
-3. `RM02-AC-03`: An executable added under a declared gate root without an entry returns nonzero and includes `unregistered gate`.
-4. `RM02-AC-04`: A gate with zero must-fail cases returns nonzero and includes `no negative control`.
-5. `RM02-AC-05`: Unbound or semantically misbound criteria, prose claims bound to unrelated cases, unbound governing prose markers, ownerless behavior deltas, stale mutations, source/deployed drift, and modeled compatibility conflicts each return nonzero with the responsible stable ID. A simultaneous stale fixture or independent phase error SHALL NOT mask responsible stable-ID diagnostics. Registered meta-negative controls move a criterion binding, remove meaning provenance, and redirect a prose claim to an unrelated case; each is observed red for its stated reason.
-6. `RM02-AC-06`: CI configuration invokes the verifier unconditionally on every pull request.
-7. `RM02-AC-07`: PR output states adjacent `DOES`/`DOES NOT` boundaries: the repository layer verifies current-tree registered cases, same-checkout inventory drift, and evidence-side subject consumption; it does not establish history provenance at all. **Detects accidental and incompetent inventory drift within a checkout; does NOT survive an adversary who rewrites baseline, manifest, and verifier consistently — that guarantee requires RM-60's external boundary.**
-8. `RM02-AC-08`: Registered must-fail controls reject an emptied registry; shrinking the verifier inventory and manifest together; overstating the same-checkout inventory boundary; adding history/ancestry/lineage success to the closed observation renderer or bypassing renderer consumption; a misspelled nested outcome field; a wrong outcome field type; and a present-but-empty outcome pattern.
-9. `RM02-AC-09`: Population controls iterate every gate listed in the baseline and prove consumed evidence-subject mismatch and wrong-type comparison input are rejected for each gate. `RM02-EVIDENCE-SUBJECT-BINDING`, `RM02-TYPE-STRICT-SCHEMA`, `RM02-HISTORY-PROVENANCE-EXCLUDED`, and `RM02-NONEMPTY-ANCHORED-QUANTIFICATION` are bidirectionally bound to their must-fail controls.
-
-### Risks, dependencies, and verification boundary
-
-- **DOES:** The repository verifier proves declared current-tree controls, modeled scenarios, bidirectional criterion/case relationships, source/deployed equality at execution time, a same-checkout seven-gate baseline comparison, and evidence-side subject consumption.
-- **DOES NOT:** This layer establishes no history provenance. PR-controlled lifecycle code executes before the gate, so no local git state in the checkout is trustworthy as a history anchor. RM-60 owns the provider-controlled/protected pre-execution boundary. The production verifier has no history verifier path, and its closed current-tree observation renderer cannot represent a history-provenance success state.
-- **Detects accidental and incompetent inventory drift within a checkout; does NOT survive an adversary who rewrites baseline, manifest, and verifier consistently — that guarantee requires RM-60's external boundary.** A registered claim control fails if the checked artifacts overstate this boundary.
-- The verifier does **not** infer arbitrary-English semantics or defend against an actor able to rewrite the gate, registry, verifier, controls, and baseline consistently.
-- `ASSUMPTION:` RM-54 is the owner for expanding registration and prose-marker coverage beyond this approved seven-gate slice; rationale: the remediation task graph already assigns the fleet-wide inert-gate audit there.
-
----
-
 ## Problem Statement
 
 Jarvis (v0.2.0) is a self-hosted AI assistant with a Python FastAPI backend and Next.js frontend. It handles chat, projects, tasks, and LLM routing but lacks orchestration depth, agent coordination, shared memory, and remote access. The Mosaic framework (`~/.config/mosaic`) provides agent guides, shell-based orchestration tools, and quality rails — but these are loose scripts, not an integrated platform. The `@mosaicstack/*` packages in mosaic-mono-v0 began consolidating these into TypeScript packages (brain, queue, coord, cli, prdy, quality-rails) but have no UI, no auth, and no agent runtime integration.

docs/SITEMAP.md

@@ -1,11 +1,5 @@
 # Documentation Sitemap
 
-## Gate verification
-
-- [Developer gate registry guide](DEVELOPER-GUIDE/quality-gate-registry.md) — manifest schema, negative controls, evidence-side subjects, and the enforced RM-60 history-provenance exclusion. Detects accidental and incompetent inventory drift within a checkout; does NOT survive an adversary who rewrites baseline, manifest, and verifier consistently — that guarantee requires RM-60's external boundary.
-- [Gate registry operations](ADMIN-GUIDE/quality-gate-registry.md) — routine verification, failure interpretation, registry updates, and unconditional CI behavior.
-- [RM-02 governing claim index](remediation/GATE-CLAIMS.md) — marker bindings for orchestrator-owned remediation claims without modifying task tracking.
-
 ## Compaction refresh lease broker
 
 - [Internal broker protocol](architecture/lease-broker-protocol.md) — kernel identity, ancestry and generation invariants, framed requests, responses, and persisted cycle bindings.

docs/plans/2026-08-01-rm-02-gate-registry.md

@@ -1,95 +0,0 @@
-# RM-02 Gate Registry Implementation Plan
-
-> **For Pi:** Use test-driven development and execute each task RED → GREEN → refactor.
-
-**Goal:** Build a machine-readable seven-gate registry and an unconditional CI verifier that detects inert gates, binds criteria to observed negative controls, records defects honestly, and verifies the current PR tree unprivileged and fail-closed.
-
-**Architecture:** A dependency-free Node CLI reads `gates/gates.manifest.json` and the same-checkout `gates/required-gates.baseline.json`, validates closed schemas and references, then runs typed cases in isolated main-disk fixtures. Detects accidental and incompetent inventory drift within a checkout; does NOT survive an adversary who rewrites baseline, manifest, and verifier consistently — that guarantee requires RM-60's external boundary. Gate-specific fixture setup remains declarative; exact invocations, evidence-side subjects, and exact observed/required exits stay in JSON. The production verifier is structurally incapable of asserting history provenance; RM-60 owns the provider-controlled/protected pre-execution boundary.
-
-**Tech Stack:** Node.js ESM, `node:test`, JSON, shell gates, pnpm, Woodpecker CI.
-
----
-
-### Task 1: Meta-negative-control kernel
-
-**Files:**
-
-- Create: `scripts/gate-verify.test.mjs`
-- Create: `scripts/gate-verify.mjs`
-
-1. Write a black-box fixture whose gate failure branch has already been changed to success.
-2. Run `node --test scripts/gate-verify.test.mjs`; require failure because the absent verifier does not name the inert gate.
-3. Implement manifest loading, exact process execution, and named mismatch reporting only.
-4. Re-run and require the external inert mutation to produce verifier nonzero while the test passes.
-5. Add an internally applied declared mutation and require a healthy fixture to report its negative control armed.
-
-### Task 2: Registry structural clauses
-
-**Files:**
-
-- Modify: `scripts/gate-verify.test.mjs`
-- Modify: `scripts/gate-verify.mjs`
-
-Add failing tests, one behavior at a time, for: `unregistered gate`; `no negative control`; unbound criterion; unbound `GATE-CLAIM`; ownerless required/actual delta; stale/ambiguous/ineffective mutation; direct modeled conflict; missing meaning-change provenance. Implement the minimum validator after each observed RED.
-
-### Task 3: Gate fixtures and seven-gate manifest
-
-**Files:**
-
-- Create: `gates/gates.manifest.json`
-- Create: `gates/fixtures/quality-case.mjs`
-- Create: `gates/fixtures/preflight-case.mjs`
-- Create: `gates/fixtures/queue-case.sh`
-- Create: `gates/fixtures/hook-case.sh`
-- Modify: `scripts/gate-verify.test.mjs`
-
-Register typecheck, lint, format, RM-01 preflight, queue guard, pre-commit, and pre-push. For each, first run its known-bad case against an intentionally inert fixture and observe verifier RED; then restore the real gate behavior and require its exact observed exit/reason. Record queue defects as required/actual deltas owned by RM-03, never as pass/green/OK.
-
-### Task 4: Source-versus-deployed identity
-
-**Files:**
-
-- Modify: `gates/gates.manifest.json`
-- Modify: `scripts/gate-verify.test.mjs`
-- Modify: `scripts/gate-verify.mjs`
-
-Write and observe a failing test with a byte-mutated deployed counterpart. Implement byte equality and internal drift mutation controls. Declare `none` explicitly for gates without deployed counterparts.
-
-### Task 5: Prose claims and compatibility constructions
-
-**Files:**
-
-- Modify: `docs/remediation/MISSION.md`
-- Modify: `docs/remediation/TASKS.md` only if coordinator authorization overrides the worker prohibition; otherwise place markers in an RM-02 claim index that references immutable source anchors.
-- Modify: `gates/gates.manifest.json`
-- Modify: verifier tests/implementation.
-
-Enumerate current security/integrity claims, bind each marker/id to a negative case, and reject unbound markers. Execute finite compatibility scenarios and clearly document that arbitrary English consistency is outside the model.
-
-### Task 6: Current-tree boundary and enforced history-provenance exclusion
-
-**Files:**
-
-- Create: `gates/required-gates.baseline.json`
-- Create: `scripts/gate-history-exclusion-control.mjs`
-- Create: `scripts/gate-inventory-shrink-control.mjs`
-- Modify: `scripts/gate-verify.mjs`
-- Modify: `gates/gates.manifest.json`
-
-Verify current-tree behavior only. Remove the anchor-dependent history verifier and provider-history consumption because PR-controlled lifecycle code executes before the gate and makes every local git anchor untrustworthy. Use a closed current-tree observation renderer and register a must-fail control that turns red if history/ancestry/lineage success becomes representable or production output bypasses renderer consumption. Compare the verifier inventory and manifest separately against the same-checkout baseline, register must-fail attacks that shrink either paired representation, and register an overclaim control. Detects accidental and incompetent inventory drift within a checkout; does NOT survive an adversary who rewrites baseline, manifest, and verifier consistently — that guarantee requires RM-60's external boundary. State both directions: current-tree controls, inventory shape, and evidence subjects are enforced here; history provenance is not established until RM-60 provides a provider-controlled/protected pre-execution boundary.
-
-### Task 7: CI and documentation
-
-**Files:**
-
-- Modify: `package.json`
-- Modify: `.woodpecker/ci.yml`
-- Create/update: `docs/DEVELOPER-GUIDE/quality-gate-registry.md`
-- Create/update: `docs/ADMIN-GUIDE/quality-gate-registry.md`
-- Modify: `docs/SITEMAP.md`
-
-Add `gate:verify`; run it in an unconditional PR/main CI step. Document invocation, defect semantics, coverage/exclusions, marker syntax, replay/provider boundaries, and source/deployed identity.
-
-### Task 8: Verification and delivery
-
-Run focused tests, `pnpm gate:verify`, checkout tests, typecheck, lint, format, and applicable integration tests. Run Codex code and security review; remediate and re-review. Verify authorship, commit, execute queue guard before push, push, create PR via Mosaic wrapper, and send exact-head review request to rev-974 through the coordinator. Do not merge without coordinator authorization.

docs/remediation/BOARD-LEDGER.md

@@ -13,13 +13,3 @@ Correct for the CI container (runs as root), fatal for EVERY non-root local chec
 ### **D-2 / hygiene — husky `prepare` fails `EPERM` copying into root-owned `.husky/_/`.** Repo working
 
 tree has root-owned dirs (`.husky/`, repo root) under a non-root agent. Worked around with the intended `HUSKY=0` escape hatch (does NOT disable the existing pre-commit/pre-push hooks).
-
-<!-- board-roll: 2 entries rolled from BOARD.md -->
-
-### **D-5 / P-QUEUE-001 + P-CONFORMANCE-001 — KEYSTONE: an inert gate that erased its own evidence.**
-
-Merged PR #868 (`b79336a8`) shipped a file that FAILS `pnpm format:check` ⇒ the CI format gate did not block. An unrelated later PR (#872) then reformatted that file via its own `lint-staged`, so `main` went green again and nobody learned the gate had failed to fire. Verified blob-level under the repo's own config. **Detection must be per-merge-commit against that commit's own tree** — a "is main green today" check reports all-clear on this exact defect. Binding on RM-02/RM-55. Full chain in `TASKS.md` §1a. NOT quiet-patched, by Mos's ruling: patching the symptom destroys the signal.
-
-### **D-4 / P-LIFECYCLE + hygiene — a dispatched agent silently IGNORED an in-message context reset.**
-
-planner-sol was at 64.3%/372k; the brief asked it to reset first; it began work on dirty context anyway. Only an out-of-band `/new` driven by the orchestrator guaranteed clean state. Confirms the postmortem thesis: **instructions are not enforcement.** Reset must be a mechanical pre-dispatch step, not a request.

docs/remediation/BOARD.md

@@ -1,6 +1,6 @@
 # mos-remediation — LIVE BOARD (keep < 8 KB)
 
-**Phase:** EXECUTING — P0 open. RM-01 MERGED; RM-02 (keystone gate registry) is next.
+**Phase:** EXECUTING — first PR merged; RM-01 in flight; all 3 decisions ruled.
 **Updated:** 2026-07-31 (mos-remediation orchestrator; seat active on `mosaic-fleet`).
 
 ## Head
@@ -16,13 +16,14 @@
 
 ## In-flight
 
-| Task                                | Owner           | State                                                                     |
-| ----------------------------------- | --------------- | ------------------------------------------------------------------------- |
-| RM-01 reproducible checkout         | —               | **MERGED** `f58b3699` (PR #1027) — rev-974 APPROVE + CI #2172 8/8 green   |
-| RM-02 gate registry ★keystone       | unassigned      | **READY** — depends only on RM-01; not held by RM-03                      |
-| RM-03 queue guard (3 defects)       | —               | HOLD — #1023 SUPERSEDED-PENDING-JASON                                     |
-| RM-59 close D-19 residual risk      | —               | BLOCKED by RM-12/RM-21/RM-25 (spine + executor) — tracked edge, not prose |
-| `remediation/state` snapshot → main | mos-remediation | opening at this mission seam                                              |
+| Task                                              | Owner           | State                                                              |
+| ------------------------------------------------- | --------------- | ------------------------------------------------------------------ |
+| PR #1026 docs (mission record + backlog)          | mos-remediation | OPEN, retargeted to main, rebased; diff verified docs-only         |
+| PR #1025 hygiene                                  | —               | **MERGED** 52414605; rev-974 APPROVE + CI #2158 8/8 terminal-green |
+| DECISION-1 wire-in point (charter change)         | Mos / Jason     | ESCALATED — both planners reject the charter's target              |
+| DECISION-2 rollback artifact + availability trade | Jason           | ESCALATED                                                          |
+| DECISION-3 RM-03 vs parked PR #1023 ownership     | Mos             | ESCALATED                                                          |
+| RM-01 reproducible checkout (unblocks everything) | unassigned      | READY TO DISPATCH                                                  |
 
 ## Fleet seats
 
@@ -38,14 +39,6 @@
 - Freeze: LIFTED for this workstream only.
 - Git identity: `MOSAIC_GIT_IDENTITY=mos-dt-0` INTERIM. Mos ruled gate-16 HOLDS (author≠reviewer is what
   gate-16 protects; rev-974 reviews, mos-dt-0 never self-reviews). Dedicated identity TRACKED, Mos provisions.
-- Capability check (D-11b): before dispatching seat X to provider Y, verify
-  `~/.config/mosaic/secrets/gitea-tokens/gitea-<Y>-<X>.token` exists. Token-file set = authoritative
-  capability registry. Mos owns provisioning; escalate missing pairs to him.
-- Seat identity (D-11a): token identity AND `git config user.name`/`user.email` must BOTH be set and
-  agree. Exporting `MOSAIC_GIT_IDENTITY` alone does NOT fix commit authorship.
-- Standing worker-brief doctrine (accreted, mandatory in every brief): don't weaken a RED test to make
-  it pass; if a check is unrunnable as written SAY SO, never silently substitute; `agent-send -f` never
-  `-m`; heavy artifacts off shared `/tmp`.
 - Remote control: native `/remote-control` NOT wired in this runtime. Path is **Mos-relay**
   (Jason ↔ mos-claude via Discord ↔ mos-remediation via agent-send). Not a blocker.
 
@@ -79,6 +72,14 @@ PR #1025 AC2's fixture `mkdir -p apps/*/venv/lib` creates a literal `apps/*/venv
 
 Running the required `ci-queue-wait.sh --purpose push` before pushing produced `state=unknown ... exit 0` — the exact defect at `ci-queue-wait.sh:282-288` that PR #1023 is parked on. It also evaluated `branch=main` rather than the branch being pushed. The mission's own required pre-push gate passed me on an indeterminate result. Third independent live instance of the class.
 
+### **D-5 / P-QUEUE-001 + P-CONFORMANCE-001 — KEYSTONE: an inert gate that erased its own evidence.**
+
+Merged PR #868 (`b79336a8`) shipped a file that FAILS `pnpm format:check` ⇒ the CI format gate did not block. An unrelated later PR (#872) then reformatted that file via its own `lint-staged`, so `main` went green again and nobody learned the gate had failed to fire. Verified blob-level under the repo's own config. **Detection must be per-merge-commit against that commit's own tree** — a "is main green today" check reports all-clear on this exact defect. Binding on RM-02/RM-55. Full chain in `TASKS.md` §1a. NOT quiet-patched, by Mos's ruling: patching the symptom destroys the signal.
+
+### **D-4 / P-LIFECYCLE + hygiene — a dispatched agent silently IGNORED an in-message context reset.**
+
+planner-sol was at 64.3%/372k; the brief asked it to reset first; it began work on dirty context anyway. Only an out-of-band `/new` driven by the orchestrator guaranteed clean state. Confirms the postmortem thesis: **instructions are not enforcement.** Reset must be a mechanical pre-dispatch step, not a request.
+
 <!-- BOARD-ROLL:END -->
 
 ## Decisions log

docs/remediation/GATE-CLAIMS.md

@@ -1,40 +0,0 @@
-# RM-02 Governing Claim Index
-
-This index binds remediation claims that live in orchestrator-owned `TASKS.md` without modifying that file. The source heading and quoted text are the reviewable anchor; `gate:verify` enforces each marker-to-criterion binding. Marker completeness beyond this approved slice remains RM-54.
-
-## Prose is an enforceable claim
-
-<!-- GATE-CLAIM:PROSE-IS-A-CLAIM -->
-
-- Source: `docs/remediation/TASKS.md`, heading `D-20 — the orchestrator's own documentation overclaimed, and a reviewer disproved it empirically`.
-- Anchored text: “The defect was not in the code — it was in this file.”
-
-## Generated-state verification scope
-
-<!-- GATE-CLAIM:GENERATED-STATE-SCOPE -->
-
-- Source: `docs/remediation/TASKS.md`, heading `D-19 — an integrity property that cannot exist at the layer it was specified`.
-- Anchored text: “a verifier that cannot detect the attack is not a verifier.”
-
-## Execution trust boundary
-
-<!-- GATE-CLAIM:EXECUTION-TRUST-BOUNDARY -->
-
-- Source: RM-02 ruling recorded under `docs/remediation/TASKS.md`, RM-02 clause 4, D-25.
-- Anchored text: “SELF-VERIFICATION BY THE AUDITED PARTY IS NOT VERIFICATION.”
-- Dependency: RM-60/#1031, cross-referenced with RM-59.
-
-## Same-checkout inventory drift boundary
-
-<!-- GATE-CLAIM:INVENTORY-DRIFT-BOUNDARY -->
-
-- Source: RM-02 ruling after D-48/CWE-353 reproduced against the round-4 baseline.
-- Boundary: Detects accidental and incompetent inventory drift within a checkout; does NOT survive an adversary who rewrites baseline, manifest, and verifier consistently — that guarantee requires RM-60's external boundary.
-- Negative control: `checkout-preflight/inventory-claim-overstatement` rewrites the boundary as protection and must go red.
-
-## Criterion restatement provenance
-
-<!-- GATE-CLAIM:CRITERION-RESTATEMENT -->
-
-- Source: `docs/remediation/TASKS.md`, heading `D-18 — two pre-registered criteria were mutually unsatisfiable, discoverable only at implementation`.
-- Anchored text: “Both criteria were pre-registered. They cannot both be satisfied.”

docs/remediation/KICKSTART.md

@@ -7,15 +7,10 @@ mechanically until Build 3 (rotation) makes it automatic.
 
 ## On resume (do in order, before any orchestration action)
 
-1. `cd /src/mosaic-stack`, then **`git fetch origin remediation/state`**.
-   ⚠ **The live board is on the rolling branch `remediation/state`, NOT on `main`.** `main` carries only
-   periodic snapshots, so reading the board from `main` will silently give you a STALE tick. Read the
-   live files at `origin/remediation/state` (e.g. `git show origin/remediation/state:docs/remediation/BOARD.md`),
-   or check that branch out. Every tick is pushed there immediately, so its HEAD is always the newest state.
+1. `cd /src/mosaic-stack` and confirm you are on the remediation working branch.
 2. Read `docs/remediation/MISSION.md` — the charter (goal, 4 builds, 15 decisions, sequencing, directives).
-3. Read `docs/remediation/BOARD.md` **at `origin/remediation/state`** — the LIVE state: current phase,
-   in-flight tasks, fleet seat assignments, gate status. Single source of in-flight truth (kept < 8 KB;
-   older entries roll to `BOARD-LEDGER.md` via `board-roll.sh`).
+3. Read `docs/remediation/BOARD.md` — the LIVE state: current phase, in-flight tasks, fleet seat assignments,
+   gate status. This is your single source of in-flight truth (kept small).
 4. Read the discussion checkpoint for full rationale if needed:
    `../jarvis-brain/docs/scratchpads/postmortem/REMEDIATION-DISCUSSION-STATE.md` (or the jarvis-brain repo path).
 5. **Residency attestation (fail-closed):** restate from the reloaded files — (a) the goal in one line, (b) the

docs/remediation/MISSION.md

@@ -1,7 +1,7 @@
 # Mosaic Stack Remediation — Mission Charter
 
 **Owner:** project orchestrator `mos-remediation` (Claude, launched in `/src/mosaic-stack`).
-**Origin:** 2026-07-16..31 fleet lifecycle postmortem. **Status:** EXECUTING (planning complete; RM-01 in flight).
+**Origin:** 2026-07-16..31 fleet lifecycle postmortem. **Status:** PLANNING (task decomposition).
 **HOLD lifted** for this workstream by Jason, 2026-07-31 — "begin full mosaic fleet operation on this."
 
 ## Goal
@@ -10,112 +10,23 @@ Convert the 15 accepted postmortem remediation proposals into a working, **dogfo
 **North star:** anything with a deterministic right answer moves OUT of the LLM into a deterministic
 gate/program; the LLM handles only genuine judgment.
 
-### First-class principle — observe the property, not the exit code
-
-<!-- GATE-CLAIM:OBSERVE-PROPERTY -->
-
-> **No write is done until the requested PROPERTY is observed. A success exit code is not evidence.**
->
-> **Success output is designed to be believed.** That is the whole reason the inert-gate class exists
-> and why P-WRAPPER-001's tri-state (`verified` / `written-unverified` / `failed`) is not optional. The
-> failure is not carelessness — a green is _engineered_ to be trusted, so trusting it is the default
-> behaviour of a competent operator, not a lapse.
->
-> Promoted to the charter by Mos (2026-07-31) after the orchestrator committed this exact error: a
-> `--draft` flag was silently dropped by a wrapper fallback that still exited 0, and the PR was reported
-> as a draft on the strength of the exit code rather than an observed `draft: true` (D-12). Twelve
-> failure instances were banked in that session; **three of them were the orchestrator's own.** That
-> ratio is the point — the mechanism must catch the mechanic too, or it is not a mechanism.
->
-> Operationally: after any write, read back the property you required. Applies to gates, wrappers, PR
-> flags, commit authorship, file installs, and message delivery alike.
-
-### First-class principle — pre-registration prevents retrofitting, and nothing else
-
-<!-- GATE-CLAIM:PREREGISTRATION-BOUNDARY -->
-
-> **A pre-registered check set can fail in three distinct ways:**
->
-> | mode                        | the set is…                                       | found as |
-> | --------------------------- | ------------------------------------------------- | -------- |
-> | **WRONG**                   | a check does not test what it claims              | D-8      |
-> | **INCOMPLETE**              | green while a criterion's requirement is untested | D-17     |
-> | **INTERNALLY INCONSISTENT** | two criteria cannot both hold                     | D-18     |
->
-> **Pre-registration protects against exactly one thing: retrofitting a check to fit the implementation
-> it is supposed to judge.** It confers neither correctness, nor coverage, nor consistency. "We
-> pre-registered the checks" has been treated as though it settled the question — it settles one of
-> three.
->
-> Promoted to the charter by Mos (2026-07-31). All three modes were found on this mission's own **first
-> delivery**, by the machinery applied to its own work — not by inspection, and not by looking for them.
->
-> **Enforceable form — RM-02's four clauses.** The registry must establish that: (1) each check is
-> **right** — proven red for its own stated reason before its green counts; (2) the set **covers** —
-> every criterion bound to a case that actually exercises it; (3) no two criteria **conflict** —
-> mutual unsatisfiability is a registry defect discoverable by construction; (4) when a criterion's
-> meaning changes, the registry **retains original text, restatement, and reason**, so evolution stays
-> auditable. A criterion with no case that can fail for its own reason is unregistered in substance,
-> however it reads in the manifest.
-
-### Corollary — never ship an integrity claim dressed as a property
-
-<!-- GATE-CLAIM:ARTIFACT-INTEGRITY-BOUNDARY -->
-
-> A verification artifact that can be forged by whoever it is meant to catch verifies nothing. If a
-> manifest, marker, ledger, or receipt is writable by the same actor whose behaviour it certifies, it
-> **certifies the attack.** Such an artifact must sit inside the integrity envelope it belongs to,
-> publish atomically, and carry a **tamper negative-control observed red** — otherwise its integrity is
-> a _claim_, not a _property_.
->
-> **If it cannot be made tamper-evident, say so and reconsider the approach.** Laundering foreign
-> content as certified is the only unacceptable outcome; an honest "this cannot be verified" is always
-> available and always preferable.
-
-### First-class principle — when a property cannot exist at the layer it was specified
-
-<!-- GATE-CLAIM:IMPOSSIBLE-LAYER-BOUNDARY -->
-
-> Some required properties are **impossible at the layer that asked for them** — not hard, impossible.
-> A local check cannot defend against an actor who can rewrite the check itself. When that happens,
-> there are exactly three honest moves, and all three are mandatory:
->
-> 1. **Implement what the layer _can_ guarantee.** Partial protection against the class it was actually
->    born from is worth having.
-> 2. **State the boundary precisely, in BOTH directions.** What it does _not_ defend, **and** beside it
->    what it _does_. A reader who sees only the negative dismisses the check as worthless; one who sees
->    only the positive over-trusts it. **Both together is the honest artifact** — either alone misleads.
-> 3. **Record where the real guarantee will come from — as a TRACKED DEPENDENCY, not prose.** It must
->    name a task that someone must close. _A documented gap with no owner becomes a permanent gap that
->    reads as intentional._
->
-> **A written-down gap is acceptable engineering. An implied-fixed gap is this mission's core failure in
-> a new costume** — a verification artifact that verifies nothing, with a green to prove it.
->
-> Promoted to the charter by Mos (2026-07-31) from D-19. Origin: the RM-01 symlink manifest could not be
-> made tamper-evident against a same-UID actor (CWE-345), because the manifest and its marker share one
-> writable tree. The implementing seat **escalated rather than relabelling self-authentication as
-> tamper-resistance** — the corollary above firing on its first real adversarial test, on the cheapest
-> seat in the loop. Residual risk bound to **RM-59** (`depends_on: RM-12, RM-21, RM-25`), where the
-> choke-point executor and spine verify from _outside_ the worktree's authority.
-
 ## Decision record (authoritative, immutable)
 
 - **15/15 proposals decided: 13 accept, 2 modify (P-AUTHORITY-001, P-INBOX-001), 0 reject.**
 - Site + `annotations.json`: `jarvis-brain/docs/postmortem-spec/site/` (committed, origin/main).
 - Discussion checkpoint (rich rationale per proposal): `jarvis-brain/docs/scratchpads/postmortem/REMEDIATION-DISCUSSION-STATE.md`.
 - Postmortem report: mosaicstack/stack PR #107 (merged 88f4ee04).
-- MACP wiring scout (verdict c=STRANDED): [`MACP-WIRING-SCOUT.md`](./MACP-WIRING-SCOUT.md) (copied into this dir; TODO discharged). Its findings are sound; its _recommended wire-in point_ is superseded by DECISION-1.
+- MACP wiring scout (verdict c=STRANDED): `/tmp/macp-wiring-investigation.md` (copy into this dir — see TODO).
 
 ## The plan — 15 proposals collapse to 4 builds + hygiene
 
-| Build                                                        | Absorbs                                 | What it is                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
-| ------------------------------------------------------------ | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| **1. One choke-point service** (mechanical enforcer)         | MISSION, STATE, AUDIT, WRAPPER, QUEUE   | Deterministic program every task/data mutation flows through. **Wire the stranded `@mosaicstack/macp`** — typed tasks, gate-runner, event ledger, credential binding, tri-state write outcomes. ⚠ **Target CORRECTED 2026-07-31 (DECISION-1, Mos):** a new production Node `TaskExecutor` on the **live** dispatch path (`packages/mosaic` launch + `packages/coord`), which Coord/Forge/live-dispatch submit through. **NOT** `mosaic_orchestrator.py::run_single_task` — that controller is `"enabled": false` and references a dispatcher absent from this checkout; wiring it would strand the executor, reproducing this mission's own disease. The Python rail is **deleted**, not ported. Both planners reached this independently. |
-| **2. One durable spine + hot path**                          | (storage under everything)              | **PG system-of-record + Redis hot queue** (transactional-outbox). Mission/tasks/state-claims/audit-ledger/comms-inbox all land here.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
-| **3. Rotation lifecycle** (finish the Mission Control Plane) | LIFECYCLE, CONTRACT, GUIDE, RECOVERY    | Coordinator daemon: contract-hash binding, compaction-detected → rotate-not-compact, checkpoint→fresh-session→rehydrate, broker-independent recovery. Deterministic, not an LLM. Reuse `packages/coord`; existing PRD at `docs/mission-control/`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
-| **4. Comms service**                                         | AUTHORITY, INBOX (+ versioning roadmap) | Envelope (comms/v1) → sole-path service → PG/Redis → pluggable adapters (tmux→Matrix/Discord/Slack/Telegram). Version the protocol, not participants.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| **+ Hygiene & proof**                                        | FLEET, WORKFLOW, CONFORMANCE            | One roster-owned socket/host + stale GC; allowlist auto-sync; the conformance harness that fault-injects the failure classes and proves builds 1–4 hold.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| Build                                                        | Absorbs                                 | What it is                                                                                                                                                                                                                                        |
+| ------------------------------------------------------------ | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **1. One choke-point service** (mechanical enforcer)         | MISSION, STATE, AUDIT, WRAPPER, QUEUE   | Deterministic program every task/data mutation flows through. **Wire the stranded `@mosaicstack/macp`** in at `mosaic_orchestrator.py::run_single_task` — typed tasks, gate-runner, event ledger, credential binding, tri-state write outcomes.   |
+| **2. One durable spine + hot path**                          | (storage under everything)              | **PG system-of-record + Redis hot queue** (transactional-outbox). Mission/tasks/state-claims/audit-ledger/comms-inbox all land here.                                                                                                              |
+| **3. Rotation lifecycle** (finish the Mission Control Plane) | LIFECYCLE, CONTRACT, GUIDE, RECOVERY    | Coordinator daemon: contract-hash binding, compaction-detected → rotate-not-compact, checkpoint→fresh-session→rehydrate, broker-independent recovery. Deterministic, not an LLM. Reuse `packages/coord`; existing PRD at `docs/mission-control/`. |
+| **4. Comms service**                                         | AUTHORITY, INBOX (+ versioning roadmap) | Envelope (comms/v1) → sole-path service → PG/Redis → pluggable adapters (tmux→Matrix/Discord/Slack/Telegram). Version the protocol, not participants.                                                                                             |
+| **+ Hygiene & proof**                                        | FLEET, WORKFLOW, CONFORMANCE            | One roster-owned socket/host + stale GC; allowlist auto-sync; the conformance harness that fault-injects the failure classes and proves builds 1–4 hold.                                                                                          |
 
 ## The finding that sets the cost
 
@@ -126,7 +37,6 @@ orphaned context loader, a fail-open bypass. **Work = wire + consolidate + retir
 ## Sequencing (skeleton — adversarial decomposition refines this)
 
 1. **Spine + choke-point service** (builds 1+2) — foundation; unlocks MISSION/STATE/AUDIT/WRAPPER/QUEUE at one integration point.
-   (Per DECISION-1, a P0 phase of provable-gate + activation work precedes this; see `TASKS.md` §3.)
 2. **Rotation daemon** (build 3) on that spine — the drift fix proper.
 3. **Comms service** (build 4) — envelope → service → PG/Redis → adapters; retire direct-tmux.
 4. **Hygiene + conformance** (build 5) — fleet convergence, allowlist sync, dogfood harness.
@@ -140,11 +50,6 @@ orphaned context loader, a fail-open bypass. **Work = wire + consolidate + retir
   (WRAPPER), auto-sync sweep (WORKFLOW), #1018 stale-consumed (INBOX). The fleet is its own test bed.
 - **Orchestration tracking → DB**, hard cutover ("rip off the bandaid"), NO flat-file interim. jarvis-brain
   PDA flat-files untouched. Current flat-file tracking runs as-is/unhardened until DB tracking is real, then one clean replace.
-  - ⚠ **QUALIFIED 2026-07-31 (DECISION-2, Mos):** the DB spine **must NOT be a single-point hard-stop.**
-    A broker-independent / degraded mode **and** a rehearsed rollback artifact are **design requirements**
-    (P-RECOVERY-001), binding now on RM-12, RM-13, RM-23, RM-36 and RM-53. This **supersedes** the earlier
-    orchestrator recommendation to pre-commit "no DB ⇒ the fleet stops" — that answer is _not_ on record.
-    Only the specific availability _target_ remains open, queued for Jason; it does **not** block current work.
 
 ## The 15 decisions (one-line; full rationale in the checkpoint)
 

docs/remediation/TASKS.md

@@ -93,520 +93,6 @@ and must not be cited as merge evidence. Rely on reviewer clearance + real CI.
 Three independent live instances in a single session — format gate, agent context reset, queue guard —
 is the class confirmed, not anecdote.
 
-### D-20 — the orchestrator's own documentation overclaimed, and a reviewer disproved it empirically
-
-`rev-974` blocked PR #1027 a second time. **The defect was not in the code — it was in this file**, at
-D-18's entry, written by the orchestrator.
-
-Two faults, both mine:
-
-1. **D-18's AC2 restatement omitted the scope clause** that D-19 later established as mandatory
-   ("within an accidental/independent-mutation threat model").
-2. **D-18 asserted that the tampered-manifest control turns integrity "from a claim into a property."**
-   It does not, and _cannot_. That sentence was written **before** D-19 proved the property impossible
-   at this layer, and was never revised when D-19 landed.
-
-**The reviewer did not merely read it — it disproved it.** It performed a **same-UID consistent
-manifest + marker rewrite**, and **preflight passed**. My documented claim was falsified by experiment.
-Code, README, scratchpad and PR body all stated both threat-model directions correctly; **this file was
-the only place still overclaiming.**
-
-**This is two banked findings firing on the orchestrator at once:**
-
-- **The integrity-claim corollary** — I wrote an integrity _claim_ in the voice of an integrity
-  _property_, in the very document that defines the rule against doing so.
-- **D-14 (propagation)** — D-19 superseded D-18's assertion. I propagated the consequence into the
-  charter and the delivery conditions, but **not back into D-18 itself.** A ruling that fails to
-  propagate _backwards_ into the finding it supersedes is the same defect as one that fails to
-  propagate forwards, and I did not audit for that direction.
-
-**Corrected in place**, with the original wording quoted and the empirical disproof recorded, rather
-than silently rewritten — the same standard demanded of any restated criterion.
-
-**Requirement on RM-02 (fifth clause).** Documentation asserting a _security or integrity_ property is
-itself a claim requiring a negative control. Where a document states "X is guaranteed", the registry
-must hold a case that **fails if X is not guaranteed** — and that case must have been observed red.
-**Prose is not exempt from the mission's own evidentiary standard**, and prose in the _governing_
-document least of all: it is the artifact most likely to be quoted as authority long after the code has
-moved on.
-
-**Reviewer credit.** rev-974 was briefed that its highest-priority check was "confirm the PR claims no
-more than it can deliver, and a softened or omitted boundary is a finding even though the code works."
-It applied that instruction **to the orchestrator's own governing document** and produced an experiment
-to settle it. That is the review standard this mission is trying to make ordinary.
-
-### D-19 — an integrity property that cannot exist at the layer it was specified
-
-Implementing D-18's manifest, the seat + a Codex security review reached **CWE-345**: the symlink
-manifest and the source-hash marker both live in the **same same-UID writable generated tree**, so an
-actor with that UID can plant a rogue link, regenerate _both_, retain the fingerprint, and pass. **No
-local cryptographic construction fixes self-authentication** without a key outside that actor's
-authority; relocating the marker changes the path, not the authority.
-
-The seat **escalated rather than describing self-authentication as tamper-resistant** — the explicit
-failure mode the charter corollary demands. That is the corollary working, on its first real test.
-
-**Ruling — Option A: scope AC2 to accidental / independent / stale mutation; retain the design.**
-Rationale, recorded so it can be challenged:
-
-1. **The undefendable boundary is not the weak link.** An actor with same-UID write can already edit the
-   source, the tests, `scripts/preflight.mjs` itself, and `.husky/*`. If they have that, _nothing_ in the
-   local checkout is trustworthy — hardening the manifest buys no real security while **implying
-   protection that does not exist**, which is worse than the gap.
-2. **What AC2 is actually for.** These checks exist because a five-month-stale `.next` produced 19
-   phantom `TS2307` errors indistinguishable from real ones (**D-5**). That is staleness, drift and
-   foreign residue — and against that class the design demonstrably works.
-3. **A real trust anchor arrives later, from this mission's own architecture.** An anchor must live
-   outside the actor's authority; for a fleet running as one user that means a separate service —
-   precisely the **choke-point executor + PG spine** of Builds 1–2, which verify outside the worktree's
-   authority. Hand-rolling key distribution for a local preflight now would duplicate that work badly.
-4. Option C (structural policy, no manifest) is strictly worse — it cannot detect a **removed** expected link.
-
-**Option A is acceptable only with honest labelling**, or it becomes the disease it is meant to cure.
-Conditions (last two added/sharpened by Mos):
-
-- Threat model stated verbatim in the code **and** the PR; the words _tamper-proof / tamper-evident /
-  secure_ **barred** from that context; the scope carried in AC2's restatement; every control kept
-  RED-first including manifest-only tamper.
-- **State the boundary in BOTH directions.** Not only what it does _not_ defend (same-UID write; no
-  local construction can) but, beside it, what it **does** defend: accidental / independent / stale /
-  foreign-residue mutation — the **D-5** class it was born from (the five-month `.next` and its 19
-  phantom `TS2307`s). _A reader who sees only the negative dismisses the check as worthless; one who
-  sees only the positive over-trusts it. Both together is the honest artifact._
-- **The residual risk is a HARD TRACKED DEPENDENCY EDGE, not a comment.** It is **RM-59**, owned by the
-  choke-point executor + spine work (`depends_on: RM-12, RM-21, RM-25`), and the AC2 scope note must
-  cite that id. _"Record where the real guarantee comes from" only holds if the record is a live
-  dependency someone must close._ **A documented gap with no owner becomes a permanent gap that reads
-  as intentional.**
-
-**The generalizable rule.** When a required property **cannot exist at the layer where it was
-specified**, the honest moves are: implement what the layer _can_ guarantee, **state the boundary
-precisely**, and record where the real guarantee will come from. **A known gap that is written down is
-acceptable; a gap that is implied fixed is not.** Silence here would have shipped a verification
-artifact that verifies nothing — with a green to prove it.
-
-### D-18 — two pre-registered criteria were mutually unsatisfiable, discoverable only at implementation
-
-Implementing D-17's fix surfaced a conflict **between** pre-registered criteria:
-
-- **AC2** (as written) — reject symlinked generated state.
-- **AC4** — the canonical `pnpm -w build` succeeds and leaves no residue.
-
-Verified independently rather than taken on report: `apps/web/next.config.ts:4` sets
-`output: 'standalone'`, and the built tree contains **42 legitimate pnpm dependency symlinks** under
-`.next/standalone/node_modules`. A blanket descendant-symlink rejection makes the canonical build fail
-its own preflight with exit 43. **AC2 read literally is unsatisfiable alongside AC4 under this
-configuration**, and nothing short of building the tree would have revealed it.
-
-**Third distinct failure mode of a pre-registered check set**, completing the chain:
-
-| finding | a pre-registered check set can be…                                 |
-| ------- | ------------------------------------------------------------------ |
-| D-8     | **wrong** — a check that does not test what it claims              |
-| D-17    | **incomplete** — green while a criterion's requirement is untested |
-| D-18    | **internally inconsistent** — two criteria that cannot both hold   |
-
-The implementing seat escalated instead of silently picking a winner. That matters: **quietly resolving
-a conflict between pre-registered criteria destroys the point of pre-registering them** — the registration
-exists so that changes of meaning are auditable rather than absorbed.
-
-**Resolution (orchestrator ruling).** Approved a **build-certified symlink manifest**: `.next` itself is
-still rejected as a symlink; descendants are rejected unless _exactly_ certified by a manifest the build
-publishes atomically. Strictly **stronger** than blanket rejection — it also catches a **retargeted**
-symlink, which blanket rejection cannot distinguish from a legitimate one.
-
-**AC2 restated (recorded, not absorbed).** _Generated state must reject `.next` itself being a symlink
-or non-directory, and must reject any descendant symlink not exactly certified by the build manifest —
-added, removed, retargeted, or manifest-only-tampered all fail with exit 43 — **within an accidental /
-independent-mutation threat model.**_
-
-> ⚠ **This entry is superseded in part by [D-19](#d-19). Do not read D-18 standalone.** The scope clause
-> above is load-bearing: the design **cannot** defend against a same-UID actor, which can rewrite the
-> manifest and the marker consistently (CWE-345). D-18 was written **before** that impossibility was
-> established.
-
-**Hardening required before this counts.** The manifest is itself generated state, so **a manifest
-writable by whoever plants a rogue symlink certifies the attack** — that is the one way this design
-fails. It must sit inside the same ownership/fingerprint envelope, published atomically via the existing
-marker mechanism, with negative controls **observed red first** for: added, removed, retargeted,
-**manifest-only-tampered**, plus a positive control that the canonical build passes.
-
-> ⚠ **CORRECTED (D-20).** This paragraph originally ended: _"without it, integrity is a claim rather
-> than a property."_ **That overclaimed**, by implying the control makes integrity a _property_. It does
-> not, and cannot. The manifest-only-tamper control detects **independent** mutation of the manifest;
-> it confers **no authenticity** against an actor who rewrites manifest _and_ marker together.
-> `rev-974` disproved the original wording empirically — a same-UID consistent manifest+marker rewrite
-> **passed preflight**. Integrity here remains a scoped **drift-detection** property, never an
-> authenticity one. See D-19 and the charter principle on properties that cannot exist at their
-> specified layer.
-
-**Requirement on RM-02 (fourth clause).** The registry must detect **conflicts between registered
-criteria**, not only wrongness and coverage. Two criteria that cannot simultaneously hold is a registry
-defect discoverable by construction — and when a criterion is restated, the registry must retain the
-original text, the restatement, and the reason, so the evolution stays auditable.
-
-### D-17 — a pre-registered criterion passed a green suite without being satisfied
-
-`rev-974` returned **CHANGES REQUESTED** on PR #1027 with one blocking finding, and it is the sharpest
-instance of the session's theme because it occurred **inside our own verification machinery**.
-
-**AC2** was pre-registered before any code was written, and explicitly required that **symlinked
-generated state be rejected**. The implementation does not do it:
-
-```sh
-ln -s /etc/hosts apps/web/.next/reviewer-symlink
-pnpm preflight       # → "checkout preflight passed", exit 0
-                     # → required: generated-state exit 43
-```
-
-The acceptance suite was **21/21 green** throughout. Confirmed independently rather than relayed:
-`scripts/preflight.mjs:82-92` rejects symlinks on the **source** path; `:28` merely _skips_ symlinked
-directories rather than rejecting them; and the **generated-state** path at `:141-163` `lstat`s and
-checks `uid` (ownership) but **never** calls `isSymbolicLink()`. The suite's only symlink cases
-(`preflight.test.mjs:59`, `:115`) cover the turbo binary and a _source_ file. No generated-state case
-exists anywhere.
-
-**So: criterion pre-registered, suite green, requirement unmet.** Nobody was careless — the coverage gap
-is _invisible from a green_, which is the entire problem.
-
-**This sharpens D-8 rather than repeating it.** D-8 established that pre-registration does not confer
-_correctness_ (a check can be wrong when written). D-17 establishes the adjacent failure:
-**pre-registration does not confer _coverage_** — a suite can be green, and every registered criterion
-can appear satisfied, while a criterion's actual requirement is untested. The two together mean a
-registry of checks needs **two** properties, not one: each check must be _right_, and the set must
-_actually exercise_ what it claims.
-
-**Requirement on RM-02 (third clause).** The registry must bind each acceptance criterion to the
-**specific case that exercises it**, and prove that case red before trusting its green. A criterion with
-no case that can fail for _that criterion's stated reason_ is unregistered in substance however it
-appears in the manifest. This is mutation testing pointed at the **criterion-to-case mapping**, not
-merely at the gate.
-
-**Credit where due:** the reviewer also declined to re-run AC8, stating plainly that the PR carried it
-forward with no runnable command rather than silently substituting a different boundary test. That is
-the D-8 clause working a second time, in the same review that produced D-17.
-
-### D-16 — the local test gate and the CI test gate disagree by environment
-
-Mos flagged a shape worth chasing: if `pnpm test` exits non-zero on a _pre-existing_ guard, then either
-`main` is red and merges step around it (the #868 shape again), or CI does not run that path. **Both
-branches turned out wrong, and the truth is a third thing.** Established by running it, not by asking:
-
-CI runs **exactly** `pnpm test` (`.woodpecker/ci.yml`, `test` step) — the same command. So the path _is_
-exercised. Yet:
-
-| environment               | result                                                                                                                                                                  |
-| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| CI container              | `test` step **green** (#2158, #2167)                                                                                                                                    |
-| this host, clean worktree | **exit 97** — `WAKE-ASSERT INIT ABORT: BASH_LINENO convention violated on bash 5.2.15(1)-release … expected [3 4], probe reported [3 5] (#973)`, after `PASS=18 FAIL=0` |
-| this host, main checkout  | **exit 1** — a _different_, second defect (below)                                                                                                                       |
-
-The guard is **environment-dependent**: it aborts on this host's bash and not in CI's container. `git
-diff origin/main...` confirms PR #1027 touches **zero** files under `packages/mosaic`, so the guard is
-genuinely pre-existing and unrelated — **f10-coder's report was accurate in every particular**, and
-`main` is equally affected on this host.
-
-**So it is not "merges step around a red" — it is worse in one specific way: the local gate and the CI
-gate do not agree about what passing means.** No agent on this host can obtain a green `pnpm test` at
-all, on any branch, including `main`. A gate an operator cannot run is a gate that only CI enforces,
-and a gate only CI enforces cannot be a pre-push gate. This is the hermeticity/portability class
-already live as #1007 (PR #1024).
-
-**Second, independent defect found while establishing the above.** In the main checkout the same
-package fails differently — exit 1 — because a test **scans the working tree** and asserts on files it
-finds, picking up `apps/coordinator/venv/**` (third-party `site-packages`: `pi = math.pi` in `rich`,
-`setuptools`, `mypy`). **A test whose result depends on untracked files present in the tree is not
-hermetic.** This is the _same_ contamination source that made `pnpm format:check` unpassable (D-1/D-7
-hygiene) — one untracked foreign tree silently breaking two independent gates.
-
-**Requirements.** RM-01/RM-04: a gate must produce the same verdict on a developer host and in CI, or
-declare loudly that it cannot run here — never diverge silently. RM-02 registers both as cases: the
-environment-divergence guard, and a hermeticity control asserting a suite's verdict is unchanged by the
-presence of untracked directories. Coordinate with #1007/#1024 rather than opening a third lane.
-
-**Ownership (Mos, 2026-07-31).** The hermeticity fix **is** PR #1024, which sits in **Jason's parked
-delivery stack** — so, like #1023, its disposition is Jason's. Marked `SUPERSEDED-PENDING-JASON`
-alongside #1023. D-16 strengthens the urgency but does not transfer ownership: **we do not open a third
-lane on a parked PR.** The one-line escalation for Jason: _two independent gates
-(`format:check`, `pnpm test`) were broken by a single untracked directory, and a third
-(`pnpm test`) disagrees between host and CI — non-hermetic gates make every green host-dependent._
-
-**Sharpened statement of the class (Mos).** A pre-push gate an operator _cannot run locally_ is a gate
-only CI enforces — so pointing `.husky/pre-push` at it **misrepresents where the gate lives**. Combined
-with the shared root cause across two gates, the finding is: **non-hermetic gates make every green
-host-dependent.** A gate that only appears to pass depending on which host runs it is this mission's
-exact subject, one meta-level up.
-
-**#1027 disposition (Mos):** proceeds on **CI-green**. CI is the authoritative gate; the local exit-97
-is a known host-specific guard abort, irrelevant to the merge decision.
-
-### D-15 — token scope is not repository permission (a THIRD capability layer)
-
-`f10-coder` was provisioned with `gitea-mosaicstack-f10-coder.token`, scopes `write:repository` +
-`write:issue`, and the mint was verified by "repo access returns 200". It then failed to push:
-
-```
-remote: error: User permission denied for writing.
-remote: error: pre-receive hook declined
-```
-
-Verified objectively rather than inferred (per the charter principle):
-
-| probe                                                  | result                                      |
-| ------------------------------------------------------ | ------------------------------------------- |
-| `GET /repos/mosaicstack/stack/collaborators/f10-coder` | **404** — not a collaborator                |
-| repo permissions as seen by **its own token**          | `admin: false`, `push: false`, `pull: true` |
-
-**Capability has at least three independent layers, and satisfying two proves nothing about the third:**
-
-1. **Token file exists** → raw-API authentication works (D-11b).
-2. **`tea` login exists** → tea-dependent wrapper paths work (D-13).
-3. **Repository permission granted** (collaborator/team membership) → _writes_ are actually authorised.
-
-A token can carry `write:repository` scope and still be refused, because **scope bounds what a token
-may attempt; repository permission decides what the user may do.** They are different systems.
-
-**This is the charter principle failing on the very check meant to confirm capability.** The mint was
-validated by an HTTP 200 on a _read_. A 200 proves reachability; it does not prove the property that
-was required, which was **write**. Both the provisioner and I accepted it — the same
-`written-unverified` treated as `verified` as D-12, one layer up, on a check whose entire purpose was
-verification.
-
-**Requirements.** RM-50's pre-dispatch capability check must probe the **effective permission for the
-operation intended** — for push authority, assert `permissions.push == true` as that seat, not token
-existence and not a 200 on a read. RM-04's registry reconciliation covers all three layers, with a
-must-fail control for each. A capability check that cannot fail on a seat lacking write permission is
-itself an inert gate.
-
-### D-14 — a ruled decision did not propagate to the authoritative record
-
-DECISION-1 (the corrected choke-point wire-in target) was ruled by the coordinator and applied to
-`TASKS.md`. **`MISSION.md` — the charter, the document a cold-starting seat reads first — kept the
-superseded target for hours.** It was flagged `CONTESTED` in a board note, then the ruling landed and
-nobody edited the charter. A seat resuming from the charter would have read the _rejected_ target as
-authoritative and wired the choke point into a disabled rail — the precise failure the ruling existed
-to prevent.
-
-Caught by hand, during an unrelated edit. Nothing would have caught it otherwise.
-
-**This is P-MISSION-001 turned on ourselves.** The mission's own thesis is that convention exists and
-_enforcement_ is the gap: a decision that lives in a chat ruling and a board note, but not in the
-source of truth, has not actually been made — it has been _agreed_. The two are different, and the
-difference is exactly what this mission is about.
-
-> ⚠ **AMENDED by D-20 — propagation is BIDIRECTIONAL.** As first written, this requirement was read by
-> both the orchestrator and the coordinator as _forward_ propagation only: a ruling reaches the
-> documents that state the new rule. **D-20 proved that insufficient.** When D-19 superseded part of
-> D-18, the consequence propagated forward into the charter and the delivery conditions but **never
-> backward into D-18 itself**, which went on asserting a withdrawn claim — and a reviewer disproved it
-> by experiment. **A supersession must update BOTH the documents that render the new rule AND the
-> finding it retires, with the retired wording quoted rather than deleted.** Backward propagation is
-> the same defect as forward; neither of us audited that direction until it bit.
-
-**Requirement (not merely a fix).** A ruled decision must propagate **mechanically** to the
-authoritative record; it must not depend on someone remembering to edit a second file. Concretely, once
-mission state is DB-backed (RM-53 / the P-MISSION cutover):
-
-- a decision is a **record**, not prose duplicated across documents;
-- documents _render_ decisions rather than restating them, so there is one place to be wrong;
-- and where duplication is unavoidable, a check asserts the authoritative record and the derived
-  document agree — with a must-fail control proving divergence is detected.
-
-Until then, the interim rule: **the same commit that records a ruling updates every document that
-states it — and every finding it supersedes.** Interim rules are exactly what the DB cutover exists to replace.
-
-**The rule found a second instance within minutes of being written.** Auditing the charter against all
-rulings to date (rather than waiting to be bitten again) surfaced that **DECISION-2 had also not
-propagated**: `MISSION.md`'s standing directives still stated the DB hard-cutover with no mention of
-Mos's binding qualification that _the spine must not be a single-point hard-stop_ (degraded mode +
-rollback artifact required). A seat reading the charter would have designed toward an availability
-posture the coordinator had explicitly rejected — and would have found the superseded
-"no DB ⇒ the fleet stops" recommendation nowhere contradicted. Now corrected in place.
-
-**Two un-propagated rulings out of two rulings that touched charter text.** The propagation gap is not
-an oversight that happened once; without a mechanism it is the _default outcome_. That is the argument
-for making this a requirement rather than a discipline.
-
-### D-13 — two credential registries that can disagree (why the `--draft` fallback fired at all)
-
-Diagnosing D-12's root cause surfaced a distinct defect. There are **two parallel credential
-registries**, and capability in one does not imply capability in the other:
-
-| registry                                               | contents for identity `mos-dt-0` on `mosaicstack`                                            |
-| ------------------------------------------------------ | -------------------------------------------------------------------------------------------- |
-| token files — `~/.config/mosaic/secrets/gitea-tokens/` | `gitea-mosaicstack-mos-dt-0.token` **EXISTS**                                                |
-| `tea login list`                                       | **NO** `mosaicstack` login for `mos-dt-0` (only `mosaicstack-mos` and `mosaicstack-rev-974`) |
-
-So `get_gitea_token` succeeds and every raw-API path works, while every **tea-dependent** wrapper path
-fails its login validation and silently degrades to the API fallback — which is exactly what dropped
-`--draft`. **tea is not "stale"; the login simply does not exist for that identity.**
-
-This matters beyond one flag: capability was declared authoritative by the token-file set (D-11b), but
-that registry does not govern the tea path. A seat can be _fully provisioned_ by the authoritative
-registry and still lose functionality with no error — only a warning, and only on the degraded path.
-
-**Requirements.** RM-04 (activation coherence): the two registries must be reconciled — one source of
-truth, or a startup check asserting they agree, with a must-fail control proving disagreement is
-detected. RM-50: the pre-dispatch capability check must verify capability for the **path actually
-used**, not merely token-file presence.
-
-**Confirmed working despite the gap** (so this is degradation, not outage): pushes, `pr-merge.sh`,
-PR/issue creation via API fallback, comment posting, and all reads. Impact is confined to
-tea-only features — `--draft`, `--labels`, `--milestone`.
-
-**Reconciliation run by Mos (the manual form of RM-04's assert-agreement, done once by hand).** For
-`git.mosaicstack.dev`, the token-file registry holds **six** seats; `tea` holds logins for **two**:
-
-| state                                            | seats                                                    |
-| ------------------------------------------------ | -------------------------------------------------------- |
-| token file present, **no** mosaicstack tea login | `f10-coder`, `jarvis`, `mos-admin`, `mos-dt-0`, `pepper` |
-| token file present **and** tea login present     | `rev-974` (only)                                         |
-
-**Five of six provisioned seats are silently degraded on tea-only features.** This is _systemic_, not
-a one-off — which is why the fix is registry reconciliation (RM-04) and not a per-seat mint. Minting
-one seat would clear a symptom and leave the class live.
-
-Mos deliberately deferred the mint: it is not on RM-01's critical path, and additively editing shared
-`tea` config underneath running work is a change he declined to make without cause. Full remediation —
-mint the five missing logins **and** wire the startup must-fail assertion that _detects_ disagreement —
-lands as RM-04 at a non-critical seam, or immediately if any seat needs a tea-only feature to progress.
-
-**Correction of record:** this supersedes D-11(b)'s claim that the token-file set is _the_ authoritative
-capability registry. It is **necessary but not sufficient**. Capability is **per-path**: the token file
-governs the raw-API path, the tea login governs the tea path, and the two can disagree silently.
-
-### D-12 — a requested SAFETY flag was silently degraded, and I did not check
-
-I created PR #1027 with `pr-create.sh ... -d` (draft) because it carries **partial, unproven work**.
-`tea` authentication was stale, so the wrapper fell back to its raw-API path — which cannot set draft —
-and emitted:
-
-```
-Warning: API fallback applies title/body/head/base only; labels/milestone/draft require authenticated tea setup.
-```
-
-The PR was created **not-draft**. I read the success output, saw the PR number, and moved on. I then
-reported to the coordinator that the PR was "opened as draft". **It was open, mergeable, and marked
-ready for ~25 minutes**, protected only by the words "DRAFT" and "do not merge" in its title and body —
-i.e. by prose a human might read, not by the platform control I asked for. Detected only because a
-watcher polled `draft:` and the value disagreed with my belief. Corrected by setting the `WIP:` title
-prefix (Gitea's draft mechanism); `draft: True` verified after.
-
-**Three distinct failures, and the third is mine:**
-
-1. **Silent degradation of a safety flag.** The fallback path dropped `--draft` and still exited 0. A
-   fallback that cannot honour a _safety_ argument must fail, not proceed — degrading `--labels` is a
-   nuisance; degrading `--draft` publishes unproven work as ready to merge.
-2. **The warning went to stderr and nothing consumed it.** It was correct, specific, and ignored — a
-   warning nobody acts on is indistinguishable from no warning.
-3. **I did not verify the flag took effect.** I checked that the PR existed, not that it had the
-   property I required. This is the mission's own thesis turned on me: **I trusted a success exit code
-   over an observed state**, on exactly the class of tool this mission exists to distrust.
-
-**Requirements.** RM-02: a wrapper that cannot honour a safety-relevant argument must exit non-zero —
-registered with a must-fail control asserting `--draft` on a degraded path fails rather than proceeds.
-RM-24 (tri-state write outcomes): this is precisely `written-unverified` being treated as `verified` —
-the PR write succeeded, the _requested property_ was never confirmed, and no one looked.
-
-### D-11 — seat identity did not survive into git, and seat capability is invisible at dispatch
-
-Two defects, one dispatch (RM-01 → `f10-coder`):
-
-**(a) Identity drift — P-WRAPPER-001, reproduced on our own delivery.** The seat's commits are
-authored `mosaic-coder <[email protected]>` — the generic fallback. **You cannot tell from
-git history which seat did this work.** Recorded, not rewritten: the drift is the evidence.
-
-> **Mechanism, corrected (Mos).** My original framing here was wrong, and the error was in the brief
-> before it was in the finding. `MOSAIC_GIT_IDENTITY` resolves the **token** (which per-slot credential
-> the wrappers act with). The **commit author** comes from `git config user.name` / `user.email`, which
-> is a **separate setting** — it fell back to the generic value because nothing set it. Exporting the
-> identity could never have fixed authorship. **My worker brief instructed only the export, so the
-> seat did exactly what it was told and the commits were still mis-attributed.**
->
-> **The requirement is coherence: token and authorship must agree.** A seat acting with
-> `gitea-mosaicstack-f10-coder` must also commit as `f10-coder <[email protected]>`.
-> Either half alone is identity drift — one produces the right credential with the wrong author, the
-> other the reverse. That coherence _is_ P-WRAPPER-001, and it belongs in seat setup, not in prose
-> instructions a seat may follow correctly and still end up wrong.
-
-**(b) Capability opacity.** Nothing at dispatch time revealed that `f10-coder` had no credential for
-the target provider. Per-slot tokens live at `~/.config/mosaic/secrets/gitea-tokens/`; the seat holds
-`gitea-usc-f10-coder` but not `gitea-mosaicstack-f10-coder`. This surfaced only when the seat failed
-**mid-task, after ~$9 and 69% of its context.** The orchestrator (me) selected a seat without any way
-to check it could act on the target repo — and there was no way to check.
-
-`get_gitea_token` behaved **correctly**: it refused to fall through and borrow another slot's token,
-failing loud precisely to protect gate-16 attribution. The tooling was right; the _dispatch-time
-information_ did not exist.
-
-**This is P-RECOVERY-001's "honest capability labeling" applied to seats rather than services.** A seat
-should declare what it can actually do — which providers, which repos, which credentials — and that
-declaration must be **checkable before dispatch**, not discovered by failure after the budget is spent.
-
-**Requirements.**
-
-- **RM-04 (activation coherence)** gains the identity-binding half: seat setup must set **both** the
-  token identity **and** `git config user.name`/`user.email`, coherently. Verified by an
-  exit-asserting test that makes a commit and asserts its author — never assumed from an instruction
-  in a brief.
-- **RM-50 (roster ownership)** gains per-seat capability declaration plus a **pre-dispatch capability
-  check**. Mos (who owns provisioning) confirms the check is mechanically trivial: **capability is
-  token-file existence.** Before dispatching seat `X` to provider `Y`, test that
-  `~/.config/mosaic/secrets/gitea-tokens/gitea-<Y>-<X>.token` exists; if absent, provision it or pick a
-  provisioned seat. **The token-file set is the authoritative capability registry.** A one-second check
-  would have replaced a mid-task failure that cost ~$9 and 69% of a seat's context.
-
-### D-10 — the queue guard's failure modes are exactly backwards
-
-`ci-queue-wait.sh` — a **required** pre-push/pre-merge gate — was observed this session doing both of
-these:
-
-- **Fails OPEN on an unknown result.** `state=unknown ⇒ exit 0`, five times, during real pushes and
-  real merges. It also evaluates `branch=main` rather than the branch being acted on.
-- **Fails CLOSED on credential resolution.** In a worker seat it aborted with
-  `Gitea token not found`, hard-blocking a legitimate push of completed, tested work. The worker
-  correctly stopped (Constitution gate 8). The identical command run from that worker's _own worktree_
-  in another shell succeeded, so the checkout and remote were fine — the difference was the worker's
-  process environment.
-
-**A gate that waves through work it never checked, and blocks work that is ready, has its failure
-modes inverted.** Availability failures (cannot reach the provider, cannot resolve a credential)
-should degrade to a loud, auditable _inability to assert_ — never to a hard stop on delivery, and
-never to a silent pass. Correctness failures (unknown, malformed, terminal-failure) are what must
-block.
-
-This is also the **Pi-brick shape** (P-RECOVERY-001): a gate whose own unavailability prevents the
-work needed to recover from it.
-
-**Requirement on RM-03, extending its existing two defects:** the guard must distinguish
-`CANNOT_ASSERT` (credential/transport/provider unavailable — loud, audited, does not silently pass and
-does not permanently block) from `ASSERTED_NOT_READY` (a real non-green CI state — blocks). Both are
-registered R-002 cases with must-fail controls; neither may exit 0 silently.
-
-### D-9 — the comms path shell-interprets message bodies (injection-shaped, found by accident)
-
-Sending a status message with `agent-send.sh -m "...`backticks`..."` caused bash to **execute** the
-backticked text as command substitution. The recipient received a mangled body plus a
-`No such file or directory` error; the intended sentence never arrived. The message was reported as
-delivered.
-
-This is the **same class** as the already-noted `pr-create.sh` backtick-quoting bug (M2 scratchpad):
-**two tools in the comms path treat a message body as shell input.** A body that can execute on the
-sender is a _correctness_ bug before it is ever a security one — and note the failure mode: the
-send reported success while silently transmitting something other than what was written. Silent
-corruption with a success receipt is precisely the pattern this mission exists to eliminate.
-
-**Requirement on RM-40 / RM-42 (comms/v1), hardened by Mos.** The envelope must carry its payload
-**verbatim** and must not be subject to shell interpretation at **any** hop — sender, transport, or
-adapter. Concretely: **file/stdin transport, never argv interpolation.**
-
-**Standing interim rule, effective now (Mos).** Until the envelope lands, use `agent-send.sh -f
-<file>` for any message body containing special characters — **never `-m`**. Passing a file sidesteps
-argv interpolation entirely. **This rule is mandatory in every worker brief this mission issues**,
-alongside the D-8 "if a check is unrunnable, say so" clause. Round-trip fidelity (send a body containing backticks, `$(…)`, quotes, and newlines; assert
-byte-identical receipt) is a required registered test case under RM-02, including a must-fail control
-proving the assertion can detect corruption.
-
 ### D-8 — a PRE-REGISTERED acceptance check that was not runnable as written
 
 On PR #1025 the author (me) pre-registered AC2 with the fixture snippet `mkdir -p apps/*/venv/lib`.
@@ -811,18 +297,17 @@ spread is itself information, and X1 says we calibrate on real merged PRs.
 
 ### P5 — Retirements, hygiene, conformance
 
-| id    | task                                                                                                                                                                                           | src                    | depends_on                 | est (S/O)        | tier   |
-| ----- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------- | -------------------------- | ---------------- | ------ |
-| RM-50 | One roster-owned socket/host; quarantine unmanaged; **deterministic reaper for stale sessions AND dead-session disk scratch** (D-7)                                                            | O+S+live               | RM-04                      | 14K / 150K       | sonnet |
-| RM-51 | Auto-sync **allowlist** (never auto-stage unknown paths) + worktree/lease isolation                                                                                                            | O+S                    | RM-02                      | 8K / 110K        | sonnet |
-| RM-52 | Retire the Python controller + duplicate MACP islands (3 → 1)                                                                                                                                  | O+S                    | RM-26, RM-27, RM-25, RM-28 | 14K / 110K       | codex  |
-| RM-53 | Flat-file orchestration → DB hard cutover, with rehearsed rollback artifact                                                                                                                    | O+S                    | RM-27, RM-30, RM-34, RM-29 | (in S-10) / 200K | opus   |
-| RM-54 | Fleet-wide inert-gate audit against the RM-02 registry                                                                                                                                         | O                      | RM-02                      | — / 120K         | sonnet |
-| RM-55 | **Conformance harness:** fault-inject the live failure classes on real artifacts                                                                                                               | O+S                    | RM-35, RM-41, RM-53        | 18K / 260K       | opus   |
-| RM-56 | Retirement proof: CI asserts all three retirements are complete **and stay complete**                                                                                                          | O                      | RM-52, RM-45, RM-53        | — / 90K          | codex  |
-| RM-57 | Operator cutover docs + activation proof; map all 15 decisions to evidence                                                                                                                     | S                      | RM-04, RM-36, RM-45, RM-55 | 6K / —           | codex  |
-| RM-59 | **Close the D-19 residual risk** — generated-state verification anchored **outside** the worktree's authority (executor/spine-side attestation), retiring the same-UID self-authentication gap | mos-remediation (D-19) | RM-12, RM-21, RM-25        | 20K              | opus   |
-| RM-58 | **Mechanical pre-dispatch context reset** — the orchestrator resets a seat out-of-band and verifies it, rather than asking the agent to reset itself                                           | mos-remediation (D-4)  | RM-31, RM-50               | 8K               | sonnet |
+| id    | task                                                                                                                                                 | src                   | depends_on                 | est (S/O)        | tier   |
+| ----- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | -------------------------- | ---------------- | ------ |
+| RM-50 | One roster-owned socket/host; quarantine unmanaged; **deterministic reaper for stale sessions AND dead-session disk scratch** (D-7)                  | O+S+live              | RM-04                      | 14K / 150K       | sonnet |
+| RM-51 | Auto-sync **allowlist** (never auto-stage unknown paths) + worktree/lease isolation                                                                  | O+S                   | RM-02                      | 8K / 110K        | sonnet |
+| RM-52 | Retire the Python controller + duplicate MACP islands (3 → 1)                                                                                        | O+S                   | RM-26, RM-27, RM-25, RM-28 | 14K / 110K       | codex  |
+| RM-53 | Flat-file orchestration → DB hard cutover, with rehearsed rollback artifact                                                                          | O+S                   | RM-27, RM-30, RM-34, RM-29 | (in S-10) / 200K | opus   |
+| RM-54 | Fleet-wide inert-gate audit against the RM-02 registry                                                                                               | O                     | RM-02                      | — / 120K         | sonnet |
+| RM-55 | **Conformance harness:** fault-inject the live failure classes on real artifacts                                                                     | O+S                   | RM-35, RM-41, RM-53        | 18K / 260K       | opus   |
+| RM-56 | Retirement proof: CI asserts all three retirements are complete **and stay complete**                                                                | O                     | RM-52, RM-45, RM-53        | — / 90K          | codex  |
+| RM-57 | Operator cutover docs + activation proof; map all 15 decisions to evidence                                                                           | S                     | RM-04, RM-36, RM-45, RM-55 | 6K / —           | codex  |
+| RM-58 | **Mechanical pre-dispatch context reset** — the orchestrator resets a seat out-of-band and verifies it, rather than asking the agent to reset itself | mos-remediation (D-4) | RM-31, RM-50               | 8K               | sonnet |
 
 **Critical path:** `RM-01 → RM-02 → RM-10 → RM-11 → RM-12 → RM-21 → RM-23 → RM-31 → RM-33 → RM-34 → RM-53 → RM-55`.
 

docs/scratchpads/1000-rm-61-ci-contract-exemption.md

@@ -1,118 +0,0 @@
-# RM-61 — CI contract exemption for #1000 teardown artifact
-
-**Tracking:** RM-61 / issue #1000
-
-**Branch:** `fix/rm-61-ci-contract-exemption`
-**Owner:** `coder-mos1`
-
-## Objective
-
-Determine, by red-first provider controls, whether the `ci-postgres` pod-not-found teardown signature discriminates from a real PostgreSQL failure. Only if it discriminates may a named, bounded CI-contract exemption be implemented. The exemption must retire when #1000 is fixed; fixing #1000 is the closure path.
-
-## Pre-registered kill criterion
-
-If an injected real `ci-postgres` failure also yields `pods "wp-svc-<ULID>-ci-postgres" not found` as the service's provider-visible failure, the signature does not discriminate. Option B is unsafe; stop exemption implementation and fall to Option A (#1000).
-
-## Plan
-
-1. Capture full `-f json` records for the 11 supplied observations and state counts.
-2. Run one startup-failure control using the real pgvector/PostgreSQL image with an invalid `initdb` argument.
-3. Run one post-readiness crash control using real PostgreSQL, `pg_isready`, and a deliberate postmaster kill while a DB-dependent probe is active.
-4. Compare the raw `ci-postgres` service record independently of failures in dependent steps.
-5. Investigate runner/time/head clustering only as a hypothesis; never encode incidental correlates or retries into policy.
-6. If and only if the controls discriminate, implement and test the exact exemption, document its two-way boundary, and track retirement at #1000.
-
-## Budget
-
-No explicit token cap supplied. Working estimate: 20K–30K tokens. Limit provider controls to the two pre-registered runs; no retries or re-roll policy.
-
-## Initial evidence
-
-Historical JSON saved locally under `.evidence/rm-61/` (not for commit). Supplied pipelines: 11 total. Child-step counts: five pipelines with 9 children and six with 10 children. Seven contain the `ci-postgres` pod-not-found failure (#2170, #2175, #2180, #2181, #2182, #2187, #2188); four do not (#2158, #2167, #2184, #2186). Every observed workflow reports `agent_id=44`, so the available JSON does not separate clean and artifact runs by runner. This refutes runner identity as a discriminator in the sampled record.
-
-## Progress
-
-- [x] Requirements and kill criterion recorded before control implementation.
-- [x] Historical full-JSON records captured.
-- [x] Startup-failure control observed terminal.
-- [x] Post-readiness crash control observed terminal.
-- [x] Discrimination verdict recorded: Option B may proceed.
-- [x] Conditional exemption implementation.
-
-## Tests / evidence
-
-### Control 1 — real startup failure
-
-- Commit: `3931b0e29eb834914f7b17e4db7e221481d436fa`
-- Pipeline: #2189, exact commit match.
-- Full JSON child scan: 9 total — 7 success, 2 failure, 0 skipped/pending/running.
-- `ci-postgres`: `state=failure`, `exit_code=1`, `error=null`, with a five-second execution window.
-- `test`: `state=failure`, `exit_code=1` after the readiness budget expired.
-- Pipeline/workflow: terminal `failure`.
-
-This control is red and its service record differs from #1000 (`exit_code=0` plus pod-not-found). It proves the startup-failure direction only. It does not settle the dangerous post-readiness crash/garbage-collection path.
-
-### Control 2 — real post-readiness crash
-
-- Commit: `25ac59715a94dd1b52ef42577472eb44ecc4b446`
-- Pipeline: #2191, exact commit match.
-- Full JSON child scan: 9 total — 7 success, 2 failure, 0 skipped/pending/running.
-- Service log proves PostgreSQL reached `database system is ready to accept connections`, the test created the arm table, and the service then killed postmaster PID 7.
-- Test log proves a successful `SELECT 1` followed by `Connection refused`; it exited the pre-registered control code 61.
-- `ci-postgres`: `state=failure`, `exit_code=137`, `error=null`, with a 203-second execution window.
-- `test`: `state=failure`, `exit_code=61`.
-- Pipeline/workflow: terminal `failure`.
-
-This is the dangerous post-readiness crash path. Its service record is not pod-not-found and therefore differs from #1000 independently of the dependent test failure.
-
-### Discrimination verdict
-
-Both real failures are provider-visible as process exits (`exit_code=1` startup; `exit_code=137` crash) with no pod-not-found error. The seven observed #1000 artifacts are provider reconciliation misses (`exit_code=0` plus the exact pod-not-found error). The declared kill criterion did not fire, so Option B may proceed with a matcher requiring the full conjunction. This evidence does **not** prove every future Kubernetes failure is distinguishable; it proves these two concrete real-failure classes remain blocking and bounds the exemption to the observed reconciliation shape.
-
-### Unit red-first checkpoint
-
-The nine-case contract harness was written before the verifier. First execution exited 1 because `verify-terminal-green.py` did not exist; no exemption implementation was live. Cases pre-register ordinary green, the exact artifact, both provider controls, near-miss signatures, an independent failure, and a skipped step.
-
-### Control 2 setup attempt — invalid, excluded from evidence
-
-- Commit: `9455cd6a2650b2b7e70f746c07933d96e5cb3d20`
-- Pipeline: #2190, exact commit match.
-- Full JSON child scan: 9 total — 7 success, 2 failure, 0 skipped/pending/running.
-- Service log: `/bin/sh: 0: -c requires an argument`.
-- Root cause: Woodpecker service `commands` did not become the third `sh -c` argument. PostgreSQL never started, so this run is **not** the post-readiness crash control and provides no discrimination evidence.
-- Focused remediation: place the script directly in the third `entrypoint` element and supply `PGPASSWORD` for the marker query. This is a control-fixture correction, not a retry of #1000 and not evidence for either verdict.
-
-## Implementation evidence
-
-- `verify-terminal-green.py` consumes only the full JSON/API record; it performs no fetch, retry, or trigger.
-- Exact #2188 record: exit 0, 10 children, 9 success + 1 named exemption.
-- Historical set: #2158/#2167/#2184/#2186 pass with no exemption; #2170/#2175/#2182/#2187/#2188 pass with one named exemption; #2180/#2181 remain red because independent failures exist.
-- Provider controls: #2189 and #2191 both exit 1 under the verifier; neither is exempted.
-- Unit harness: initial 9/9 cases passed after the red-first checkpoint; review remediation expands this to 12 cases with expected-head match/missing/mismatch coverage.
-- Test-membership guard: PASS, population 45; 26 enumerated, 19 signed exclusions; all 39 surface paths present.
-- Python compile: PASS.
-- `pnpm typecheck`: PASS, 45/45 tasks.
-- `pnpm lint`: PASS, 25/25 tasks.
-- `pnpm format:check`: PASS after moving local evidence outside the repository tree.
-- `test:framework-shell`: RM-61 and all preceding suites passed, then the pre-existing wake assertion aborted with exit 97 because this host's Bash 5.2.15 reports `BASH_LINENO [3 5]` where that suite requires `[3 4]`. RM-61 does not modify the wake suite; the command is not fully runnable on this host as written and no substitute result is claimed.
-
-## Independent review
-
-- Review 67 / comment 20403 at exact head `e7b29219e11efd0a19395156ac0b154bec0c3a73`: **REQUEST CHANGES**.
-- Blocker: the verifier echoed the pipeline commit but did not bind it to the current PR head; mutating only #2188's commit still returned terminal-green.
-- Remediation: require `--expect-commit <full-40>`, add a pipeline anomaly on missing/mismatched record commits, emit expected and observed values, wire both CI documentation and the merge-gate baseline to pass provider PR head, and add match/missing/mismatch tests.
-- This binding is not prohibited head-based clustering policy: it proves the evidence belongs to the commit under verdict. Runner/node/time/head correlation remains excluded from the teardown signature itself.
-- Review 69 later approved the commit-binding remediation at exact head `033b2ffb46674b2c0bcc5197273c109b461f62d9`; pipeline #2193 was 9/9 success. Before merge-gate, an independent adjudicator found that Python treats JSON `false == 0`, allowing a non-integer exit value to match. The prior gate-ready state was withdrawn. The type-strict set distinguishes genuine red-first controls (`false`, `0.0`, which wrongly exempted) from regression guards (`true`, `"0"`, `null`, which already blocked). Remediation requires the decoded type to be exactly `int` and excludes `bool` explicitly.
-
-## Documentation checklist
-
-- [x] CI contract documented in the canonical framework CI/CD guide.
-- [x] Operator command documented in the Woodpecker tool README.
-- [x] Merge-gate baseline points to the deterministic verifier and named retirement.
-- [x] Tracking and retirement cite issue #1000.
-- [x] Both positive and negative guarantee boundaries are stated.
-- [x] No API/auth/schema/user-facing navigation change; OpenAPI, user guide, and sitemap are not applicable.
-
-## Risks
-
-The controls establish discrimination for deterministic startup failure and an armed post-readiness postmaster crash on the current Woodpecker Kubernetes provider. They cannot prove that every future Kubernetes failure mode will preserve a non-zero exit before reconciliation. The exact matcher minimizes that residual risk, and issue #1000 remains the mandatory provider-seam closure and retirement trigger.

docs/scratchpads/1029-rm-02-gate-registry.md

@@ -1,107 +0,0 @@
-# RM-02 Gate Registry Scratchpad (#1029)
-
-## Objective
-
-Deliver the seven-gate registry and RED-first anti-inert verifier on `feat/rm-02-gate-registry`, preserving required-versus-actual defects without laundering them as success.
-
-## Constraints and boundaries
-
-- Do not modify `ci-queue-wait.sh`; RM-03 owns that fix.
-- Do not modify `docs/remediation/TASKS.md`; workers cannot edit orchestrator tracking.
-- Every declared behavior must be observed, not inferred from an exit code.
-- Repository-local evidence does not establish same-authority tamper resistance; RM-25/RM-59 own the external trust anchor.
-- Coverage is seven logical gates; broader inventory is RM-54.
-- Budget assumption: no explicit token ceiling was supplied. Keep implementation dependency-free (stock Node), avoid repeated full monorepo installs, and keep generated test artifacts under the worktree/main disk.
-
-## Plan
-
-1. Update PRD and tracking references.
-2. Write black-box meta-negative-control first and observe it fail for the missing verifier behavior.
-3. Implement minimal manifest parser/case runner/mutation detector; observe meta-control succeed.
-4. Add schema, coverage, provenance, prose marker, compatibility, discovery, deployment identity, and defect-delta tests RED-first.
-5. Register seven gates with exact cases and run each case.
-6. Add prospective per-commit replay and bounded provider-evidence reporting.
-7. Wire unconditional Woodpecker CI and update developer/admin documentation.
-8. Run situational and baseline verification, independent Codex review, remediate, commit, queue guard, push, PR, coordinator/reviewer handoff.
-
-## Progress
-
-- 2026-08-01: Design approved by `mos-remediation`; rulings A-E and source/deployed identity addition incorporated.
-- 2026-08-01: Isolated worktree created from `origin/main` f65e9ea6; RM-01 f58b3699 verified as ancestor.
-- 2026-08-01: Git author set to `f10-coder <[email protected]>`; provider issue #1029 created with `MOSAIC_GIT_IDENTITY=f10-coder`.
-- 2026-08-01: Source/deployed queue-guard SHA-256 observed equal (`19cda2f...`); this observation is not yet an enforced property.
-
-## Tests and RED-first evidence
-
-- Meta-negative RED first: `node --test scripts/gate-verify.test.mjs` failed because the absent verifier did not name externally inerted `meta-fixture`.
-- Structural RED: nine tests failed before implementation for internal mutation, unregistered executable, missing negative control, ownerless delta, unbound criterion/claim, modeled conflict, missing provenance, and deployment drift.
-- Clause hardening RED: positive-only security criterion and missing registered claim marker both passed incorrectly before validation was added.
-- CI wiring RED: package script and unconditional Woodpecker step tests both failed before wiring.
-- History RED: history test failed with missing module before own-tree manifest selection/provider classification was implemented.
-- `pnpm gate:verify`: exit 0; seven gates each reported `META-NEGATIVE-CONTROL ... observed red`; queue source/deployed drift control observed red; six queue behavior deltas printed as `DEFECT (owner: RM-03)`.
-- Focused Node tests: 54/54 pass after third-round hardening (36 verifier/wiring plus 18 history/provider tests).
-- `pnpm typecheck`: pass (45/45 Turbo tasks).
-- `pnpm lint`: pass (25/25 Turbo tasks).
-- `pnpm format:check`: pass.
-- `pnpm test`: repository suites reached 45/46 Turbo tasks; all application/package tests shown passed, then the known host-specific wake assertion aborted exit 97 (`BASH_LINENO convention violated`, #973/D-16). No test was edited or bypassed. CI remains the authoritative full-suite environment.
-
-## Self-surfaced defect
-
-The queue guard's `get_state_from_status_json` runs `python3 - <<'PY'` while provider JSON is piped to the shell function. The heredoc owns stdin, so Python never reads provider JSON. Terminal success, no-status, terminal failure, and malformed payloads all classify as `unknown`; the associated fail-open outcomes are recorded under RM-03. No queue-guard source was modified.
-
-## Independent review remediation
-
-- Final pre-commit Codex code review found three blockers: a tautological deployment drift control, independently observed rather than combined compatibility cases, and unauthorized edits to orchestrator-owned `TASKS.md`.
-- Deployment identity now uses one shared file comparator for both live equality and a temporary drifted deployed copy; a test makes that comparator inert and proves the meta-control fails.
-- Compatibility scenarios now merge referenced fixtures/environments into one isolated construction and execute an exact scenario invocation; a test proves two independently valid fixtures coexist in the combined run.
-- `TASKS.md` changes were reverted. `docs/remediation/GATE-CLAIMS.md` binds source headings and anchored text without editing orchestrator tracking.
-- Codex security review found the Bubblewrap replay shared the runner PID namespace. Replay now unshares PID, IPC, and UTS namespaces, and an abuse-case test proves a sibling runner PID is invisible.
-- Second review found empty reason diagnostics, final-symlink fixture writes, and lifecycle-script mutation of authoritative history files. Must-fail cases now require a reason pattern; writes use no-follow semantics; and replay snapshots every archived file before install and rejects any changed, deleted, or type/mode-shifted source before executing the verifier. Dedicated negative tests cover all three.
-- Third code review found ambiguous duplicate provider steps and order-sensitive JSON outcome comparison. Provider evidence now requires exactly one `gate-verify` step in the authoritative rerun, and structural equality normalizes object keys. Both regressions have RED-first tests. Third security review reported no findings.
-- Initial PR pipeline #2177 exposed Woodpecker's shallow boundary: the activation parent object was present but marked shallow, so `merge-base --is-ancestor` correctly refused to infer ancestry. The unconditional gate step now unshallows before ancestry/provenance checks; its wiring test was observed RED before the CI fix.
-- Pipeline #2178 then proved the unprivileged Docker runner cannot establish Bubblewrap namespaces. A privileged experiment remained uncommitted and was rejected after Codex correctly rated it CRITICAL: PR-controlled code executes before an in-repository sandbox and could directly use the granted capability.
-- `mos-remediation` and `rev-974` independently ruled Option C. RM02-REQ-10 now retains its original text, restatement, and reason: PR CI verifies only the current tree, unprivileged and fail-closed; isolated own-tree replay is deferred to RM-60/#1031's external pre-execution authority, cross-referenced with RM-59. Future protected post-merge replay is detection with quarantine/revert, never pre-merge prevention.
-- RED-first boundary test proved the old path executed an inert intermediate verifier. The revised path states adjacent `DOES`/`DOES NOT` claims, validates historical manifest provenance without executing it, and infers no replay success. Direct sandbox tests remain hard-fail; unprivileged CI asserts terminal refusal instead of treating replay as success. Pipelines #2179/#2180/#2181 exposed two runner refusal forms: namespace denial as `spawnSync bwrap` with `error.code=EPERM`, and a test image without Bubblewrap as `error.code=ENOENT`. The replay diagnostic now preserves spawn errors. Parent-generated launcher/entry metadata distinguishes refusal before sandbox entry from child-controlled output; the detector recognizes exact `spawnSync bwrap` provenance for `EPERM`/`EACCES`/`ENOENT` and known namespace-refusal text only when the entry command provably did not run. Focused negative assertions reject unrelated `spawnSync git EPERM`, verifier output that merely says `bwrap ENOENT`, and exact namespace-denial impersonation without provenance or after sandbox entry.
-- Exact-head independent review at `38f1b249` found one valid diagnostic-masking blocker: canonical verification knew four stable-ID rebinding failures but a thrown stale fixture replacement reached the outer catch first and emitted only the generic error. RED-first reproduction confirmed the canonical path omitted both responsible criterion IDs. Verification now collects labeled failures independently across claims, discovery, deployment, case execution/outcome checks, mutation, and compatibility, preserving structural stable-ID failures alongside the stale-fixture signal. The canonical regression test requires both missing-binding IDs and the generic fixture error.
-- Exact-head independent review at `9b4d4beb` found two valid blockers. RED-first controls reproduced both: denial-looking child stderr was accepted as sandbox unavailability, and moving meaning/prose criterion IDs to an unrelated type-error case left `gate:verify` green. Bubblewrap execution now emits a parent-generated random entry marker and returns parent-owned launcher/entry metadata; unavailability requires Bubblewrap launcher provenance plus proof entry never ran, so exact denial impersonation from plain or entered-child results is rejected. Criterion objects now declare exact `caseRefs`, checked bidirectionally against case-side `criterionIds`; prose claims declare an exact must-fail `caseRef`. Registered must-fail cases move a criterion binding, remove meaning provenance, and redirect a prose claim, each producing its stable reason. The review freeze was deliberately lifted before remediation.
-- Option C security review reported no findings. Code review rejected an initial unrelated typecheck binding for the new security criterion. It was replaced with a dedicated registered `privileged-pr-gate` case: the fixture injects a privilege key into the gate step, the wiring control rejects it for that exact reason, and `gate:verify` observes the boundary negative control. Follow-up hardening uses a closed exact gate-step construction, rejects privilege across the entire pipeline, rejects non-canonical/merged YAML keys, and pins the unrestricted PR/main trigger block; quoted/escaped/alias/merge/duplicate/filter bypass tests pass. Final Codex code review approved with no findings.
-
-- Exact-head review at `83d2ecb2` found four silent-defeat paths. Genuine RED-first tests on the pre-fix code proved: author-controlled HEAD/parent/introduction seams produced no boundary failure; cross-commit duplicate pipeline number 7 returned terminal-success; and misspelling `outputPattern` as `outputPatern` in required/actual left canonical verification green. Fixes derive the seam from Git, validate provider identity globally before subject filtering, and recursively close/type-check nested schemas. New registry criteria `RM02-EVIDENCE-SUBJECT-BINDING`, `RM02-TYPE-STRICT-SCHEMA`, and `RM02-HISTORY-BOUNDARY` are bidirectionally bound to eight registered must-fail controls. The broad nested-object typo table and exact derived-boundary test are regression guards added after implementation, not claimed as RED-first. Pre-commit Codex review then found that global evidence failure was only observed—not failed—when HEAD was the sole prospective commit, and that non-object collection entries threw before normalization. Both were reproduced RED-first, then fixed by one collection validator used before iteration and by per-commit assessment. Follow-up review found collection validation still omitted exactly-one-gate-step cardinality for unrelated subjects; a focused test reproduced terminal-success RED-first, and collection validation now rejects that ambiguity globally. Security review then found present-but-empty outcome patterns were truthy-optional assertion bypasses; a reason-specific test reproduced that they lacked the required schema diagnostic, and present pattern fields now require non-whitespace content.
-
-- Exact-head review at `32b490a7` found three population-level blockers. Genuine RED-first tests proved a gate change before author-delayed registry introduction fell outside the range, and empty criteria/gates/prose/scenario populations returned zero. History now anchors at the provider target merge-base; delayed introduction is a registered must-fail control. Production verification requires non-empty populations and a hardcoded seven-gate ID/source inventory before quantified checks. D-38/D-40 criteria now quantify over `gateRefs` exactly spanning every registered gate; each gate declares its evidence subject, and population controls mutate evidence subject and comparison type for every gate. The history record states both bootstrap directions: sound against a branch author unable to rewrite main, not sound against compromised/rewritten main, with residual owned by Builds 1-2. Pre-commit review rejected an initial production CLI `--fixture-profile` test relaxation as a vacuity bypass. That flag was removed; synthetic fixtures now use a non-executable test-support runner, while regression tests prove the shipped CLI rejects the flag and production population checks remain mandatory. Follow-up review then proved deleting `gateRefs` skipped population validation; a RED-first loop reproduced all three deletions, and the three general criterion IDs now require the field before exact-span validation.
-
-## Documentation checklist
-
-- PRD, developer guide, admin guide, governing claim index, sitemap, plan, and scratchpad updated.
-- User/API documentation not applicable: no user workflow or API changed.
-- Independent review documentation check pending rev-974 at the revised exact head.
-- Canonical documentation remains in-repository; no external publication requested.
-
-## Rebase onto RM-61
-
-- Rebasing `f9746b23` onto main `f4fd5967` completed mechanically with no conflicts.
-- The first post-rebase `pnpm gate:verify` correctly failed because the old activation seam `f65e9ea6` made the newly merged pre-registry RM-61 commit part of prospective history even though that commit predates the registry. An initial manifest update to `f4fd5967` had the right value but retained an author-controlled mechanism. Independent mutation proved HEAD, HEAD's parent, and the introduction commit could each make history coverage vacuous or partial. The manifest field is now forbidden; the verifier derives the boundary as the parent of the first first-parent registry-introduction commit, and registered must-fail controls reject all three unsafe candidates.
-
-## Risks/blockers
-
-- Current queue guard intentionally has required-versus-actual deltas owned by RM-03.
-- Provider CI cannot report the currently executing pipeline as terminal success; current-commit evidence must be labeled pending and becomes historical current-tree evidence only after provider completion.
-- Isolated per-commit execution requires RM-60/#1031. Until that external authority exists, no replay success is claimed. A future protected post-merge failure requires quarantine/revert.
-- CI containers may not expose the operator-home deployed queue guard. In that layer the verifier checks the pinned observed digest and reports live identity unavailable under RM-04; it does not infer live equality.
-
-## coder-mos2 remediation — fourth round
-
-- Coordinator correction loaded: Blocker 2 requires a genuine shrink-both control against an independent inventory baseline; Blocker 3 requires evidence-side subjects consumed against gate definitions for every gate; anchor-dependent history provenance must be removed rather than relabelled because PR lifecycle code makes all local git state untrustworthy before verification.
-- Boundary to preserve in both directions: this repository layer DOES verify current-tree registered cases, independently anchored inventory shape, evidence subject consumption, and an enforced absence of history-provenance claims. It DOES NOT establish history provenance at all. RM-60 owns the provider-controlled/protected pre-execution boundary required for that property; no local ref, config, URL, constant, or author-positioned path is treated as an anchor.
-- TDD plan: add three genuine red-first controls before implementation: shrink verifier inventory plus manifest together; mutate evidence-side subject for every gate; and reject the currently enabled history verifier/import/report path. Existing controls retained as regression guards and labelled honestly.
-- Identity observation before first commit: `git var GIT_AUTHOR_IDENT` returned `coder-mos2 <[email protected]>` using process-scoped author/committer variables; shared repository config was not modified.
-- Genuine RED-first evidence: `node --test scripts/gate-remediation.test.mjs` produced 0/3 passing on frozen head `fbb61912`: source+manifest shrink exited zero, no evidence-side case subjects existed, and the production verifier still imported/invoked history verification. These were failures for the three stated blocker reasons, not regression guards.
-- Sixth mutation found before review: after the first baseline implementation, shrinking the new baseline and manifest together while leaving the verifier inventory unchanged still exited zero. A new test observed that attack RED first. Inventory equality diagnostics are now bidirectional, and the registered shrink control attacks both source+manifest and baseline+manifest pairs.
-- Regression guards retained and honestly labelled: manifest-only shrink, exact `gateRefs` span, production fixture-profile rejection, and broad nested schema checks already blocked before this round.
-- Current focused evidence before independent review: remediation controls 4/4; verifier/wiring/remediation suite 39/39; canonical `pnpm gate:verify` exits zero while reporting six RM-03-owned `DEFECT` deltas and all seven gate meta-negative controls observed red.
-- Independent Codex code review requested changes on two valid blockers. First, the evidence population control called the subject helper directly rather than traversing production result consumption. It now creates one lightweight executed fixture per required gate, invokes the real `verifyRegistry` path, and fails to observe rejection if the production consumer is removed; a regression mutation proves that coupling. Second, a lexical history blacklist overclaimed structural incapacity. Production output now passes through a closed current-tree observation renderer with no history/ancestry/lineage success class; the exclusion control tests three alternate success wordings plus exact production renderer wiring, and the registered must-fail fixture adds a prohibited class.
-- Codex review test attempts were unrunnable in its read-only sandbox (`EROFS`/`EPERM`); the reviewer disclosed this rather than substituting a passing variant. Local writable-worktree tests remain the runnable evidence.
-- Renderer remediation: every non-error production observation and final summary now routes through the closed current-tree output renderer. The exclusion control additionally requires one stdout sink, exactly two `GATE VERIFY FAILED` stderr sinks, no console sinks, and renderer use for both per-observation and final-summary paths. Regression attacks cover allowlisted history/ancestry/lineage wording, writer assertion removal, direct final-success stdout, and direct success stderr; focused suite 41/41, `pnpm gate:verify` green with six declared RM-03 deltas, and format check green.
-- Coordinator ruling after CWE-353: retain the same-checkout inventory comparison but narrow its claim. Canonical current boundary: “Detects accidental and incompetent inventory drift within a checkout; does NOT survive an adversary who rewrites baseline, manifest, and verifier consistently — that guarantee requires RM-60's external boundary.” This supersedes the earlier “independent/anchored” wording in the historical entries above; those entries remain as append-only evidence, not current claims.
-- Genuine RED-first overclaim control: before claim remediation, `node scripts/gate-inventory-claim-control.mjs` exited 84 and named every artifact missing the narrowed boundary plus each current overclaim. The registered `inventory-claim-overstatement` case now rewrites the baseline purpose to a protection claim and must exit 84 with `INVENTORY_CLAIM_OVERSTATED`. Existing shrink-pair controls remain regression guards for the same-checkout drift property, not adversarial-integrity claims.
-- Follow-up code review found a genuine propagation/control gap: `docs/PRD.md` still said “independent seven-gate baseline,” and the first forbidden regex did not match the intervening qualifier. The reviewer observed the control green against that overclaim. The PRD now says same-checkout, the detector rejects `independent … baseline` across bounded same-line qualifiers, the registered mutation uses the exact qualified wording, and a focused behavioral test requires exit 84 for it. Follow-up security review passed with risk `none` and explicitly accepted the narrowed RM-60 boundary.

gates/required-gates.baseline.json

@@ -1,34 +0,0 @@
-{
-  "schemaVersion": 1,
-  "purpose": "Detects accidental and incompetent inventory drift within a checkout; does NOT survive an adversary who rewrites baseline, manifest, and verifier consistently — that guarantee requires RM-60's external boundary.",
-  "gates": [
-    {
-      "id": "quality-typecheck",
-      "source": "package.json"
-    },
-    {
-      "id": "quality-lint",
-      "source": "package.json"
-    },
-    {
-      "id": "quality-format",
-      "source": "package.json"
-    },
-    {
-      "id": "checkout-preflight",
-      "source": "scripts/preflight.mjs"
-    },
-    {
-      "id": "ci-queue-wait",
-      "source": "packages/mosaic/framework/tools/git/ci-queue-wait.sh"
-    },
-    {
-      "id": "hook-pre-commit",
-      "source": ".husky/pre-commit"
-    },
-    {
-      "id": "hook-pre-push",
-      "source": ".husky/pre-push"
-    }
-  ]
-}

package.json

@@ -6,7 +6,6 @@
     "build": "turbo run build",
     "dev": "turbo run dev",
     "lint": "turbo run lint",
-    "gate:verify": "node scripts/gate-verify.mjs",
     "preflight": "node scripts/preflight.mjs",
     "clean:generated": "node scripts/clean-generated.mjs",
     "typecheck": "pnpm preflight && turbo run typecheck",

packages/mosaic/framework/fleet/roles/merge-gate.md

@@ -13,14 +13,7 @@ It is a **gate** role: the one and only merge path.
 2. **Use the wrapped scripts as the ONLY merge path** — the merge-gate merges
    **exclusively** by calling **`pr-merge.sh`** (the merge action, which carries the
    authoritative forbidden-path guard) and **`pr-ci-wait.sh`** (to wait for green
-   CI before merging). Before issuing a verdict, scan the full JSON/API child-step
-   record (including `clone`) with **`verify-terminal-green.py --expect-commit
-<current-provider-PR-head>`** and record the equal expected/observed full-40
-   commits, exact step count, anomalies, and named exemptions. Missing or mismatched
-   commit binding is a hard refusal. The verifier's sole interim
-   exemption is `WP-K8S-1000-CI-POSTGRES-TEARDOWN`; it is signature-scoped, tracked
-   by #1000, and retires when #1000 is fixed. These scripts are the _only_
-   sanctioned merge path.
+   CI before merging). These two scripts are the _only_ sanctioned merge path.
 3. **Never call the raw API** — the merge-gate **does NOT** call `tea`, the raw
    Gitea/forge HTTP API, or any other merge mechanism directly. Only `pr-merge.sh`
    and `pr-ci-wait.sh`.

packages/mosaic/framework/guides/CI-CD-PIPELINES.md

@@ -868,38 +868,6 @@ steps:
 7. **Test on a short-lived non-main branch first** — open a PR and verify quality gates before merging to `main`
 8. **Verify images appear** in Gitea Packages tab after successful pipeline
 
-## Terminal-Green Full-Step Contract
-
-A successful pipeline summary is not sufficient: verification MUST consume the full JSON/API child-step record, including `clone`.
-
-```bash
-PR_HEAD=<full-40-hex-provider-head>
-~/.config/mosaic/tools/woodpecker/pipeline-status.sh \
-  -r mosaicstack/stack -n <pipeline-number> -f json \
-  | ~/.config/mosaic/tools/woodpecker/verify-terminal-green.py \
-      --expect-commit "$PR_HEAD" -
-```
-
-`PR_HEAD` MUST come from the current provider PR metadata and MUST be the full 40-hex head, not a local branch guess. The verifier fails if the argument is missing, malformed, absent from the pipeline record, or differs from that record.
-
-The verifier reports the expected and observed commits, total step count, state counts, anomalies, and any applied exemption. Exit `0` means the record satisfies the contract; exit `1` means the commit binding or at least one pipeline, workflow, or child-step state blocks terminal-green; exit `2` means the invocation or JSON input could not be verified.
-
-### Named interim exemption: `WP-K8S-1000-CI-POSTGRES-TEARDOWN`
-
-Only this exact conjunction is exempted:
-
-- pipeline and workflow state are `success`;
-- exactly one non-success child exists;
-- its name is `ci-postgres` and type is `service`;
-- its state is `failure`, exit code is the JSON integer `0` (not boolean, float, string, or null); and
-- its error exactly matches `pods "wp-svc-<ULID>-ci-postgres" not found`.
-
-Every near miss remains blocking, including non-zero service exits, startup failures, post-readiness crashes, connection errors, image-pull errors, skipped steps, another failed child, malformed pod names, duplicate matches, or a non-success pipeline/workflow.
-
-**Boundary in both directions:** this exemption recognizes the observed Woodpecker Kubernetes reconciliation miss after an otherwise-successful run. It does not prove that every future PostgreSQL or Kubernetes failure is distinguishable. It does prove, through provider controls, that a deterministic startup failure (`exit_code=1`) and an armed post-readiness postmaster crash (`exit_code=137`, dependent probe `Connection refused`) do not match and remain red.
-
-**Tracking and retirement:** [mosaicstack/stack#1000](https://git.mosaicstack.dev/mosaicstack/stack/issues/1000) owns the provider-seam fix. This exemption MUST be removed when #1000 is fixed. It is not authority to retry or re-trigger a pipeline, and no per-PR re-roll is part of the contract.
-
 ## Post-Merge CI Monitoring (Hard Rule)
 
 For source-code delivery, completion is not allowed at "PR opened" stage.

packages/mosaic/framework/tools/woodpecker/README.md

@@ -26,13 +26,12 @@ A Woodpecker API token is required. To configure:
 
 ## Scripts
 
-| Script                     | Purpose                                                        |
-| -------------------------- | -------------------------------------------------------------- |
-| `pipeline-list.sh`         | List recent pipelines for a repo                               |
-| `pipeline-status.sh`       | Get status of a specific or latest pipeline                    |
-| `pipeline-trigger.sh`      | Trigger a new pipeline build                                   |
-| `ci-wait.sh`               | Block until pipeline(s) reach terminal state                   |
-| `verify-terminal-green.py` | Verify every JSON/API child step under the bounded CI contract |
+| Script                | Purpose                                      |
+| --------------------- | -------------------------------------------- |
+| `pipeline-list.sh`    | List recent pipelines for a repo             |
+| `pipeline-status.sh`  | Get status of a specific or latest pipeline  |
+| `pipeline-trigger.sh` | Trigger a new pipeline build                 |
+| `ci-wait.sh`          | Block until pipeline(s) reach terminal state |
 
 ## Common Options
 
@@ -60,9 +59,4 @@ A Woodpecker API token is required. To configure:
 
 # Block until one or more pipelines finish (event-driven CI wait)
 ~/.config/mosaic/tools/woodpecker/ci-wait.sh -r usc/uconnect -n 3917 -n 3918
-
-# Verify the full JSON child-step record; do not use the text summary for this gate
-PR_HEAD=<full-40-hex-provider-head>
-~/.config/mosaic/tools/woodpecker/pipeline-status.sh -r mosaicstack/stack -n 2188 -f json \
-  | ~/.config/mosaic/tools/woodpecker/verify-terminal-green.py --expect-commit "$PR_HEAD" -
 ```

packages/mosaic/framework/tools/woodpecker/test-terminal-green-contract.sh

@@ -1,109 +0,0 @@
-#!/usr/bin/env bash
-# Red-first contract harness for RM-61 / #1000.
-set -euo pipefail
-
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-VERIFIER="$SCRIPT_DIR/verify-terminal-green.py"
-EXPECTED_COMMIT=aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
-TMP=$(mktemp -d)
-trap 'rm -rf "$TMP"' EXIT
-
-write_fixture() {
-    local file="$1" pipeline_status="$2" postgres_state="$3" postgres_exit="$4" postgres_error="$5" test_state="$6"
-    python3 - "$file" "$pipeline_status" "$postgres_state" "$postgres_exit" "$postgres_error" "$test_state" <<'PY'
-import json, sys
-path, pipeline_status, pg_state, pg_exit, pg_error, test_state = sys.argv[1:]
-steps = [
-    {"name": "clone", "type": "clone", "state": "success", "exit_code": 0, "error": None},
-    {"name": "ci-postgres", "type": "service", "state": pg_state, "exit_code": int(pg_exit), "error": pg_error or None},
-    {"name": "test", "type": "commands", "state": test_state, "exit_code": 0 if test_state == "success" else 1, "error": None},
-]
-json.dump({
-    "number": 9999,
-    "status": pipeline_status,
-    "commit": "a" * 40,
-    "workflows": [{"name": "ci", "state": pipeline_status, "children": steps}],
-}, open(path, "w"))
-PY
-}
-
-expect_exit() {
-    local expected_exit="$1" label="$2" file="$3" expected_commit="${4:-$EXPECTED_COMMIT}"
-    set +e
-    output=$(python3 "$VERIFIER" --expect-commit "$expected_commit" "$file" 2>&1)
-    actual=$?
-    set -e
-    if [[ "$actual" -ne "$expected_exit" ]]; then
-        printf 'FAIL %s: expected exit %s, got %s\n%s\n' "$label" "$expected_exit" "$actual" "$output" >&2
-        exit 1
-    fi
-    printf 'PASS %s\n' "$label"
-    printf '%s' "$output"
-}
-
-# Ordinary terminal green.
-write_fixture "$TMP/green.json" success success 0 '' success
-out=$(expect_exit 0 green "$TMP/green.json")
-grep -q '"total_steps": 3' <<<"$out"
-grep -q '"exempted_steps": 0' <<<"$out"
-
-# Exact, named #1000 teardown artifact: the only permitted non-success child.
-artifact='pods "wp-svc-01kyxzjhdf6w81swsnbfzh85z9-ci-postgres" not found'
-write_fixture "$TMP/artifact.json" success failure 0 "$artifact" success
-out=$(expect_exit 0 exact-artifact "$TMP/artifact.json")
-grep -q '"exemption_id": "WP-K8S-1000-CI-POSTGRES-TEARDOWN"' <<<"$out"
-grep -q '"exempted_steps": 1' <<<"$out"
-
-# Negative controls: both real PostgreSQL failures must remain red.
-write_fixture "$TMP/startup.json" failure failure 1 '' failure
-expect_exit 1 startup-failure "$TMP/startup.json" >/dev/null
-write_fixture "$TMP/crash.json" failure failure 137 '' failure
-expect_exit 1 post-readiness-crash "$TMP/crash.json" >/dev/null
-
-# The exemption is signature-scoped, not step-scoped.
-write_fixture "$TMP/wrong-error.json" success failure 0 'connection refused' success
-expect_exit 1 other-postgres-error "$TMP/wrong-error.json" >/dev/null
-write_fixture "$TMP/wrong-pod.json" success failure 0 'pods "other-ci-postgres" not found' success
-expect_exit 1 wrong-pod-signature "$TMP/wrong-pod.json" >/dev/null
-write_fixture "$TMP/nonzero-artifact.json" success failure 137 "$artifact" success
-expect_exit 1 nonzero-with-artifact-text "$TMP/nonzero-artifact.json" >/dev/null
-
-# JSON booleans and non-integer zero look equal to 0 in Python but are not exit codes.
-python3 - "$TMP/artifact.json" "$TMP" <<'PY'
-import json, os, sys
-record = json.load(open(sys.argv[1]))
-for label, value in (("false", False), ("true", True), ("float", 0.0), ("string", "0"), ("null", None)):
-    changed = json.loads(json.dumps(record))
-    changed["workflows"][0]["children"][1]["exit_code"] = value
-    json.dump(changed, open(os.path.join(sys.argv[2], f"exit-{label}.json"), "w"))
-PY
-for label in false true float string null; do
-    expect_exit 1 "non-integer-exit-$label" "$TMP/exit-$label.json" >/dev/null
-done
-
-# Exact artifact cannot mask any independent failure or non-success pipeline.
-write_fixture "$TMP/artifact-plus-failure.json" failure failure 0 "$artifact" failure
-expect_exit 1 artifact-plus-real-failure "$TMP/artifact-plus-failure.json" >/dev/null
-write_fixture "$TMP/skipped.json" success success 0 '' skipped
-expect_exit 1 skipped-step "$TMP/skipped.json" >/dev/null
-
-# The scanned pipeline must be bound to an explicit, full PR-head commit.
-set +e
-missing_output=$(python3 "$VERIFIER" "$TMP/artifact.json" 2>&1)
-missing_rc=$?
-set -e
-if [[ "$missing_rc" -ne 2 ]] || ! grep -q -- '--expect-commit' <<<"$missing_output"; then
-    printf 'FAIL missing-expected-commit: expected usage exit 2\n%s\n' "$missing_output" >&2
-    exit 1
-fi
-expect_exit 1 mismatched-expected-commit "$TMP/artifact.json" bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb >/dev/null
-
-python3 - "$TMP/artifact.json" "$TMP/missing-record-commit.json" <<'PY'
-import json, sys
-record = json.load(open(sys.argv[1]))
-record.pop("commit")
-json.dump(record, open(sys.argv[2], "w"))
-PY
-expect_exit 1 missing-record-commit "$TMP/missing-record-commit.json" >/dev/null
-
-printf 'terminal-green contract harness: PASS (17 cases)\n'

packages/mosaic/framework/tools/woodpecker/verify-terminal-green.py

@@ -1,230 +0,0 @@
-#!/usr/bin/env python3
-"""Verify Mosaic's full-step Woodpecker terminal-green contract.
-
-RM-61 permits one named, signature-scoped exception for issue #1000. The
-exception retires when #1000 is fixed; all other non-success states block.
-This program consumes the JSON/API record emitted by pipeline-status.sh -f json.
-It does not fetch, retry, or re-trigger pipelines.
-"""
-
-from __future__ import annotations
-
-import argparse
-import json
-import re
-import sys
-from collections import Counter
-from pathlib import Path
-from typing import Any
-
-EXEMPTION_ID = "WP-K8S-1000-CI-POSTGRES-TEARDOWN"
-EXEMPTION_ISSUE = "https://git.mosaicstack.dev/mosaicstack/stack/issues/1000"
-POD_NOT_FOUND = re.compile(
-    r'^pods "wp-svc-[0-9a-hjkmnp-tv-z]{26}-ci-postgres" not found$'
-)
-
-
-def fail_usage(message: str) -> int:
-    print(f"terminal-green contract input error: {message}", file=sys.stderr)
-    return 2
-
-
-def load_record(argument: str | None) -> dict[str, Any]:
-    if argument in (None, "-"):
-        value = json.load(sys.stdin)
-    else:
-        with Path(argument).open(encoding="utf-8") as handle:
-            value = json.load(handle)
-    if not isinstance(value, dict):
-        raise ValueError("pipeline record must be a JSON object")
-    return value
-
-
-def is_issue_1000_artifact(step: dict[str, Any]) -> bool:
-    error = step.get("error")
-    exit_code = step.get("exit_code")
-    return (
-        step.get("name") == "ci-postgres"
-        and step.get("type") == "service"
-        and step.get("state") == "failure"
-        and type(exit_code) is int
-        and not isinstance(exit_code, bool)
-        and exit_code == 0
-        and isinstance(error, str)
-        and POD_NOT_FOUND.fullmatch(error) is not None
-    )
-
-
-def verify(record: dict[str, Any], expected_commit: str) -> tuple[int, dict[str, Any]]:
-    anomalies: list[dict[str, Any]] = []
-    candidates: list[dict[str, Any]] = []
-    steps: list[dict[str, Any]] = []
-
-    pipeline_status = record.get("status")
-    actual_commit = record.get("commit")
-    if actual_commit != expected_commit:
-        anomalies.append(
-            {
-                "scope": "pipeline",
-                "name": str(record.get("number", "unknown")),
-                "state": pipeline_status,
-                "reason": "pipeline commit does not equal the expected PR head",
-                "expected_commit": expected_commit,
-                "actual_commit": actual_commit,
-            }
-        )
-    if pipeline_status != "success":
-        anomalies.append(
-            {
-                "scope": "pipeline",
-                "name": str(record.get("number", "unknown")),
-                "state": pipeline_status,
-                "reason": "pipeline status is not success",
-            }
-        )
-
-    workflows = record.get("workflows")
-    if not isinstance(workflows, list) or not workflows:
-        anomalies.append(
-            {
-                "scope": "pipeline",
-                "name": str(record.get("number", "unknown")),
-                "state": pipeline_status,
-                "reason": "workflows are missing or empty",
-            }
-        )
-        workflows = []
-
-    for workflow_index, workflow in enumerate(workflows):
-        if not isinstance(workflow, dict):
-            anomalies.append(
-                {
-                    "scope": "workflow",
-                    "name": str(workflow_index),
-                    "state": None,
-                    "reason": "workflow is not an object",
-                }
-            )
-            continue
-        workflow_name = str(workflow.get("name", workflow_index))
-        if workflow.get("state") != "success":
-            anomalies.append(
-                {
-                    "scope": "workflow",
-                    "name": workflow_name,
-                    "state": workflow.get("state"),
-                    "reason": "workflow state is not success",
-                }
-            )
-        children = workflow.get("children")
-        if not isinstance(children, list) or not children:
-            anomalies.append(
-                {
-                    "scope": "workflow",
-                    "name": workflow_name,
-                    "state": workflow.get("state"),
-                    "reason": "child-step list is missing or empty",
-                }
-            )
-            continue
-        for child_index, child in enumerate(children):
-            if not isinstance(child, dict):
-                anomalies.append(
-                    {
-                        "scope": "step",
-                        "name": f"{workflow_name}[{child_index}]",
-                        "state": None,
-                        "reason": "step is not an object",
-                    }
-                )
-                continue
-            steps.append(child)
-            if child.get("state") == "success":
-                continue
-            if is_issue_1000_artifact(child):
-                candidates.append(child)
-                continue
-            anomalies.append(
-                {
-                    "scope": "step",
-                    "name": child.get("name"),
-                    "type": child.get("type"),
-                    "state": child.get("state"),
-                    "exit_code": child.get("exit_code"),
-                    "error": child.get("error"),
-                    "reason": "non-success step does not match the #1000 teardown signature",
-                }
-            )
-
-    if len(candidates) > 1:
-        anomalies.append(
-            {
-                "scope": "exemption",
-                "name": EXEMPTION_ID,
-                "state": "invalid",
-                "reason": "the #1000 exemption may apply to exactly one step",
-            }
-        )
-
-    exemption_applies = len(candidates) == 1 and not anomalies
-    state_counts = Counter(str(step.get("state", "missing")) for step in steps)
-    result: dict[str, Any] = {
-        "schema_version": "mosaic-terminal-green/v1",
-        "verdict": "terminal-green" if not anomalies else "not-terminal-green",
-        "pipeline_number": record.get("number"),
-        "commit": actual_commit,
-        "expected_commit": expected_commit,
-        "pipeline_status": pipeline_status,
-        "total_steps": len(steps),
-        "state_counts": dict(sorted(state_counts.items())),
-        "exempted_steps": 1 if exemption_applies else 0,
-        "anomalies": anomalies,
-    }
-    if exemption_applies:
-        candidate = candidates[0]
-        result["exemptions"] = [
-            {
-                "exemption_id": EXEMPTION_ID,
-                "step": candidate.get("name"),
-                "signature": candidate.get("error"),
-                "tracking_issue": EXEMPTION_ISSUE,
-                "retires_when": "issue #1000 is fixed",
-            }
-        ]
-    else:
-        result["exemptions"] = []
-
-    return (0 if not anomalies else 1), result
-
-
-def parse_arguments() -> argparse.Namespace:
-    parser = argparse.ArgumentParser(
-        description="verify the full Woodpecker terminal-green child-step contract"
-    )
-    parser.add_argument(
-        "--expect-commit",
-        required=True,
-        metavar="FULL_SHA",
-        help="full 40-hex PR-head commit that the pipeline record must match",
-    )
-    parser.add_argument("record", nargs="?", default="-", help="pipeline JSON file or -")
-    arguments = parser.parse_args()
-    if re.fullmatch(r"[0-9a-fA-F]{40}", arguments.expect_commit) is None:
-        parser.error("--expect-commit must be a full 40-hex commit")
-    arguments.expect_commit = arguments.expect_commit.lower()
-    return arguments
-
-
-def main() -> int:
-    arguments = parse_arguments()
-    try:
-        record = load_record(arguments.record)
-    except (OSError, ValueError, json.JSONDecodeError) as error:
-        return fail_usage(str(error))
-    code, result = verify(record, arguments.expect_commit)
-    print(json.dumps(result, indent=2, sort_keys=True))
-    return code
-
-
-if __name__ == "__main__":
-    raise SystemExit(main())

packages/mosaic/package.json

@@ -25,7 +25,7 @@
     "lint": "eslint src",
     "typecheck": "tsc --noEmit",
     "test": "vitest run --passWithNoTests && pnpm run test:framework-shell",
-    "test:framework-shell": "bash framework/tools/quality/scripts/check-test-enumeration.sh && bash framework/tools/quality/scripts/test-check-test-enumeration.sh && python3 src/lease-broker/daemon_deadline_unittest.py && python3 src/lease-broker/normative_fragments_unittest.py && python3 src/lease-broker/receipt_challenge_unittest.py && python3 src/lease-broker/context_recovery_unittest.py && python3 src/lease-broker/recovery_runtime_unittest.py && python3 src/lease-broker/recovery_b1_adversarial_unittest.py && python3 src/lease-broker/framework_skill_portability_unittest.py && python3 src/mutator-gate/runtime_tools_unittest.py && python3 src/mutator-gate/runtime_launch_guard_unittest.py && python3 src/mutator-gate/version_coupling_unittest.py && python3 framework/tools/lease-broker/check-runtime-launches.py --root ../.. && bash framework/tools/codex/test-pr-diff-context.sh && bash framework/tools/qa/test-deps-preflight.sh && bash framework/tools/git/test-pr-review-gitea-comment.sh && bash framework/tools/git/test-pr-review-repo-host-override.sh && bash framework/tools/git/test-ci-queue-wait-branch-absent.sh && bash framework/tools/git/test-git-credential-mosaic.sh && bash framework/tools/git/test-gitea-token-identity.sh && bash framework/tools/woodpecker/test-terminal-green-contract.sh && bash framework/tools/_scripts/test-install-ordering-guard.sh && bash framework/tools/tmux/agent-send.test.sh && bash framework/tools/wake/test-wake-store-ack.sh && bash framework/tools/wake/test-wake-store-enqueue-race.sh && bash framework/tools/wake/test-wake-digest-hmac.sh && bash framework/tools/wake/test-wake-digest-quarantine.sh && bash framework/tools/wake/test-wake-detector.sh && bash framework/tools/wake/test-wake-fn-oracle.sh && bash framework/tools/wake/test-wake-reconcile.sh && bash framework/tools/wake/test-wake-beacon.sh && bash framework/tools/wake/test-wake-preimage.sh && bash framework/tools/wake/test-wake-install.sh"
+    "test:framework-shell": "bash framework/tools/quality/scripts/check-test-enumeration.sh && bash framework/tools/quality/scripts/test-check-test-enumeration.sh && python3 src/lease-broker/daemon_deadline_unittest.py && python3 src/lease-broker/normative_fragments_unittest.py && python3 src/lease-broker/receipt_challenge_unittest.py && python3 src/lease-broker/context_recovery_unittest.py && python3 src/lease-broker/recovery_runtime_unittest.py && python3 src/lease-broker/recovery_b1_adversarial_unittest.py && python3 src/lease-broker/framework_skill_portability_unittest.py && python3 src/mutator-gate/runtime_tools_unittest.py && python3 src/mutator-gate/runtime_launch_guard_unittest.py && python3 src/mutator-gate/version_coupling_unittest.py && python3 framework/tools/lease-broker/check-runtime-launches.py --root ../.. && bash framework/tools/codex/test-pr-diff-context.sh && bash framework/tools/qa/test-deps-preflight.sh && bash framework/tools/git/test-pr-review-gitea-comment.sh && bash framework/tools/git/test-pr-review-repo-host-override.sh && bash framework/tools/git/test-ci-queue-wait-branch-absent.sh && bash framework/tools/git/test-git-credential-mosaic.sh && bash framework/tools/git/test-gitea-token-identity.sh && bash framework/tools/_scripts/test-install-ordering-guard.sh && bash framework/tools/tmux/agent-send.test.sh && bash framework/tools/wake/test-wake-store-ack.sh && bash framework/tools/wake/test-wake-store-enqueue-race.sh && bash framework/tools/wake/test-wake-digest-hmac.sh && bash framework/tools/wake/test-wake-digest-quarantine.sh && bash framework/tools/wake/test-wake-detector.sh && bash framework/tools/wake/test-wake-fn-oracle.sh && bash framework/tools/wake/test-wake-reconcile.sh && bash framework/tools/wake/test-wake-beacon.sh && bash framework/tools/wake/test-wake-preimage.sh && bash framework/tools/wake/test-wake-install.sh"
   },
   "dependencies": {
     "@mosaicstack/brain": "workspace:*",

scripts/gate-empty-population-control.mjs

@@ -1,44 +0,0 @@
-#!/usr/bin/env node
-
-import { mkdtemp, readFile, rm, writeFile } from 'node:fs/promises';
-import os from 'node:os';
-import path from 'node:path';
-
-import { verifyRegistry } from './gate-verify.mjs';
-
-const root = process.cwd();
-const manifest = JSON.parse(await readFile(path.join(root, 'gates/gates.manifest.json'), 'utf8'));
-manifest.gateRoots = ['.mosaic-empty-gate-root'];
-manifest.criteria = [];
-manifest.gates = [];
-manifest.proseClaims = [];
-manifest.compatibilityScenarios = [];
-const directory = await mkdtemp(path.join(os.tmpdir(), 'gate-empty-population-'));
-try {
-  const manifestPath = path.join(directory, 'manifest.json');
-  await writeFile(manifestPath, `${JSON.stringify(manifest)}\n`);
-  const result = await verifyRegistry({
-    root,
-    manifest: manifestPath,
-    structureOnly: true,
-    fixtureProfile: false,
-  });
-  const required = ['criteria', 'gates', 'proseClaims', 'compatibilityScenarios'];
-  const missing = required.filter(
-    (population) =>
-      !result.failures.some((failure) =>
-        failure.includes(`${population} population must be non-empty and anchored`),
-      ),
-  );
-  if (missing.length > 0) {
-    process.stdout.write(`empty populations were not rejected: ${missing.join(', ')}\n`);
-    process.exitCode = 0;
-  } else {
-    process.stderr.write(
-      'empty universally quantified registry populations rejected before evaluation\n',
-    );
-    process.exitCode = 1;
-  }
-} finally {
-  await rm(directory, { recursive: true, force: true });
-}

scripts/gate-history-exclusion-control.mjs

@@ -1,48 +0,0 @@
-#!/usr/bin/env node
-
-import { readFile } from 'node:fs/promises';
-import path from 'node:path';
-
-import { assertCurrentTreeObservation } from './gate-verify.mjs';
-
-const prohibitedReports = [
-  'HISTORY PROVENANCE VERIFIED local-ref',
-  'COMMIT ANCESTRY VERIFIED origin/main',
-  'PROVIDER LINEAGE SUCCESS pipeline-7',
-];
-const accepted = prohibitedReports.filter((report) => {
-  try {
-    assertCurrentTreeObservation(report);
-    return true;
-  } catch {
-    return false;
-  }
-});
-
-const verifier = await readFile(path.join(process.cwd(), 'scripts', 'gate-verify.mjs'), 'utf8');
-const stdoutWrites = [...verifier.matchAll(/process\.stdout\.write\s*\(/g)].length;
-const stderrWrites = [...verifier.matchAll(/process\.stderr\.write\s*\(/g)].length;
-const gatedErrorWrites = [...verifier.matchAll(/process\.stderr\.write\(`GATE VERIFY FAILED:/g)]
-  .length;
-const currentTreeWriterCalls = [...verifier.matchAll(/writeCurrentTreeOutput\s*\(/g)].length;
-const productionRendererWired =
-  stdoutWrites === 1 &&
-  stderrWrites === 2 &&
-  gatedErrorWrites === 2 &&
-  currentTreeWriterCalls === 3 &&
-  /function writeCurrentTreeOutput\(output\) \{\s*assertCurrentTreeObservation\(output\);\s*process\.stdout\.write/s.test(
-    verifier,
-  ) &&
-  /for \(const observation of observations\) \{\s*writeCurrentTreeOutput\(observation\);\s*\}/s.test(
-    verifier,
-  ) &&
-  /writeCurrentTreeOutput\(\s*`REGISTRY SUMMARY open behavior deltas:/s.test(verifier) &&
-  !/\bconsole\.(?:log|info|debug|error|warn)\s*\(/.test(verifier);
-
-if (accepted.length > 0 || !productionRendererWired) {
-  process.stderr.write(
-    `HISTORY_PROVENANCE_FORBIDDEN: closed current-tree observation renderer rejected=${prohibitedReports.length - accepted.length}/${prohibitedReports.length} production-wired=${productionRendererWired}\n`,
-  );
-  process.exit(79);
-}
-process.stdout.write('history provenance reporting capability is absent; owner RM-60\n');

scripts/gate-inventory-claim-control.mjs

@@ -1,44 +0,0 @@
-#!/usr/bin/env node
-
-import { readFile } from 'node:fs/promises';
-import path from 'node:path';
-
-const boundary =
-  "Detects accidental and incompetent inventory drift within a checkout; does NOT survive an adversary who rewrites baseline, manifest, and verifier consistently — that guarantee requires RM-60's external boundary.";
-const artifacts = [
-  'gates/required-gates.baseline.json',
-  'gates/gates.manifest.json',
-  'docs/PRD.md',
-  'docs/ADMIN-GUIDE/quality-gate-registry.md',
-  'docs/DEVELOPER-GUIDE/quality-gate-registry.md',
-  'docs/remediation/GATE-CLAIMS.md',
-  'docs/plans/2026-08-01-rm-02-gate-registry.md',
-  'docs/SITEMAP.md',
-];
-const forbidden = [
-  /\bindependent\b[^\n.]{0,80}\bbaseline\b/i,
-  /independently baselined/i,
-  /independently anchored inventory/i,
-  /protected (?:inventory )?(?:anchor|baseline)/i,
-  /inventory (?:anchor|anchored)/i,
-];
-const failures = [];
-for (const relativePath of artifacts) {
-  const contents = await readFile(path.join(process.cwd(), relativePath), 'utf8');
-  const claims =
-    relativePath === 'gates/gates.manifest.json'
-      ? JSON.parse(contents)
-          .criteria.map((criterion) => criterion.currentText)
-          .join('\n')
-      : contents;
-  if (!claims.includes(boundary)) failures.push(`${relativePath}: narrowed boundary is missing`);
-  const overclaim = forbidden.find((pattern) => pattern.test(claims));
-  if (overclaim) failures.push(`${relativePath}: inventory protection is overstated`);
-}
-if (failures.length > 0) {
-  for (const failure of failures) {
-    process.stderr.write(`INVENTORY_CLAIM_OVERSTATED: ${failure}\n`);
-  }
-  process.exit(84);
-}
-process.stdout.write('inventory drift boundary is stated in both directions; owner RM-60\n');

scripts/gate-inventory-shrink-control.mjs

@@ -1,119 +0,0 @@
-#!/usr/bin/env node
-
-import assert from 'node:assert/strict';
-import { copyFile, mkdir, mkdtemp, readFile, rm, writeFile } from 'node:fs/promises';
-import os from 'node:os';
-import path from 'node:path';
-import { spawnSync } from 'node:child_process';
-
-const root = process.cwd();
-const removedGateId = 'hook-pre-push';
-const inventoryEntry = "  ['hook-pre-push', '.husky/pre-push'],\n";
-
-function shrinkManifest(manifest) {
-  const removedGate = manifest.gates.find((gate) => gate.id === removedGateId);
-  assert.ok(removedGate);
-  const removedCaseRefs = new Set(
-    removedGate.cases.map((gateCase) => `${removedGateId}/${gateCase.id}`),
-  );
-  const removedCriterionIds = new Set(
-    manifest.criteria
-      .filter(
-        (criterion) =>
-          criterion.caseRefs.length > 0 &&
-          criterion.caseRefs.every((caseRef) => removedCaseRefs.has(caseRef)),
-      )
-      .map((criterion) => criterion.id),
-  );
-  manifest.gates = manifest.gates.filter((gate) => gate.id !== removedGateId);
-  manifest.criteria = manifest.criteria
-    .filter((criterion) => !removedCriterionIds.has(criterion.id))
-    .map((criterion) => ({
-      ...criterion,
-      caseRefs: criterion.caseRefs.filter((caseRef) => !removedCaseRefs.has(caseRef)),
-      ...(criterion.gateRefs
-        ? { gateRefs: criterion.gateRefs.filter((gateId) => gateId !== removedGateId) }
-        : {}),
-    }));
-  manifest.proseClaims = manifest.proseClaims.filter(
-    (claim) => !removedCriterionIds.has(claim.criterionId) && !removedCaseRefs.has(claim.caseRef),
-  );
-  manifest.compatibilityScenarios = manifest.compatibilityScenarios
-    .map((scenario) => ({
-      ...scenario,
-      caseRefs: scenario.caseRefs.filter((caseRef) => !removedCaseRefs.has(caseRef)),
-    }))
-    .filter((scenario) => scenario.caseRefs.length > 0);
-  for (const gate of manifest.gates) {
-    for (const gateCase of gate.cases) {
-      gateCase.criterionIds = gateCase.criterionIds.filter(
-        (criterionId) => !removedCriterionIds.has(criterionId),
-      );
-    }
-  }
-}
-
-async function attack(mode) {
-  const fixture = await mkdtemp(path.join(os.tmpdir(), `gate-inventory-${mode}-`));
-  try {
-    await mkdir(path.join(fixture, 'scripts'), { recursive: true });
-    await mkdir(path.join(fixture, 'gates'), { recursive: true });
-    const source = await readFile(path.join(root, 'scripts', 'gate-verify.mjs'), 'utf8');
-    if (source.split(inventoryEntry).length - 1 !== 1) {
-      throw new Error('source inventory fixture drifted');
-    }
-    await writeFile(
-      path.join(fixture, 'scripts', 'gate-verify.mjs'),
-      mode === 'source-manifest' ? source.replace(inventoryEntry, '') : source,
-    );
-    const baseline = JSON.parse(
-      await readFile(path.join(root, 'gates', 'required-gates.baseline.json'), 'utf8'),
-    );
-    if (mode === 'baseline-manifest') {
-      baseline.gates = baseline.gates.filter((gate) => gate.id !== removedGateId);
-    }
-    await writeFile(
-      path.join(fixture, 'gates', 'required-gates.baseline.json'),
-      `${JSON.stringify(baseline)}\n`,
-    );
-    const manifest = JSON.parse(
-      await readFile(path.join(root, 'gates', 'gates.manifest.json'), 'utf8'),
-    );
-    shrinkManifest(manifest);
-    await writeFile(
-      path.join(fixture, 'gates', 'gates.manifest.json'),
-      `${JSON.stringify(manifest)}\n`,
-    );
-    const result = spawnSync(
-      process.execPath,
-      [
-        path.join(fixture, 'scripts', 'gate-verify.mjs'),
-        '--root',
-        fixture,
-        '--manifest',
-        'gates/gates.manifest.json',
-        '--structure-only',
-      ],
-      { cwd: fixture, encoding: 'utf8' },
-    );
-    const combined = `${result.stdout ?? ''}\n${result.stderr ?? ''}`;
-    return (
-      result.status !== 0 &&
-      new RegExp(`(?:baseline|verifier inventory).*${removedGateId}`, 'i').test(combined)
-    );
-  } finally {
-    await rm(fixture, { recursive: true, force: true });
-  }
-}
-
-const sourceManifestRejected = await attack('source-manifest');
-const baselineManifestRejected = await attack('baseline-manifest');
-if (sourceManifestRejected && baselineManifestRejected) {
-  process.stderr.write(
-    'INVENTORY_SHRINK_REJECTED: source+manifest and baseline+manifest shrink attacks detected\n',
-  );
-  process.exit(83);
-}
-process.stdout.write(
-  `inventory shrink attack escaped: source-manifest=${sourceManifestRejected} baseline-manifest=${baselineManifestRejected}\n`,
-);

scripts/gate-population-control.mjs

@@ -1,138 +0,0 @@
-#!/usr/bin/env node
-
-import { chmod, mkdir, mkdtemp, readFile, rm, writeFile } from 'node:fs/promises';
-import os from 'node:os';
-import path from 'node:path';
-
-import { verifyRegistry } from './gate-verify.mjs';
-
-const mode = process.argv[2];
-const root = process.cwd();
-const source = JSON.parse(await readFile(path.join(root, 'gates/gates.manifest.json'), 'utf8'));
-const expectedGateIds = source.gates.map((gate) => gate.id);
-if (expectedGateIds.length === 0) {
-  process.stderr.write('gate population control requires a non-empty anchored inventory\n');
-  process.exit(2);
-}
-
-async function rejectedForEveryGate(mutate, diagnostic) {
-  for (const gateId of expectedGateIds) {
-    const manifest = structuredClone(source);
-    const gate = manifest.gates.find((candidate) => candidate.id === gateId);
-    mutate(gate);
-    const directory = await mkdtemp(path.join(os.tmpdir(), 'gate-population-control-'));
-    const manifestPath = path.join(directory, 'manifest.json');
-    try {
-      await writeFile(manifestPath, `${JSON.stringify(manifest)}\n`);
-      const result = await verifyRegistry({
-        root,
-        manifest: manifestPath,
-        structureOnly: true,
-        fixtureProfile: false,
-      });
-      if (!result.failures.some((failure) => diagnostic(failure, gateId))) return false;
-    } finally {
-      await rm(directory, { recursive: true, force: true });
-    }
-  }
-  return true;
-}
-
-let rejected;
-if (mode === 'evidence-subject') {
-  rejected = true;
-  for (const gateId of expectedGateIds) {
-    const directory = await mkdtemp(path.join(os.tmpdir(), 'gate-evidence-consumption-'));
-    try {
-      await mkdir(path.join(directory, 'gates'), { recursive: true });
-      const probe = path.join(directory, 'gates', 'probe.sh');
-      await writeFile(probe, '#!/bin/sh\necho EVIDENCE_PROBE >&2\nexit 7\n');
-      await chmod(probe, 0o755);
-      const manifest = {
-        schemaVersion: 1,
-        gateRoots: ['gates'],
-        governingClaimFiles: [],
-        coverageBoundary: { included: ['evidence fixture'], excluded: [], trackedBy: 'RM-02' },
-        criteria: [
-          {
-            id: 'EVIDENCE-CONSUMPTION',
-            originalText: 'Consumed evidence stays bound to its gate.',
-            currentText: 'Consumed evidence stays bound to its gate.',
-            claimType: 'integrity',
-            source: 'gate-population-control',
-            meaningChanges: [],
-            caseRefs: [`${gateId}/probe`],
-          },
-        ],
-        proseClaims: [],
-        compatibilityScenarios: [],
-        gates: [
-          {
-            id: gateId,
-            source: 'gates/probe.sh',
-            invocation: ['gates/probe.sh'],
-            deployment: { kind: 'none', reason: 'population fixture' },
-            inertMutation: {
-              file: 'gates/probe.sh',
-              find: 'exit 7',
-              replace: 'exit 0',
-              caseId: 'probe',
-              expected: { exitCode: 0 },
-            },
-            cases: [
-              {
-                id: 'probe',
-                criterionIds: ['EVIDENCE-CONSUMPTION'],
-                mustFail: true,
-                required: { exitCode: 7 },
-                actual: { exitCode: 7 },
-                evidence: { subject: 'different-gate-subject' },
-                reasonPattern: 'EVIDENCE_PROBE',
-              },
-            ],
-          },
-        ],
-      };
-      const manifestPath = path.join(directory, 'gates', 'gates.manifest.json');
-      await writeFile(manifestPath, `${JSON.stringify(manifest)}\n`);
-      const result = await verifyRegistry({
-        root: directory,
-        manifest: manifestPath,
-        structureOnly: false,
-        fixtureProfile: true,
-      });
-      if (
-        !result.failures.some(
-          (failure) =>
-            failure.includes(`gate ${gateId}: consumed evidence subject`) &&
-            failure.includes('does not match gate definition'),
-        )
-      ) {
-        rejected = false;
-        break;
-      }
-    } finally {
-      await rm(directory, { recursive: true, force: true });
-    }
-  }
-} else if (mode === 'type-strict') {
-  rejected = await rejectedForEveryGate(
-    (gate) => {
-      gate.cases[0].actual.exitCode = '0';
-    },
-    (failure, gateId) =>
-      failure.includes(
-        `${gateId}/${source.gates.find((gate) => gate.id === gateId).cases[0].id}.actual.exitCode`,
-      ) && failure.includes('expected an integer'),
-  );
-} else {
-  process.stderr.write(`unknown gate population control ${String(mode)}\n`);
-  process.exit(2);
-}
-
-if (!rejected) {
-  process.stdout.write(`${mode} population control did not reject every registered gate\n`);
-  process.exit(0);
-}
-process.stderr.write(`${mode} population control rejected every registered gate\n`);
-process.exit(1);

scripts/gate-remediation.test.mjs

@@ -1,283 +0,0 @@
-import assert from 'node:assert/strict';
-import { copyFile, mkdir, mkdtemp, readFile, rm, writeFile } from 'node:fs/promises';
-import os from 'node:os';
-import path from 'node:path';
-import { spawnSync } from 'node:child_process';
-import test from 'node:test';
-
-const root = process.cwd();
-const verifierPath = path.join(root, 'scripts', 'gate-verify.mjs');
-const manifestPath = path.join(root, 'gates', 'gates.manifest.json');
-const requiredGateId = 'hook-pre-push';
-
-function output(result) {
-  return `${result.stdout ?? ''}\n${result.stderr ?? ''}`;
-}
-
-function shrinkManifest(manifest, removedGateId) {
-  const removedGate = manifest.gates.find((gate) => gate.id === removedGateId);
-  assert.ok(removedGate, `fixture gate ${removedGateId} must exist`);
-  const removedCaseRefs = new Set(
-    removedGate.cases.map((gateCase) => `${removedGateId}/${gateCase.id}`),
-  );
-  const removedCriterionIds = new Set(
-    manifest.criteria
-      .filter(
-        (criterion) =>
-          criterion.caseRefs.length > 0 &&
-          criterion.caseRefs.every((caseRef) => removedCaseRefs.has(caseRef)),
-      )
-      .map((criterion) => criterion.id),
-  );
-
-  manifest.gates = manifest.gates.filter((gate) => gate.id !== removedGateId);
-  manifest.criteria = manifest.criteria
-    .filter((criterion) => !removedCriterionIds.has(criterion.id))
-    .map((criterion) => ({
-      ...criterion,
-      caseRefs: criterion.caseRefs.filter((caseRef) => !removedCaseRefs.has(caseRef)),
-      ...(criterion.gateRefs
-        ? { gateRefs: criterion.gateRefs.filter((gateId) => gateId !== removedGateId) }
-        : {}),
-    }));
-  manifest.proseClaims = manifest.proseClaims.filter(
-    (claim) => !removedCriterionIds.has(claim.criterionId) && !removedCaseRefs.has(claim.caseRef),
-  );
-  manifest.compatibilityScenarios = manifest.compatibilityScenarios
-    .map((scenario) => ({
-      ...scenario,
-      caseRefs: scenario.caseRefs.filter((caseRef) => !removedCaseRefs.has(caseRef)),
-    }))
-    .filter((scenario) => scenario.caseRefs.length > 0);
-  for (const gate of manifest.gates) {
-    for (const gateCase of gate.cases) {
-      gateCase.criterionIds = gateCase.criterionIds.filter(
-        (criterionId) => !removedCriterionIds.has(criterionId),
-      );
-    }
-  }
-}
-
-test('shrinking the verifier inventory and manifest together is rejected by a same-checkout baseline', async () => {
-  const fixture = await mkdtemp(path.join(os.tmpdir(), 'rm02-shrink-both-'));
-  try {
-    await mkdir(path.join(fixture, 'scripts'), { recursive: true });
-    await mkdir(path.join(fixture, 'gates'), { recursive: true });
-    const verifier = await readFile(verifierPath, 'utf8');
-    const inventoryEntry = "  ['hook-pre-push', '.husky/pre-push'],\n";
-    assert.equal(verifier.split(inventoryEntry).length - 1, 1, 'source inventory fixture drifted');
-    await writeFile(
-      path.join(fixture, 'scripts', 'gate-verify.mjs'),
-      verifier.replace(inventoryEntry, ''),
-    );
-    await copyFile(
-      path.join(root, 'gates', 'required-gates.baseline.json'),
-      path.join(fixture, 'gates', 'required-gates.baseline.json'),
-    );
-    const manifest = JSON.parse(await readFile(manifestPath, 'utf8'));
-    shrinkManifest(manifest, requiredGateId);
-    await writeFile(
-      path.join(fixture, 'gates', 'gates.manifest.json'),
-      `${JSON.stringify(manifest)}\n`,
-    );
-
-    const result = spawnSync(
-      process.execPath,
-      [
-        path.join(fixture, 'scripts', 'gate-verify.mjs'),
-        '--root',
-        fixture,
-        '--manifest',
-        'gates/gates.manifest.json',
-        '--structure-only',
-      ],
-      { cwd: fixture, encoding: 'utf8' },
-    );
-    assert.notEqual(result.status, 0, 'shrinking source anchor and manifest together must go red');
-    assert.match(output(result), /same-checkout required-gate baseline.*hook-pre-push/i);
-  } finally {
-    await rm(fixture, { recursive: true, force: true });
-  }
-});
-
-test('shrinking the same-checkout baseline and manifest together is rejected by verifier inventory', async () => {
-  const fixture = await mkdtemp(path.join(os.tmpdir(), 'rm02-shrink-baseline-manifest-'));
-  try {
-    await mkdir(path.join(fixture, 'scripts'), { recursive: true });
-    await mkdir(path.join(fixture, 'gates'), { recursive: true });
-    await copyFile(verifierPath, path.join(fixture, 'scripts', 'gate-verify.mjs'));
-    const baseline = JSON.parse(
-      await readFile(path.join(root, 'gates', 'required-gates.baseline.json'), 'utf8'),
-    );
-    baseline.gates = baseline.gates.filter((gate) => gate.id !== requiredGateId);
-    await writeFile(
-      path.join(fixture, 'gates', 'required-gates.baseline.json'),
-      `${JSON.stringify(baseline)}\n`,
-    );
-    const manifest = JSON.parse(await readFile(manifestPath, 'utf8'));
-    shrinkManifest(manifest, requiredGateId);
-    await writeFile(
-      path.join(fixture, 'gates', 'gates.manifest.json'),
-      `${JSON.stringify(manifest)}\n`,
-    );
-
-    const result = spawnSync(
-      process.execPath,
-      [
-        path.join(fixture, 'scripts', 'gate-verify.mjs'),
-        '--root',
-        fixture,
-        '--manifest',
-        'gates/gates.manifest.json',
-        '--structure-only',
-      ],
-      { cwd: fixture, encoding: 'utf8' },
-    );
-    assert.notEqual(result.status, 0, 'shrinking baseline and manifest together must go red');
-    assert.match(output(result), /verifier inventory.*hook-pre-push.*baseline/i);
-  } finally {
-    await rm(fixture, { recursive: true, force: true });
-  }
-});
-
-test('every gate carries an evidence-side subject distinct from its definition', async () => {
-  const manifest = JSON.parse(await readFile(manifestPath, 'utf8'));
-  for (const gate of manifest.gates) {
-    assert.ok(gate.cases.length > 0, `${gate.id} must have consumable evidence`);
-    for (const gateCase of gate.cases) {
-      assert.equal(
-        gateCase.evidence?.subject,
-        gate.id,
-        `${gate.id}/${gateCase.id} must source its subject from the evidence record`,
-      );
-    }
-  }
-});
-
-test('inventory claim control rejects qualified independence wording', async () => {
-  const fixture = await mkdtemp(path.join(os.tmpdir(), 'rm02-inventory-overclaim-'));
-  const artifacts = [
-    'gates/required-gates.baseline.json',
-    'gates/gates.manifest.json',
-    'docs/PRD.md',
-    'docs/ADMIN-GUIDE/quality-gate-registry.md',
-    'docs/DEVELOPER-GUIDE/quality-gate-registry.md',
-    'docs/remediation/GATE-CLAIMS.md',
-    'docs/plans/2026-08-01-rm-02-gate-registry.md',
-    'docs/SITEMAP.md',
-  ];
-  try {
-    await mkdir(path.join(fixture, 'scripts'), { recursive: true });
-    await copyFile(
-      path.join(root, 'scripts', 'gate-inventory-claim-control.mjs'),
-      path.join(fixture, 'scripts', 'gate-inventory-claim-control.mjs'),
-    );
-    for (const relativePath of artifacts) {
-      const target = path.join(fixture, relativePath);
-      await mkdir(path.dirname(target), { recursive: true });
-      await copyFile(path.join(root, relativePath), target);
-    }
-    const prd = path.join(fixture, 'docs', 'PRD.md');
-    await writeFile(
-      prd,
-      `${await readFile(prd, 'utf8')}\nThis provides an independent seven-gate baseline comparison.\n`,
-    );
-    const result = spawnSync(
-      process.execPath,
-      [path.join(fixture, 'scripts', 'gate-inventory-claim-control.mjs')],
-      { cwd: fixture, encoding: 'utf8' },
-    );
-    assert.equal(result.status, 84, output(result));
-    assert.match(output(result), /INVENTORY_CLAIM_OVERSTATED.*docs\/PRD\.md/i);
-  } finally {
-    await rm(fixture, { recursive: true, force: true });
-  }
-});
-
-test('evidence population control depends on production result consumption wiring', async () => {
-  const fixture = await mkdtemp(path.join(os.tmpdir(), 'rm02-evidence-consumer-inert-'));
-  try {
-    await mkdir(path.join(fixture, 'scripts'), { recursive: true });
-    await mkdir(path.join(fixture, 'gates'), { recursive: true });
-    const verifier = await readFile(verifierPath, 'utf8');
-    const consumer = `        const subjectFailure = consumeEvidenceSubject(gate, result.evidence);\n        if (subjectFailure) failures.push(subjectFailure);\n`;
-    assert.equal(verifier.split(consumer).length - 1, 1, 'consumer fixture drifted');
-    await writeFile(
-      path.join(fixture, 'scripts', 'gate-verify.mjs'),
-      verifier.replace(consumer, ''),
-    );
-    await copyFile(
-      path.join(root, 'scripts', 'gate-population-control.mjs'),
-      path.join(fixture, 'scripts', 'gate-population-control.mjs'),
-    );
-    await copyFile(manifestPath, path.join(fixture, 'gates', 'gates.manifest.json'));
-    const result = spawnSync(
-      process.execPath,
-      [path.join(fixture, 'scripts', 'gate-population-control.mjs'), 'evidence-subject'],
-      { cwd: fixture, encoding: 'utf8' },
-    );
-    assert.equal(result.status, 0, output(result));
-    assert.match(output(result), /did not reject every registered gate/i);
-  } finally {
-    await rm(fixture, { recursive: true, force: true });
-  }
-});
-
-test('production verification has a closed current-tree observation renderer', async () => {
-  const verifier = await readFile(verifierPath, 'utf8');
-  assert.doesNotMatch(verifier, /from ['"]\.\/gate-history\.mjs['"]/);
-  assert.doesNotMatch(verifier, /\bverifyHistory\s*\(/);
-  assert.doesNotMatch(verifier, /history[-_ ]?provenance/i);
-  const attacks = [
-    [
-      'history wording',
-      '  /^META-NEGATIVE-CONTROL /,',
-      '  /^HISTORY PROVENANCE VERIFIED /,\n  /^META-NEGATIVE-CONTROL /,',
-    ],
-    [
-      'renamed ancestry wording',
-      '  /^META-NEGATIVE-CONTROL /,',
-      '  /^COMMIT ANCESTRY VERIFIED /,\n  /^META-NEGATIVE-CONTROL /,',
-    ],
-    [
-      'provider lineage wording',
-      '  /^META-NEGATIVE-CONTROL /,',
-      '  /^PROVIDER LINEAGE SUCCESS /,\n  /^META-NEGATIVE-CONTROL /,',
-    ],
-    ['writer assertion bypass', '  assertCurrentTreeObservation(output);\n', ''],
-    [
-      'final success stdout bypass',
-      '    writeCurrentTreeOutput(\n      `REGISTRY SUMMARY open behavior deltas: ${defects}; required-behavior conformance is not asserted while deltas remain`,\n    );',
-      "    process.stdout.write('COMMIT ANCESTRY VERIFIED\\n');",
-    ],
-    [
-      'direct success stderr bypass',
-      "    const defects = observations.filter((line) => line.startsWith('DEFECT ')).length;",
-      "    process.stderr.write('PROVIDER LINEAGE SUCCESS\\n');\n    const defects = observations.filter((line) => line.startsWith('DEFECT ')).length;",
-    ],
-  ];
-  for (const [name, find, replace] of attacks) {
-    const fixture = await mkdtemp(path.join(os.tmpdir(), 'rm02-history-renderer-'));
-    try {
-      await mkdir(path.join(fixture, 'scripts'), { recursive: true });
-      assert.equal(verifier.split(find).length - 1, 1, `${name}: fixture drifted`);
-      await writeFile(
-        path.join(fixture, 'scripts', 'gate-verify.mjs'),
-        verifier.replace(find, replace),
-      );
-      await copyFile(
-        path.join(root, 'scripts', 'gate-history-exclusion-control.mjs'),
-        path.join(fixture, 'scripts', 'gate-history-exclusion-control.mjs'),
-      );
-      const result = spawnSync(
-        process.execPath,
-        [path.join(fixture, 'scripts', 'gate-history-exclusion-control.mjs')],
-        { cwd: fixture, encoding: 'utf8' },
-      );
-      assert.equal(result.status, 79, `${name}: ${output(result)}`);
-      assert.match(output(result), /HISTORY_PROVENANCE_FORBIDDEN/);
-    } finally {
-      await rm(fixture, { recursive: true, force: true });
-    }
-  }
-});

scripts/gate-verify.test.mjs

@@ -1,785 +0,0 @@
-import assert from 'node:assert/strict';
-import { chmod, copyFile, mkdir, readFile, rm, symlink, writeFile } from 'node:fs/promises';
-import os from 'node:os';
-import path from 'node:path';
-import { spawnSync } from 'node:child_process';
-import test from 'node:test';
-
-const verifier = path.join(process.cwd(), 'scripts', 'gate-verify.mjs');
-const fixtureRunner = path.join(
-  process.cwd(),
-  'scripts',
-  'test-support',
-  'gate-verify-fixture-runner.mjs',
-);
-const fixtureBase = path.join(process.cwd(), '.mosaic-test-work', `gate-verify-${process.pid}`);
-
-async function fixture(name = 'case') {
-  const root = path.join(fixtureBase, name);
-  await rm(root, { recursive: true, force: true });
-  await mkdir(path.join(root, 'gates'), { recursive: true });
-  return root;
-}
-
-function baseManifest() {
-  return {
-    schemaVersion: 1,
-    gateRoots: ['gates'],
-    governingClaimFiles: [],
-    coverageBoundary: { included: ['meta fixture'], excluded: [], trackedBy: 'RM-54' },
-    criteria: [
-      {
-        id: 'META-CRIT-1',
-        originalText: 'The fixture rejects its bad input.',
-        currentText: 'The fixture rejects its bad input.',
-        claimType: 'integrity',
-        source: 'fixture',
-        meaningChanges: [],
-        caseRefs: ['meta-fixture/rejects-bad-input'],
-      },
-    ],
-    compatibilityScenarios: [],
-    proseClaims: [],
-    gates: [
-      {
-        id: 'meta-fixture',
-        source: 'gates/meta-fixture.sh',
-        invocation: ['gates/meta-fixture.sh'],
-        deployment: { kind: 'none', reason: 'test fixture only' },
-        inertMutation: {
-          file: 'gates/meta-fixture.sh',
-          find: 'exit 7',
-          replace: 'exit 0',
-          expected: { exitCode: 0 },
-        },
-        cases: [
-          {
-            id: 'rejects-bad-input',
-            criterionIds: ['META-CRIT-1'],
-            mustFail: true,
-            invocation: ['gates/meta-fixture.sh'],
-            required: { exitCode: 7 },
-            actual: { exitCode: 7 },
-            evidence: { subject: 'meta-fixture' },
-            reasonPattern: 'META_REJECT',
-          },
-        ],
-      },
-    ],
-  };
-}
-
-async function writeGate(root, contents = '#!/bin/sh\necho META_REJECT >&2\nexit 7\n') {
-  const target = path.join(root, 'gates', 'meta-fixture.sh');
-  await writeFile(target, contents);
-  await chmod(target, 0o755);
-}
-
-async function writeManifest(root, manifest) {
-  await writeFile(path.join(root, 'gates', 'gates.manifest.json'), `${JSON.stringify(manifest)}\n`);
-}
-
-function verify(root, extraArgs = []) {
-  return spawnSync(
-    process.execPath,
-    [fixtureRunner, '--root', root, '--manifest', 'gates/gates.manifest.json', ...extraArgs],
-    { cwd: root, encoding: 'utf8', env: { ...process.env, HOME: os.homedir() } },
-  );
-}
-
-function verifyProductionStructure(root, extraArgs = []) {
-  return spawnSync(
-    process.execPath,
-    [
-      verifier,
-      '--root',
-      root,
-      '--manifest',
-      'gates/gates.manifest.json',
-      '--structure-only',
-      ...extraArgs,
-    ],
-    { cwd: root, encoding: 'utf8', env: { ...process.env, HOME: os.homedir() } },
-  );
-}
-
-function output(result) {
-  return `${result.stdout}\n${result.stderr}`;
-}
-
-test.after(async () => {
-  await rm(fixtureBase, { recursive: true, force: true });
-});
-
-test('universally quantified registry checks reject empty populations before evaluation', async () => {
-  const root = await fixture('empty-registry-populations');
-  await mkdir(path.join(root, 'empty-gate-root'), { recursive: true });
-  const manifest = baseManifest();
-  manifest.gateRoots = ['empty-gate-root'];
-  manifest.criteria = [];
-  manifest.proseClaims = [];
-  manifest.compatibilityScenarios = [];
-  manifest.gates = [];
-  await writeManifest(root, manifest);
-
-  const result = verifyProductionStructure(root);
-  assert.notEqual(result.status, 0);
-  assert.match(output(result), /criteria population.*non-empty.*anchored/i);
-  assert.match(output(result), /gates population.*non-empty.*anchored/i);
-  assert.match(output(result), /proseClaims population.*non-empty.*anchored/i);
-  assert.match(output(result), /compatibilityScenarios population.*non-empty.*anchored/i);
-});
-
-test('production verifier exposes no fixture-profile population bypass', async () => {
-  const root = await fixture('no-production-fixture-profile');
-  const result = verifyProductionStructure(root, ['--fixture-profile']);
-  assert.notEqual(result.status, 0);
-  assert.match(output(result), /unknown option: --fixture-profile/i);
-});
-
-test('anchored gate inventory and population criteria cannot shrink together', async () => {
-  const source = JSON.parse(
-    await readFile(path.join(process.cwd(), 'gates', 'gates.manifest.json'), 'utf8'),
-  );
-  const root = await fixture('shrunken-gate-population');
-  await copyFile(
-    path.join(process.cwd(), 'gates', 'required-gates.baseline.json'),
-    path.join(root, 'gates', 'required-gates.baseline.json'),
-  );
-  source.gates = source.gates.filter((gate) => gate.id !== 'hook-pre-push');
-  for (const criterion of source.criteria) {
-    if (criterion.gateRefs) {
-      criterion.gateRefs = criterion.gateRefs.filter((gateId) => gateId !== 'hook-pre-push');
-    }
-    criterion.caseRefs = criterion.caseRefs.filter(
-      (caseRef) => !caseRef.startsWith('hook-pre-push/'),
-    );
-  }
-  await writeManifest(root, source);
-
-  const result = verifyProductionStructure(root);
-  assert.notEqual(result.status, 0);
-  assert.match(
-    output(result),
-    /same-checkout required-gate baseline rejects manifest drift at hook-pre-push/i,
-  );
-});
-
-test('general population criteria cannot delete their gateRefs binding', async () => {
-  const requiredCriteria = [
-    'RM02-EVIDENCE-SUBJECT-BINDING',
-    'RM02-TYPE-STRICT-SCHEMA',
-    'RM02-NONEMPTY-ANCHORED-QUANTIFICATION',
-  ];
-  for (const criterionId of requiredCriteria) {
-    const source = JSON.parse(
-      await readFile(path.join(process.cwd(), 'gates', 'gates.manifest.json'), 'utf8'),
-    );
-    const root = await fixture(`missing-gate-refs-${criterionId}`);
-    delete source.criteria.find((criterion) => criterion.id === criterionId).gateRefs;
-    await writeManifest(root, source);
-    const result = verifyProductionStructure(root);
-    assert.notEqual(result.status, 0);
-    assert.match(
-      output(result),
-      new RegExp(`${criterionId}.*gateRefs.*required`, 'i'),
-      criterionId,
-    );
-  }
-});
-
-test('general population criteria must span every registered gate', async () => {
-  const source = JSON.parse(
-    await readFile(path.join(process.cwd(), 'gates', 'gates.manifest.json'), 'utf8'),
-  );
-  const root = await fixture('incomplete-gate-refs');
-  source.criteria.find((criterion) => criterion.id === 'RM02-EVIDENCE-SUBJECT-BINDING').gateRefs =
-    source.criteria
-      .find((criterion) => criterion.id === 'RM02-EVIDENCE-SUBJECT-BINDING')
-      .gateRefs.filter((gateId) => gateId !== 'quality-lint');
-  await writeManifest(root, source);
-
-  const result = verifyProductionStructure(root);
-  assert.notEqual(result.status, 0);
-  assert.match(
-    output(result),
-    /RM02-EVIDENCE-SUBJECT-BINDING.*gate population binding is missing quality-lint/i,
-  );
-});
-
-test('an externally inerted failure branch makes verification nonzero and names the gate', async () => {
-  const root = await fixture('external-inert');
-  await writeGate(root, '#!/bin/sh\nexit 0\n');
-  await writeManifest(root, baseManifest());
-
-  const result = verify(root);
-  assert.notEqual(result.status, 0);
-  assert.match(output(result), /meta-fixture/);
-});
-
-test('the verifier applies the declared inert mutation and observes its own control red', async () => {
-  const root = await fixture('internal-meta');
-  await writeGate(root);
-  await writeManifest(root, baseManifest());
-
-  const result = verify(root);
-  assert.equal(result.status, 0, output(result));
-  assert.match(output(result), /META-NEGATIVE-CONTROL.*meta-fixture.*observed red/i);
-});
-
-test('a mutation crash is rejected instead of counted as an observed-red control', async () => {
-  const root = await fixture('mutation-crash');
-  await writeGate(root);
-  const manifest = baseManifest();
-  manifest.gates[0].inertMutation.replace = 'this is not valid shell (';
-  manifest.gates[0].inertMutation.expected = { exitCode: 0 };
-  await writeManifest(root, manifest);
-
-  const result = verify(root);
-  assert.notEqual(result.status, 0);
-  assert.match(output(result), /meta-fixture.*mutation.*unexpected outcome/i);
-  assert.doesNotMatch(output(result), /META-NEGATIVE-CONTROL.*observed red/i);
-});
-
-test('a stale declared mutation case id is rejected instead of falling back', async () => {
-  const root = await fixture('stale-case-id');
-  await writeGate(root);
-  const manifest = baseManifest();
-  manifest.gates[0].inertMutation.caseId = 'case-that-does-not-exist';
-  await writeManifest(root, manifest);
-
-  const result = verify(root);
-  assert.notEqual(result.status, 0);
-  assert.match(output(result), /meta-fixture.*case-that-does-not-exist.*not found/i);
-});
-
-test('duplicate stable ids and unsupported schema versions are rejected', async () => {
-  const root = await fixture('closed-schema');
-  await writeGate(root);
-  const manifest = baseManifest();
-  manifest.schemaVersion = 99;
-  manifest.criteria.push({ ...manifest.criteria[0] });
-  await writeManifest(root, manifest);
-
-  const result = verify(root);
-  assert.notEqual(result.status, 0);
-  assert.match(output(result), /unsupported schemaVersion 99/i);
-  assert.match(output(result), /duplicate criterion id META-CRIT-1/i);
-});
-
-test('misspelled nested assertion fields are rejected instead of becoming optional', async () => {
-  const root = await fixture('nested-schema-typo');
-  await writeGate(root);
-  const manifest = baseManifest();
-  manifest.gates[0].cases[0].required.outputPatern = 'META_REJECT';
-  manifest.gates[0].cases[0].actual.outputPatern = 'META_REJECT';
-  await writeManifest(root, manifest);
-
-  const result = verify(root);
-  assert.notEqual(result.status, 0);
-  assert.match(output(result), /required.*unknown field outputPatern/i);
-  assert.match(output(result), /actual.*unknown field outputPatern/i);
-});
-
-test('present outcome patterns cannot be empty assertion bypasses', async () => {
-  const root = await fixture('nested-schema-empty-patterns');
-  await writeGate(root);
-  const manifest = baseManifest();
-  manifest.gates[0].cases[0].required.outputPattern = '';
-  manifest.gates[0].cases[0].actual.notOutputPattern = '   ';
-  await writeManifest(root, manifest);
-
-  const result = verify(root, ['--structure-only']);
-  assert.notEqual(result.status, 0);
-  assert.match(output(result), /required.outputPattern: expected a non-empty pattern/i);
-  assert.match(output(result), /actual.notOutputPattern: expected a non-empty pattern/i);
-});
-
-test('nested discriminator and comparison fields reject wrong types', async () => {
-  const root = await fixture('nested-schema-types');
-  await writeGate(root);
-  const manifest = baseManifest();
-  manifest.gates[0].cases[0].mustFail = 'true';
-  manifest.gates[0].cases[0].required.exitCode = '7';
-  manifest.gates[0].cases[0].actual.outputPattern = 7;
-  await writeManifest(root, manifest);
-
-  const result = verify(root, ['--structure-only']);
-  assert.notEqual(result.status, 0);
-  assert.match(output(result), /mustFail: expected a boolean/i);
-  assert.match(output(result), /required.exitCode: expected an integer/i);
-  assert.match(output(result), /actual.outputPattern: expected a string/i);
-});
-
-test('recursive closed-schema guards reject unknown fields in every nested assertion object', async () => {
-  const source = JSON.parse(
-    await readFile(path.join(process.cwd(), 'gates', 'gates.manifest.json'), 'utf8'),
-  );
-  const checkout = source.gates.find((gate) => gate.id === 'checkout-preflight');
-  const stale = checkout.cases.find((gateCase) => gateCase.id === 'stale-build-lock');
-  const queue = source.gates.find((gate) => gate.id === 'ci-queue-wait');
-  const queueCase = queue.cases.find((gateCase) => gateCase.id === 'terminal-success');
-  const targets = [
-    ['coverageBoundary', (manifest) => manifest.coverageBoundary],
-    ['mergeAssertions', (manifest) => manifest.mergeAssertions],
-    [
-      'meaningChanges',
-      (manifest) =>
-        manifest.criteria.find((criterion) => criterion.meaningChanges.length).meaningChanges[0],
-    ],
-    ['proseClaims', (manifest) => manifest.proseClaims[0]],
-    ['compatibility expected', (manifest) => manifest.compatibilityScenarios[0].expected],
-    [
-      'deployment',
-      (manifest) => manifest.gates.find((gate) => gate.id === 'ci-queue-wait').deployment,
-    ],
-    ['inertMutation', (manifest) => manifest.gates[0].inertMutation],
-    ['inert expected', (manifest) => manifest.gates[0].inertMutation.expected],
-    ['required', (manifest) => manifest.gates[0].cases[0].required],
-    ['actual', (manifest) => manifest.gates[0].cases[0].actual],
-    [
-      'fixture',
-      (manifest) =>
-        manifest.gates
-          .find((gate) => gate.id === 'checkout-preflight')
-          .cases.find((gateCase) => gateCase.id === 'stale-build-lock').fixture,
-    ],
-    [
-      'write entry',
-      (manifest) =>
-        manifest.gates
-          .find((gate) => gate.id === 'checkout-preflight')
-          .cases.find((gateCase) => gateCase.id === 'stale-build-lock').fixture.writeFiles[0],
-    ],
-    [
-      'replace entry',
-      (manifest) =>
-        manifest.gates
-          .find((gate) => gate.id === 'checkout-preflight')
-          .cases.find((gateCase) => gateCase.id === 'criterion-misbinding').fixture.replaceFiles[0],
-    ],
-    [
-      'defect',
-      (manifest) =>
-        manifest.gates
-          .find((gate) => gate.id === 'ci-queue-wait')
-          .cases.find((gateCase) => gateCase.id === 'terminal-success').defect,
-    ],
-  ];
-  assert.ok(stale.fixture && queueCase.defect);
-  for (const [name, select] of targets) {
-    const root = await fixture(`recursive-${name.replaceAll(' ', '-')}`);
-    const manifest = structuredClone(source);
-    select(manifest).unexpectedNestedField = true;
-    await writeManifest(root, manifest);
-    const result = verify(root, ['--structure-only']);
-    assert.notEqual(result.status, 0, `${name}: ${output(result)}`);
-    assert.match(output(result), /unknown field unexpectedNestedField/i, name);
-  }
-});
-
-test('manifest-controlled fixture paths cannot escape the sandbox', async () => {
-  const root = await fixture('path-traversal');
-  await writeGate(root);
-  const manifest = baseManifest();
-  manifest.gates[0].cases[0].fixture = {
-    writeFiles: [{ path: '../../escaped-by-manifest', content: 'bad' }],
-  };
-  await writeManifest(root, manifest);
-
-  const result = verify(root);
-  assert.notEqual(result.status, 0);
-  assert.match(output(result), /path escapes sandbox/i);
-});
-
-test('fixture writes reject a final symlink and preserve its outside target', async () => {
-  const root = await fixture('final-symlink');
-  await writeGate(root);
-  const outside = path.join(fixtureBase, 'outside-sentinel');
-  await writeFile(outside, 'preserve-me\n');
-  const linked = path.join(root, 'linked-sentinel');
-  await symlink(outside, linked);
-  const manifest = baseManifest();
-  manifest.gates[0].cases[0].fixture = {
-    writeFiles: [{ path: 'linked-sentinel', content: 'overwritten\n' }],
-  };
-  await writeManifest(root, manifest);
-
-  const result = verify(root);
-  assert.notEqual(result.status, 0);
-  assert.match(output(result), /fixture write.*symbolic link/i);
-  assert.equal(await readFile(outside, 'utf8'), 'preserve-me\n');
-});
-
-test('an executable below a gate root without an entry is rejected', async () => {
-  const root = await fixture('unregistered');
-  await writeGate(root);
-  const extra = path.join(root, 'gates', 'forgotten.sh');
-  await writeFile(extra, '#!/bin/sh\nexit 1\n');
-  await chmod(extra, 0o755);
-  await writeManifest(root, baseManifest());
-
-  const result = verify(root);
-  assert.notEqual(result.status, 0);
-  assert.match(output(result), /unregistered gate.*forgotten\.sh/i);
-});
-
-test('a must-fail case without a reason diagnostic is rejected', async () => {
-  const root = await fixture('missing-reason');
-  await writeGate(root);
-  const manifest = baseManifest();
-  manifest.gates[0].cases[0].reasonPattern = '';
-  await writeManifest(root, manifest);
-
-  const result = verify(root);
-  assert.notEqual(result.status, 0);
-  assert.match(output(result), /meta-fixture.*rejects-bad-input.*reasonPattern/i);
-});
-
-test('a gate with zero must-fail cases is rejected', async () => {
-  const root = await fixture('no-negative');
-  await writeGate(root, '#!/bin/sh\nexit 0\n');
-  const manifest = baseManifest();
-  manifest.gates[0].inertMutation = {
-    file: 'gates/meta-fixture.sh',
-    find: 'exit 0',
-    replace: 'exit 1',
-  };
-  manifest.gates[0].cases = [
-    {
-      id: 'positive',
-      criterionIds: ['META-CRIT-1'],
-      mustFail: false,
-      invocation: ['gates/meta-fixture.sh'],
-      required: { exitCode: 0 },
-      actual: { exitCode: 0 },
-      reasonPattern: '',
-    },
-  ];
-  await writeManifest(root, manifest);
-
-  const result = verify(root);
-  assert.notEqual(result.status, 0);
-  assert.match(output(result), /meta-fixture.*no negative control/i);
-});
-
-test('reordered but equivalent outcome fields do not create a false behavior delta', async () => {
-  const root = await fixture('reordered-outcomes');
-  await writeGate(root);
-  const manifest = baseManifest();
-  manifest.gates[0].cases[0].required = { exitCode: 7, outputPattern: 'META_REJECT' };
-  manifest.gates[0].cases[0].actual = { outputPattern: 'META_REJECT', exitCode: 7 };
-  await writeManifest(root, manifest);
-
-  const result = verify(root);
-  assert.equal(result.status, 0, output(result));
-  assert.doesNotMatch(output(result), /behavior delta requires|DEFECT \(owner:/);
-});
-
-test('a required-versus-actual delta without a tracked owner is rejected', async () => {
-  const root = await fixture('ownerless-delta');
-  await writeGate(root, '#!/bin/sh\nexit 0\n');
-  const manifest = baseManifest();
-  manifest.gates[0].inertMutation.find = 'exit 0';
-  manifest.gates[0].inertMutation.replace = 'exit 7';
-  manifest.gates[0].cases[0].actual.exitCode = 0;
-  await writeManifest(root, manifest);
-
-  const result = verify(root);
-  assert.notEqual(result.status, 0);
-  assert.match(output(result), /meta-fixture.*delta.*tracked owner/i);
-});
-
-test('moving criterion bindings to unrelated cases is rejected', async () => {
-  const root = await fixture('semantic-misbinding');
-  await writeGate(root);
-  const manifest = baseManifest();
-  manifest.criteria.push({
-    id: 'META-CRIT-2',
-    originalText: 'The fixture reports the second rejection reason.',
-    currentText: 'The fixture reports the second rejection reason.',
-    claimType: 'integrity',
-    source: 'fixture',
-    meaningChanges: [],
-    caseRefs: ['meta-fixture/rejects-second-input'],
-  });
-  manifest.gates[0].cases.push({
-    ...manifest.gates[0].cases[0],
-    id: 'rejects-second-input',
-    criterionIds: ['META-CRIT-1'],
-  });
-  manifest.gates[0].cases[0].criterionIds = ['META-CRIT-2'];
-  await writeManifest(root, manifest);
-
-  const result = verify(root);
-  assert.notEqual(result.status, 0);
-  assert.match(output(result), /META-CRIT-1.*rejects-bad-input.*not bound/i);
-  assert.match(output(result), /META-CRIT-2.*rejects-second-input.*not bound/i);
-});
-
-test('canonical verification preserves binding diagnostics when a case fixture is also stale', async () => {
-  const root = await fixture('misbinding-plus-stale-fixture');
-  await writeGate(root);
-  const manifest = baseManifest();
-  manifest.criteria.push({
-    id: 'META-CRIT-2',
-    originalText: 'The second case rejects its own bad input.',
-    currentText: 'The second case rejects its own bad input.',
-    claimType: 'integrity',
-    source: 'fixture',
-    meaningChanges: [],
-    caseRefs: ['meta-fixture/rejects-second-input'],
-  });
-  manifest.gates[0].cases.push({
-    ...manifest.gates[0].cases[0],
-    id: 'rejects-second-input',
-    criterionIds: ['META-CRIT-1'],
-  });
-  manifest.gates[0].cases[0].criterionIds = ['META-CRIT-2'];
-  manifest.gates[0].cases[0].fixture = {
-    replaceFiles: [
-      {
-        path: 'gates/meta-fixture.sh',
-        find: 'text that is not present',
-        replace: 'irrelevant',
-      },
-    ],
-  };
-  await writeManifest(root, manifest);
-
-  const result = verify(root);
-  assert.notEqual(result.status, 0);
-  assert.match(output(result), /META-CRIT-1.*rejects-bad-input.*not bound/i);
-  assert.match(output(result), /META-CRIT-2.*rejects-second-input.*not bound/i);
-  assert.match(output(result), /fixture replace.*stale or ambiguous/i);
-});
-
-test('moving meaning and prose criteria to an unrelated type error is rejected', async () => {
-  const root = await fixture('real-manifest-misbinding');
-  const manifest = JSON.parse(
-    await readFile(path.join(process.cwd(), 'gates', 'gates.manifest.json'), 'utf8'),
-  );
-  for (const gate of manifest.gates) {
-    for (const gateCase of gate.cases) {
-      gateCase.criterionIds = gateCase.criterionIds.filter(
-        (id) => !['RM02-MEANING-PROVENANCE', 'RM02-PROSE-CONTROL'].includes(id),
-      );
-    }
-  }
-  const typeError = manifest.gates
-    .find((gate) => gate.id === 'quality-typecheck')
-    .cases.find((gateCase) => gateCase.id === 'type-error');
-  typeError.criterionIds.push('RM02-MEANING-PROVENANCE', 'RM02-PROSE-CONTROL');
-  await writeManifest(root, manifest);
-
-  const result = verify(root, ['--structure-only']);
-  assert.notEqual(result.status, 0);
-  assert.match(output(result), /RM02-MEANING-PROVENANCE.*missing-meaning-provenance.*not bound/i);
-  assert.match(output(result), /RM02-PROSE-CONTROL.*prose-claim-misbinding.*not bound/i);
-  assert.match(
-    output(result),
-    /RM02-(?:MEANING-PROVENANCE|PROSE-CONTROL).*undeclared exercising case quality-typecheck\/type-error/i,
-  );
-});
-
-test('a criterion with no bound case is rejected', async () => {
-  const root = await fixture('unbound-criterion');
-  await writeGate(root);
-  const manifest = baseManifest();
-  manifest.criteria.push({
-    id: 'ORPHAN',
-    originalText: 'This criterion is not exercised.',
-    currentText: 'This criterion is not exercised.',
-    claimType: 'quality',
-    source: 'fixture',
-    meaningChanges: [],
-  });
-  await writeManifest(root, manifest);
-
-  const result = verify(root);
-  assert.notEqual(result.status, 0);
-  assert.match(output(result), /ORPHAN.*no bound case/i);
-});
-
-test('an unbound governing prose marker is rejected', async () => {
-  const root = await fixture('unbound-prose');
-  await writeGate(root);
-  await mkdir(path.join(root, 'docs'), { recursive: true });
-  await writeFile(path.join(root, 'docs', 'governing.md'), 'GATE-CLAIM:UNBOUND\n');
-  const manifest = baseManifest();
-  manifest.governingClaimFiles = ['docs/governing.md'];
-  await writeManifest(root, manifest);
-
-  const result = verify(root);
-  assert.notEqual(result.status, 0);
-  assert.match(output(result), /GATE-CLAIM:UNBOUND.*unbound/i);
-});
-
-test('directly contradictory modeled scenarios are rejected', async () => {
-  const root = await fixture('conflict');
-  await writeGate(root);
-  const manifest = baseManifest();
-  manifest.compatibilityScenarios = [
-    {
-      id: 'ONE',
-      construction: 'same-input',
-      caseRefs: ['meta-fixture/rejects-bad-input'],
-      invocation: ['sh', '-c', 'exit 0'],
-      expected: { exitCode: 0 },
-    },
-    {
-      id: 'TWO',
-      construction: 'same-input',
-      caseRefs: ['meta-fixture/rejects-bad-input'],
-      invocation: ['sh', '-c', 'exit 1'],
-      expected: { exitCode: 1 },
-    },
-  ];
-  await writeManifest(root, manifest);
-
-  const result = verify(root);
-  assert.notEqual(result.status, 0);
-  assert.match(output(result), /ONE.*TWO.*conflict/i);
-});
-
-test('compatibility scenarios execute referenced conditions as one construction', async () => {
-  const root = await fixture('combined-compatibility');
-  await writeGate(root);
-  const manifest = baseManifest();
-  manifest.gates[0].cases.push({
-    id: 'second-condition',
-    criterionIds: ['META-CRIT-1'],
-    mustFail: true,
-    invocation: ['sh', '-c', 'echo "$SECOND_REASON" >&2; exit 7'],
-    fixture: { writeFiles: [{ path: 'conditions/second', content: 'present\n' }] },
-    required: { exitCode: 7 },
-    actual: { exitCode: 7 },
-    evidence: { subject: 'meta-fixture' },
-    reasonPattern: 'SECOND_REASON',
-    environment: { SECOND_REASON: 'SECOND_REASON' },
-  });
-  manifest.criteria[0].caseRefs.push('meta-fixture/second-condition');
-  manifest.gates[0].cases[0].fixture = {
-    writeFiles: [{ path: 'conditions/first', content: 'present\n' }],
-  };
-  manifest.compatibilityScenarios = [
-    {
-      id: 'BOTH-CONDITIONS',
-      construction: 'both-fixtures',
-      caseRefs: ['meta-fixture/rejects-bad-input', 'meta-fixture/second-condition'],
-      invocation: ['sh', '-c', 'test -f conditions/first && test -f conditions/second'],
-      expected: { exitCode: 0 },
-    },
-  ];
-  await writeManifest(root, manifest);
-
-  const result = verify(root);
-  assert.equal(result.status, 0, output(result));
-  assert.match(output(result), /COMPATIBILITY BOTH-CONDITIONS: observed expected outcome/i);
-});
-
-test('a restated criterion without provenance is rejected', async () => {
-  const root = await fixture('provenance');
-  await writeGate(root);
-  const manifest = baseManifest();
-  manifest.criteria[0].currentText = 'The fixture rejects only malformed input.';
-  await writeManifest(root, manifest);
-
-  const result = verify(root);
-  assert.notEqual(result.status, 0);
-  assert.match(output(result), /META-CRIT-1.*meaning-change provenance/i);
-});
-
-test('a security criterion bound only to a positive case is unregistered in substance', async () => {
-  const root = await fixture('positive-only-criterion');
-  await writeGate(root);
-  const manifest = baseManifest();
-  manifest.criteria.push({
-    id: 'POSITIVE-ONLY',
-    originalText: 'A security property.',
-    currentText: 'A security property.',
-    claimType: 'security',
-    source: 'fixture',
-    meaningChanges: [],
-  });
-  manifest.gates[0].cases.push({
-    id: 'positive-only',
-    criterionIds: ['POSITIVE-ONLY'],
-    mustFail: false,
-    invocation: ['gates/meta-fixture.sh'],
-    required: { exitCode: 7 },
-    actual: { exitCode: 7 },
-    reasonPattern: '',
-  });
-  await writeManifest(root, manifest);
-
-  const result = verify(root);
-  assert.notEqual(result.status, 0);
-  assert.match(output(result), /POSITIVE-ONLY.*no must-fail case/i);
-});
-
-test('a registered prose claim whose marker is absent is rejected', async () => {
-  const root = await fixture('missing-prose-marker');
-  await writeGate(root);
-  await mkdir(path.join(root, 'docs'), { recursive: true });
-  await writeFile(path.join(root, 'docs', 'governing.md'), 'No marker here.\n');
-  const manifest = baseManifest();
-  manifest.governingClaimFiles = ['docs/governing.md'];
-  manifest.proseClaims = [{ id: 'MISSING-MARKER', criterionId: 'META-CRIT-1' }];
-  await writeManifest(root, manifest);
-
-  const result = verify(root);
-  assert.notEqual(result.status, 0);
-  assert.match(output(result), /GATE-CLAIM:MISSING-MARKER.*missing/i);
-});
-
-test('source-versus-deployed byte drift is rejected and names the gate', async () => {
-  const root = await fixture('deployment-drift');
-  await writeGate(root);
-  await mkdir(path.join(root, 'deployed'), { recursive: true });
-  await writeFile(path.join(root, 'deployed', 'meta-fixture.sh'), '#!/bin/sh\nexit 0\n');
-  const manifest = baseManifest();
-  manifest.gates[0].deployment = { kind: 'file', path: 'deployed/meta-fixture.sh' };
-  await writeManifest(root, manifest);
-
-  const result = verify(root);
-  assert.notEqual(result.status, 0);
-  assert.match(output(result), /meta-fixture.*source.*deployed.*drift/i);
-});
-
-test('deployment drift meta-control fails if the shared comparator is made inert', async () => {
-  const root = await fixture('deployment-comparator-inert');
-  await writeGate(root);
-  await mkdir(path.join(root, 'deployed'), { recursive: true });
-  await copyFile(
-    path.join(root, 'gates', 'meta-fixture.sh'),
-    path.join(root, 'deployed', 'meta-fixture.sh'),
-  );
-  const manifest = baseManifest();
-  manifest.gates[0].deployment = { kind: 'file', path: 'deployed/meta-fixture.sh' };
-  await writeManifest(root, manifest);
-
-  const alteredScripts = path.join(root, 'verifier-scripts');
-  await mkdir(alteredScripts, { recursive: true });
-  const verifierSource = await readFile(verifier, 'utf8');
-  const inertSource = verifierSource.replace(
-    'return source.equals(deployed);',
-    'return true; // deliberate test-only inert comparator',
-  );
-  assert.notEqual(inertSource, verifierSource, 'shared deployment comparator mutation went stale');
-  await writeFile(path.join(alteredScripts, 'gate-verify.mjs'), inertSource);
-
-  const result = spawnSync(
-    process.execPath,
-    [
-      path.join(alteredScripts, 'gate-verify.mjs'),
-      '--root',
-      root,
-      '--manifest',
-      'gates/gates.manifest.json',
-    ],
-    { cwd: root, encoding: 'utf8', env: { ...process.env, HOME: os.homedir() } },
-  );
-  assert.notEqual(result.status, 0);
-  assert.match(output(result), /meta-fixture.*drift negative control was ineffective/i);
-});

scripts/gate-wiring.test.mjs

@@ -1,104 +0,0 @@
-import assert from 'node:assert/strict';
-import { readFile } from 'node:fs/promises';
-import test from 'node:test';
-
-const root = process.cwd();
-const expectedTriggers = `when:
-  # PR + manual CI run on any branch — the pull_request pipeline is the merge gate.
-  # push CI is restricted to protected branches (main) so a feature-branch push no
-  # longer fires a redundant SECOND pipeline alongside its PR pipeline. This ~halves
-  # CI load on the storage-constrained runner with zero loss of gating (branch
-  # protection requires no push/ci status context; main still gets full push CI).
-  - event: [pull_request, manual]
-  - event: push
-    branch: main`;
-const expectedGateStep = `    image: *node_image
-    commands:
-      - *enable_pnpm
-      - pnpm gate:verify
-    depends_on:
-      - install
-      - sanitization
-      - upgrade-guard`;
-
-export function assertUnprivilegedGateStep(pipeline) {
-  assert.doesNotMatch(
-    pipeline,
-    /privileged/i,
-    'no pull-request pipeline step may declare privilege',
-  );
-  for (const line of pipeline.split('\n')) {
-    const candidate = line.trimStart().replace(/^-\s+/, '');
-    if (/^(?:["'!<].*|[A-Za-z_][A-Za-z0-9_-]*\s+):(?:\s|$)/.test(candidate)) {
-      assert.fail(`non-canonical or merged YAML key is forbidden: ${candidate}`);
-    }
-  }
-  const triggerMatches = [...pipeline.matchAll(/^when:\n([\s\S]*?)(?=\n\n)/gm)];
-  assert.equal(triggerMatches.length, 1, 'exactly one top-level trigger is required');
-  assert.equal(
-    `when:\n${triggerMatches[0][1].trimEnd()}`,
-    expectedTriggers,
-    'top-level triggers must match closed PR/main construction',
-  );
-
-  const matches = [
-    ...pipeline.matchAll(/\n  gate-verify:\n([\s\S]*?)(?=\n  [a-z][a-z0-9-]+:|\nservices:|$)/g),
-  ];
-  assert.equal(matches.length, 1, 'exactly one gate-verify step is required');
-  // Closed textual construction by design: accepting arbitrary YAML syntax here
-  // would require a duplicate-key-preserving parser. Exact equality rejects all
-  // extra keys, quoted/escaped key spellings, aliases, and mapping merges.
-  assert.equal(
-    matches[0][1].trimEnd(),
-    expectedGateStep,
-    'gate-verify step must match closed unprivileged construction',
-  );
-}
-
-test('package.json exposes the canonical gate:verify command', async () => {
-  const packageJson = JSON.parse(await readFile(`${root}/package.json`, 'utf8'));
-  assert.equal(packageJson.scripts['gate:verify'], 'node scripts/gate-verify.mjs');
-});
-
-test('Woodpecker runs the closed unprivileged gate construction on every pipeline', async () => {
-  const pipeline = await readFile(`${root}/.woodpecker/ci.yml`, 'utf8');
-  assertUnprivilegedGateStep(pipeline);
-});
-
-test('gate wiring rejects privilege syntax, merges, duplicate keys, and trigger narrowing', async () => {
-  const pipeline = await readFile(`${root}/.woodpecker/ci.yml`, 'utf8');
-  const additions = [
-    '    privileged: *enabled\n',
-    '    "privileged": true\n',
-    "    'privileged': true\n",
-    '    privileged : true\n',
-    '    "priv\\u0069leged": true\n',
-    '    <<: *privileged-step\n',
-    '    "<<": *privileged-step\n',
-  ];
-  for (const addition of additions) {
-    const changed = pipeline.replace(
-      '  gate-verify:\n    image:',
-      `  gate-verify:\n${addition}    image:`,
-    );
-    assert.throws(() => assertUnprivilegedGateStep(changed));
-  }
-  const privilegedInstall = pipeline.replace(
-    '  install:\n    image:',
-    '  install:\n    privileged: true\n    image:',
-  );
-  const duplicate = `${pipeline}\n  gate-verify:\n    image: *node_image\n`;
-  const noPullRequest = pipeline.replace('  - event: [pull_request, manual]', '  - event: manual');
-  const filteredPullRequest = pipeline.replace(
-    '  - event: [pull_request, manual]',
-    '  - event: [pull_request, manual]\n    path: [scripts/**]',
-  );
-
-  assert.throws(() => assertUnprivilegedGateStep(privilegedInstall), /privilege/i);
-  assert.throws(() => assertUnprivilegedGateStep(duplicate), /exactly one gate-verify/);
-  assert.throws(() => assertUnprivilegedGateStep(noPullRequest), /closed PR\/main construction/);
-  assert.throws(
-    () => assertUnprivilegedGateStep(filteredPullRequest),
-    /closed PR\/main construction/,
-  );
-});

scripts/test-support/gate-verify-fixture-runner.mjs

@@ -1,27 +0,0 @@
-#!/usr/bin/env node
-
-import path from 'node:path';
-
-import { verifyRegistry } from '../gate-verify.mjs';
-
-let root;
-let manifest = 'gates/gates.manifest.json';
-let structureOnly = false;
-for (let index = 0; index < process.argv.slice(2).length; index += 1) {
-  const args = process.argv.slice(2);
-  const value = args[index];
-  if (value === '--root') root = path.resolve(args[++index]);
-  else if (value === '--manifest') manifest = args[++index];
-  else if (value === '--structure-only') structureOnly = true;
-  else throw new Error(`unknown fixture-runner option: ${value}`);
-}
-if (!root) throw new Error('fixture runner requires --root');
-const { failures, observations } = await verifyRegistry({
-  root,
-  manifest,
-  structureOnly,
-  fixtureProfile: true,
-});
-for (const observation of observations) process.stdout.write(`${observation}\n`);
-for (const failure of failures) process.stderr.write(`GATE VERIFY FAILED: ${failure}\n`);
-if (failures.length > 0) process.exitCode = 1;