.github/ci/push-main-unit-reuse-selftest.py:17:    "unit_reuse", Path(__file__).with_name("push-main-unit-reuse.py"))
.github/ci/push-main-unit-reuse-selftest.py:56:# [unit->REQ-CI-PUSH-MAIN-UNIT-REUSE]
.github/ci/push-main-unit-reuse-selftest.py:87:            self.assertEqual(output.read_text(), f"run-unit={str(run_unit).lower()}\n")
.github/ci/push-main-unit-reuse.py:2:"""Reuse exact-SHA PR unit evidence; uncertainty always requests fresh units."""
.github/ci/push-main-unit-reuse.py:110:# [impl->REQ-CI-PUSH-MAIN-UNIT-REUSE]
.github/ci/push-main-unit-reuse.py:177:    print(f"UNIT_REUSE run-unit={value} reason={reason}")
.github/ci/push-main-unit-reuse.py:181:            stream.write(f"run-unit={value}\n")
.github/ci/reaper-breadcrumb-census.ps1:47:    # flow — the exact shape the fix spec's file list was drawn from).
.github/workflows/ci.yml:26:      run-unit: ${{ steps.reuse.outputs.run-unit || 'true' }}
.github/workflows/ci.yml:64:      - name: Self-test push-main unit reuse
.github/workflows/ci.yml:65:        run: python3 .github/ci/push-main-unit-reuse-selftest.py
.github/workflows/ci.yml:66:      # [impl->REQ-CI-PUSH-MAIN-UNIT-REUSE]
.github/workflows/ci.yml:73:          if ! python3 .github/ci/push-main-unit-reuse.py; then
.github/workflows/ci.yml:74:            echo 'UNIT_REUSE run-unit=true reason=helper-failed'
.github/workflows/ci.yml:75:            echo 'run-unit=true' >> "$GITHUB_OUTPUT"
.github/workflows/ci.yml:98:    # [impl->REQ-CI-PUSH-MAIN-UNIT-REUSE]
.github/workflows/ci.yml:99:    if: needs.changes.outputs.code == 'true' && needs.changes.outputs.run-unit != 'false'
.github/workflows/golden.yml:24:  # only the exact gater-assembled golden candidate. Main itself runs thin CI,
AGENTS.md:42:- **CI / merge strategy:** golden CI (ADR-0050, ruled 2026-07-27) — milestone-batch golden runs, thin-lane PRs, ff-only main (tested sha == merged sha). Pi
CONCIERGE-183-JIT.md:507:- RCA COMPLETE (golden red, one cell): LATENT MAIN DEFECT, not chain regression. Census
CONTEXT.md:169:**capability declaration** — which endpoint types a harness/node can host (a Pi node might host only Shells, never a LiveAgent). Static manifest list, co
EMISSION-RESIDUAL-CENSUS-FINDING.md:82:  (main is frozen for r2 parity — tag == main == r2-tested `e4f52047`; the sites are
IO-PARSER-22-JIT.md:9:main ff-only to tested sha. Registry-first: REQs mint in the builder PR before evidence (rule 3).
KEYSTONE-182-JIT.md:104:Assemble golden head off main, compile-gate + traceable-reqs check, NAME THE NEVER-EXECUTED CELLS
KEYSTONE-182-JIT.md:340:  BOTH HELD for the golden freeze on main.
KEYSTONE-182-JIT.md:901:  main FF 80ab77a -> 901a9f5 PUSHED, tested sha == merged sha (ADR-0050). Freeze-held register
REGISTER-SWEEP-242-DRAFT.md:5:nothing lands on main before the tag (tag==main==tested parity).
WEBSERVE-272-W2-JIT.md:259:  1. Wait for main run 34083455082's WINDOWS UNIT job to conclude (doyle's ruling (b): one
WEBSERVE-272-W3-DRIFT-RIDERS.md:37:Your cells (in `crates/xtask/src/main.rs` `#[cfg(test)]`, tagged `// [unit->REQ-DOCS-CHANGELOG-PAGE]`):
docs-site/src/serving/attachments.md:194:firewall output remained unchanged on both nodes. This accepts the tested
docs/GOLDEN-CI.md:11:## Push-main unit evidence reuse
docs/GOLDEN-CI.md:13:<!-- [doc->REQ-CI-PUSH-MAIN-UNIT-REUSE] -->
docs/GOLDEN-CI.md:16:`changes` job publishes TWO outputs, and a push to main skips unit through
docs/GOLDEN-CI.md:22:- `run-unit` (IR-144, this section): defaults to `true`. Only a `push` to
docs/GOLDEN-CI.md:24:  `.github/ci/push-main-unit-reuse.py` and exact-SHA PR proof. Lint still
docs/GOLDEN-CI.md:55:`UNIT_REUSE run-unit=true reason=...`; a proved reuse records the run ID,
docs/GOLDEN-CI.md:56:attempt and SHA with `run-unit=false`. Tokens and API stderr are never
docs/GOLDEN-CI.md:60:conditions. Golden remains the full-suite authority (ADR-0050).
docs/GOLDEN-CI.md:63:`python3 .github/ci/push-main-unit-reuse-selftest.py` (also a changes-job
docs/GOLDEN-CI.md:99:**What main-tip unit evidence means:** main's exact SHA carries unit evidence for its CODE: at that sha via IR-144's exact-PR proof, or inherited fro
docs/INPUT-PROVENANCE-CONTRACT.md:6:The two-node field acceptance remains separate from the doc/impl/unit lane.
docs/KNOWN-HAZARDS.md:946:- **Measured breadth, predicates stated separately:** on the wider non-recursive root `crates/*/tests/*.rs`, 42 files contain `taskkill` plus th
docs/RELEASE-RUNBOOK.md:111:  construction — ruled sha == main tip == golden ref == tag, one object with
docs/RELEASE-RUNBOOK.md:602:   the SHA: golden remains the full-suite authority. Required golden evidence
docs/REMOTE-FRICTION-GRILL.md:27:Implementation and release orchestration are authorized under the confirmed scope. Build capacity, fixture isolation, independent golden 
docs/adr/0050-golden-ci-merge-integration.md:5:Per-PR full-suite CI on two single-box runners produced eight-hour merge sweeps dominated by queue wait and environmental f
docs/adr/0050-golden-ci-merge-integration.md:12:- **Green-then-merge-individually** — golden as a gate but PRs merge normally after. Rejected: recreated merge commits m
docs/adr/0050-golden-ci-merge-integration.md:53:The omission became visible because the release driver published his exact commands for review before running them: his fi
docs/adr/0050-golden-ci-merge-integration.md:63:Main advances only to a SHA whose golden run is **green**. “Tested” means the suite passed; an explained red is not go