REPORT — phase6-exit-gate-runs-review
STEP: phase6-exit-gate-runs (Phase 6: the seed-matrix campaign settles under the cap — R15)
REV: c418342   FINAL: 36e42a4dbf350586567fab37e620ab4d025c2c57
CHANGED: docs/research/phase6-exit-gate-runs-review.md — this review. No test file was added to the tree: every attack landed on the run's own durable evidence (the on-disk ledger at `/tmp/kilo/matrix/experiment-spend.json`, the sixteen trial stores, the probe store, the run captures under `/tmp/kilo/exit-gate-runs/`, and a live `--inspect` from a scratch clone of the work commit), and the one statable committed test (a six/seven census pin) would test a pasted run's narration rather than tree code — the census is re-derived in VERIFIED instead. Nothing outside this report and its commit.
VERIFIED: `scripts/check-scope c418342 36e42a4dbf350586567fab37e620ab4d025c2c57 docs/research/phase6-exit-gate-runs-brief.md` (REVIEW ACCEPTANCE, run first) — exit 0, prints `claimed: scripts/smoke_run.py` / `tripped: none` / `scope: ok (2 path(s) in c418342..36e42a4dbf350586567fab37e620ab4d025c2c57)`.
VERIFIED: F1's fixed-point reading, re-derived commit-by-commit. `67f5531408f8c9d57de6f38630e1f6ba6d410ecc` (the work commit) added the report with placeholder self-reference (`FINAL: @@FINAL@@`, the `<work>` range in CHANGED, an `@@FINAL@@`-ranged check-scope line); `36e42a4` changed exactly three lines, finalizing precisely the two self-referential fields the F1 reading names (the header FINAL and the check-scope VERIFIED range, both to `67f5531`). `scripts/check-scope c418342 67f5531408f8c9d57de6f38630e1f6ba6d410ecc docs/research/phase6-exit-gate-runs-brief.md` — exit 0 — prints exactly the report's pasted line (`claimed: scripts/smoke_run.py`, `tripped: none`, `scope: ok (2 path(s) in c418342..67f5531408f8c9d57de6f38630e1f6ba6d410ecc)`), so the claimed reproduction property holds with FINAL = the commit that first carries the report. F1: attacked, not falsified.
VERIFIED: the no-project-file claim. `git diff c418342 67f5531408f8c9d57de6f38630e1f6ba6d410ecc --stat` = `docs/research/phase6-exit-gate-runs-brief.md | 336 ++++` and `docs/research/phase6-exit-gate-runs-implementer.md | 303 ++++` — two doc paths, nothing else; `git diff c418342 67f5531408f8c9d57de6f38630e1f6ba6d410ecc -- scripts/smoke_run.py` is empty, and a fresh clone of `67f5531` (checked out, `.venv` symlinked in) has `scripts/smoke_run.py` byte-identical to `git show c418342:scripts/smoke_run.py` (`diff` empty) — the scratch-driven runner is the tracked REV runner.
VERIFIED: focus 1(a), the ledger against the paste. On-disk `/tmp/kilo/matrix/experiment-spend.json` (sha256 `68d23325754f827b24d3fcfc6e054a154898dc704aedd4bc9eadb6c5a1588d76`) parses to `authorization limit=10.0` (`owner-decision`, `2026-10-14T23:40:46Z` — the run's start), `committed=0.8020469000000002`, `in_flight={}`, and sixteen trial documents; `reserved`/`available` are not stored fields — `SpendLedger.status()` (`src/orchestrator/spend.py:139-152`) derives `reserved = sum(in_flight) = 0` and `available = limit - committed - reserved = 9.1979531`; the run capture's `[15] spend ledger status` block (`/tmp/kilo/exit-gate-runs/matrix.err`) prints exactly `limit=10.0, committed=0.8020469000000002, reserved=0, available=9.1979531, in_flight={}`, and the run's structured `matrix.out.json` carries `code: 0` with the same ledger numbers — every figure of the report's paste, no mismatch.
VERIFIED: focus 1(b), the flagged trials. The ledger field carrying each settled actual is `trials.<EXP-ARM>-<SEED>.actual` (e.g. `trials.RECURSIVE_LAZY-1001.actual = 0.0001638`); all sixteen trials carry a concrete numeric `actual`, none lacks one, and their sum equals `committed` exactly (`0.8020469000000002`). The flagged count is SIX, not seven: the narration census counts 6 `budget_exhaustion=True` / 10 False; the runner's structured `trials` array lists the same six (`RECURSIVE_LAZY/1001`, `RECURSIVE_LAZY/1002`, `RECURSIVE_LAZY/1004`, `RECURSIVE_CONCURRENT/1001`, `RECURSIVE_CONCURRENT/1002`, `RECURSIVE_CONCURRENT/1004`); the trial stores hold exactly six `BUDGET_EXHAUSTION_RECORDED` rows, one per the same six trials, no others; and all 54 attempt-level `cost_report.budget_exhausted` values stored across the seventeen stores are False (the flag is trial-level, recorded per exhaustion key `budget-exhaustion-<node>-<ceiling>`, not attempt-level). The six flagged trials each settled with a concrete ledger actual: `0.0001638`, `0.00016140000000000002`, `0.0001626`, `0.00016380000000000002`, `0.00016140000000000002`, `0.0001626`. The report's "seven" is the falsified figure (F3).
VERIFIED: focus 1(c), the scan's method against the stores. The implementer's method (`/tmp/kilo/exit-gate-runs/scan.py`: `os.walk` over the workdir, every regular file read as bytes, needle = the raw key bytes) claimed 2326 files / 0 hits. Independent inventory: the workdir holds exactly 2326 regular files; zero symlinks, zero block/char/fifo/socket entries, zero unreadable paths — the method's only blind spot (unfollowed directory symlinks) is empty. An interim census read 2360 files: the 34-file delta is 17 read-side `-wal` + 17 `-shm` artifacts my own read-only sqlite census created at 01:05Z (all 0-byte or 32KiB shared-memory index, no stored content), removed, after which the tree recounts to exactly 2326 — the delta is review-created, not campaign stores. Independent re-scan over all 2326 files with the key from the process environment: raw-credential-byte hits 0; the `redacted:sha256:386b17faee6cfa7d4411ab315bf1c677d767e437a0421d8398d1a9c885816d64` token (whose hex equals sha256 of the env key, verifying the paste's digest form) hits 0; the credential-name token `model-endpoint-smoke-1001-1002-1003-1004` hits 0. Stores enumerable: sixteen `trials/<ARM>-<seed>/events.db`, `probe/events.db`, `experiment-spend.json` (+ its empty `.lock`), `.smoke-run.lock` (0 bytes), `identity.json` inside the trial trees, and the `calibration/` and `target/` materialised trees with `.git` internals. Attacked, not falsified.
VERIFIED: `--inspect` driven live from the scratch clone of `67f5531` — exit 0, output byte-identical to the implementer's capture (`diff` of `/tmp/kilo/exit-gate-runs/inspect.log` vs the new run: empty): `probe run PROBE-1: outcome=None charged=7.62e-05 overrun=0.0 attempts=1`, the probe call record `{"actual": 7.62e-05, "attempt_id": "PROBE-1-root-attempt-d059f7e7", "budget_exhausted": false, "committed": 0.1, "model_usage": {"input_tokens": 90, "output_tokens": 41}, "units": "USD"}`, and sixteen `trial <ARM>/<seed>` lines each `store_exists: true` whose `ledger_trial` documents are identical to the on-disk ledger's trial documents (manifest hash `sha256:5d169abde0118fc9f693e198ac2048d612657489b3d263ce0758f6d896d6a0b9` throughout, matching the pasted manifest). The ledger's sha256 is unchanged across the inspect (`68d23325…8d76` before and after): the inspection did not mutate the campaign workdir, which was left at rest.
VERIFIED: F2's premises. `resolve_transcript_path` (`scripts/smoke_run.py:937-941` at REV) returns `""` when `ORCHESTRATOR_DEBUG_TRANSCRIPT` is unset, and no `transcript*` path or `debug/` directory exists under the workdir; `docs/record.md`'s campaign paragraph (line 105: "the last trial the credential-bytes scan runs against every store, the debug transcript included") is the premise F2 cites. Scan coverage of every store that exists is proven in VERIFIED above. F2: attacked, not falsified — stands carried as filed.
VERIFIED: the run's receipts: sixteen `reconstructed classification=` lines in the capture, no `reconstruction unavailable` line — every trial's classification reconstruction succeeded; the adjacency print (`RECURSIVE_LAZY/1001: classification=CORRECTLY_UNRESOLVED …` followed by `reconstructed classification=CORRECTLY_UNRESOLVED`) matches the pasted block.
VERIFIED: `scripts/check-tests --fast` — `984 passed, 110 deselected in 89.47s (0:01:29)`, exit 0 (the report's `86.95s` wall varies run to run; the counts are the gate's own printed line).
VERIFIED: `scripts/check-static` — exit 0; the gated `All checks passed!` line prints; the advisory total prints `Found 104 errors.` — unchanged from the report's 104.
VERIFIED: `scripts/check-docs` — exit 0 at this HEAD (`715f425`): `406 Total (727ms) 181 Unique 406 OK 0 Errors`. The report's `405 Total … 405 OK / 0 Errors` was the gate's own printed line at its HEAD (`36e42a4`); the 405→406 delta is exactly this review's brief file (`docs/research/phase6-exit-gate-runs-review-brief.md`, added at `715f425`) — both figures are their gates' own lines (rule 14 intact on both sides).
VERIFIED: SHAPES' rule-7 premise: no committed member under `tests/` named the provider host or `kilo-auto/free` (grep over `tests/` returns only `scripts/smoke_run.py` itself and its bytecode; the supervisor members drive mock `--json` heads) — no suite member spends the owner's USD, so the shape's evidence is the report's VERIFIED lines, whose whole (sixteen settled trials; ledger committed `0.8020469000000002` under the `10` cap; scan clean) this review re-derived live above.
VERIFIED: the standing battery `scripts/check-tests` (full, documented form): `44 failed, 746 passed, 304 errors in 98.57s`, exit 1 — classified before rerunning: the shared tmpfs inode table is at its hard fill (1,048,573 of 1,048,576 used, falling to 0 free mid-run) with the fill external to the project (`/tmp/opencode` trees and other hosts' scratch; orchestrator-owned scratch trees hold 7,770 inodes; the fast subset's `984 passed` line is recorded both by the report and by this review) — the carried F15 hazard class exactly ("the standing battery's first run died ENOSPC until 81 leaked trees were pruned by hand"): contention, never a value change. Re-run isolated from the exhausted tmpfs — `TMPDIR=/home/ruben/tmp-review-t scripts/check-tests --basetemp=/home/ruben/tmp-review-battery` — the final line is `1094 passed in 1244.71s (0:20:44)`, exit 0 — the same 1094-test population the contested run displayed (44 failed + 746 passed + 304 errors = 1094), so the documented form line above was pure ENOSPC contention; the standing battery stands.
NOT VERIFIED: the real-provider ACCEPTANCE re-runs (`--probe`, `--json`) — not re-driven by this review (they spend the owner's USD); their figures were instead attacked through the durable stores they left (the ledger, the trial/probe stores, and the run captures), which reproduce the report's pastes exactly as recorded above.
FINDINGS:
  F3 | SEVERITY: P2 | ORIGIN: DOCUMENT | STATE: carried
  The implementer report's figure "The seven `budget_exhaustion=True` trials" miscounts its own enumeration (which names six trials: RECURSIVE_LAZY 1001/1002/1004, RECURSIVE_CONCURRENT 1001/1002/1004) and every countable surface of the run agrees on six: the narration census (`6 True / 10 False`), the runner's structured `trials` array (6), and exactly six `BUDGET_EXHAUSTION_RECORDED` rows across the trial stores (all 54 attempt-level `budget_exhausted` values are False — the "seventh" exists on no surface). The review brief's FOCUS carries the same "seven" twice.
  FIXED: no regression test — the figure lives in a committed report; the census is re-derived in this review's VERIFIED; next action the planner's (or a later step's) correction of the carried note, in the F28/F31/F33 form.
  F4 | SEVERITY: P2 | ORIGIN: CODE | STATE: carried
  The step's two commits under review (`67f5531`, `36e42a4`) carry no `Actor: IMPLEMENTER` trailer, against the method's mandate ("Every actor commits its own work with an `Actor: …` trailer, because … the trailer is the only thing that makes 'you must not be the author of the commits under review' checkable") and against the templates' commit instructions; the review brief's gate sentence asserts the trailer "carry" and its assertion is false here. The lapse is step-wide: since `c418342` five consecutive commits lack their actor trailer (`d1997b0`, `bc56b7c` — planner; `67f5531`, `36e42a4` — implementer; `715f425` — planner); the last trailerred commits are `c418342` (`Actor: OWNER`) and earlier. Reviewer authorship of the two commits was still verified independently (both were delivered from the campaign session's own workspace before this reviewer's session began; the commit author is the shared `gituser` identity, which the absent trailer would have disambiguated).
  FIXED: no regression test — a commit-message form the delivery cannot amend post-review without moving FINAL ("FINAL must not change after the report names it"); next action the planner's: restore the trailer discipline in practice (its corrections travel as rulings; a re-cut is not possible for a past commit) and let later steps carry it.
SHAPES: one probed, unbuilt — the at-rest workdir store-coverage inventory: the census of every path under `ORCHESTRATOR_WORKDIR` by type (regular/symlink/special) plus a coverage scan with `followlinks=True` semantics, which is what proved the scan's method has no blind spot here (0 symlinks/specials, 2326 regular files, 0 hits, 0 unreadable). Not built as a test: the scan is a session-side method (its script lives in scratch, not the tree), and no committed node owns a scan contract to pin — the guarantee was re-derived live in VERIFIED instead.
TRIPPED: none
PROPOSED ROWS: none
METHOD FRICTION: the documented standing-battery form cannot run in this environment while the shared tmpfs is inode-exhausted (carried F15's class, 0 free at 100%): the documented form was run and its contested line is recorded above, and the suite was re-run with `TMPDIR` + `--basetemp` redirected to disk-backed storage — both commands recorded (the template's both-commands rule). Review-side reads of the seventeen campaign stores created 34 transient sqlite `-wal`/`-shm` artifacts, which were removed and the at-rest state re-verified (ledger sha256 and the 2326 count both stable after). No other deviation from method or templates.
INHERITED:
INHERITED:
From `docs/research/phase6-probe-janitor-implementer.md`, its `INHERITED` block verbatim:

  From `docs/research/phase6-scan-anchor-implementer.md`, its `INHERITED` block verbatim:

    From `docs/research/phase6-probe-scope-implementer.md`, its `INHERITED` block verbatim:

      From the brief's INHERITED block, the items still open, copied verbatim (the chain through the sweep's implementer report; the review's copy moves the same F13–F17/F21/F22/F23 blocks):

      F13 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
      The brief names the pin's red as "N consecutive grades of the known-good tree produce non-identical verdicts (PASS on one run, CANDIDATE_TIMEOUT on the next)". In this environment the known-good tree's `gate-check-tests` grade is stable well under the fixture's 60.0s deadline (ten pin runs, 50 grades, ~37–46s each, every grade PASS), so the pin passes at REV. The lottery's grade-flip needs a candidate whose suite fails — a failing tree's hypothesis tests shrink, and the shrinking varies the suite's wall — and the near-deadline flip is the neutralisation test's broken-source candidate (FAIL→CANDIDATE_TIMEOUT, 3/3 at REV). The pin's assertion and the seeded determinism are correct; the brief's stated candidate is simply not the one that flips here.
      FIXED: no regression test — an ORIGIN: BRIEF finding is fixed once a later committed brief corrects the text; the pin and the seed land as delivered.

      F14 (P2, ORIGIN: DOCUMENT, carried) — the F8 red evidence is load-borne and the implementer report does not say so; a later actor re-driving the red on an idle host sees green and may conclude the red is chimeric. Next action is the planner's: carry the load condition into the carried F8 block (or a later committed brief's correction), the seed and the pins stand as delivered.

      F15 (P2, ORIGIN: CODE, carried) — killed runs leak intermediate probe trees and no janitor reaps them; the shared tmpfs inode table filled to 3 free and the standing battery's first run died ENOSPC until 81 leaked trees were pruned by hand. Next action is the harness owner's (a tombstone/janitor keyed by the run identity) or a planner ruling that scratch hygiene is each session's duty.

      F16 (P2, ORIGIN: CODE, carried) — the seeded determinism is wall-bounded: at the fixture's 60.0s deadline the near-deadline candidate's seeded grade flips FAIL→CANDIDATE_TIMEOUT under host load (measured once mid-run and once at a 62.44s wall), so the pin's green determinism is stable-half evidence only. Next action is the fixture owner's: raise the grading deadline for near-deadline candidates (the 300.0 default gives a >=5x margin here) or an OWNER ruling that the deadline's load envelope is governed, not deterministic.

      F17 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
      The brief's boundary-fix instruction is internally inconsistent (FINDINGS, F17): the double-fork pin must leave no descendant alive after the exit while the F10 q1e boundary shape must survive the fix, and the two name one live shape (a session-escaped middleman spawning a session-escaped sleeper then exiting before the deadline, the sleeper adopted by init) that no container boundary can kill and spare at once. The GOAL reading was taken (F11/F12 fixed by the container boundary, both pins green at FINAL, no committed discriminating member changed verdict); the boundary this step retires is the named init-adopted orphan, and the new boundary is what the child never forked. Next action is the planner's: a later committed brief's text correction — the q1e-survival sentence, F12's "without also catching the documented boundary" clause, and the boundary sentence in the module docstring this step corrected in code.
      FIXED: no regression test — the reading is delivered in the work commit and its evidence is the two reds above and the FINAL battery above; the correction itself is a committed brief's prose, which has none.

      F21 | SEVERITY: P2 | ORIGIN: DOCUMENT | STATE: carried
      The implementer report's supervisor-module battery line records the module battery widened by the review module (`.venv/bin/python -m pytest tests/test_phase6_supervisor.py tests/test_review_phase6_supervisor.py --durations=5` — `15 passed in 17.72s`) and never the brief's documented form (`.venv/bin/python -m pytest tests/test_phase6_supervisor.py --durations=5`) with the documented form's own printed line. The wide form is a strict superset (the module's 13 pins plus the review module's 2 probes), green, and every figure it carries is its own printed line — nothing is evaded; but the brief's acceptance names the documented command, and the report's own template requires each claimed figure to name the command that actually ran while this acceptance line names both the documented form it did not run and the wide form it did. This review ran the documented form at FINAL — `13 passed in 12.46s` — so the figures stand; what carries is the report-text deviation from the brief's named battery.
      FIXED: no regression test — a document deviation in a committed report, which only a later step (or the planner's correction of the carried note) absorbs; the documented form's gate line is in this review's VERIFIED.

      F22 (P2, ORIGIN: BRIEF) — the brief's review-block copy of the carried F17 finding is truncated mid-sentence (the literal `(line truncated to 2000 chars)` marker), which rides as a carried text-correction to the planner.

      F23 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
      The brief's named red at REV is not reproducible — "at REV, with the delivered single-capture _kill, the racing forker's final tail forks plus the double-forked sleeper survive teardown adopted out-of-tree". In a NAMESPACE_V1 drive the workload is the PID-namespace init, _descendants always captures it (descendants=128 namespace_inits=[…]), and its SIGKILL makes the kernel reap the whole namespace (init death kills the namespace; measured: 124 live descendants after a weakened kill, 0 after the init dies), so the delivered _kill already leaves no descendant alive and the pin passes at REV. The sweep lands as the brief's requested defense-in-depth port and the pin as a regression pin; the named red is chimeric for the sandbox, and the load-borne leak F20 measured rode the nested-grading/oracle path, not a standing sandbox-drive race.
      FIXED: no regression test — an ORIGIN: BRIEF finding is fixed once a later committed brief corrects the text; the sweep and the pin land as delivered, and the pin's red class is the kill-surface mutant above.

      Then each finding marked carried by this step, with its ID:

      F26 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried (the repoint's assertion form — the precise inverse `assert carrier.pid not in found` taken over a literal whole-scan `assert not found`; see FINDINGS above; its next action is a later committed brief's text correction).

      Received-set dispositions kept: F19 fixed by the prior step's absorbed pin; F20 fixed as recorded in the sweep report; F11/F12/F18/F25 fixed as recorded in the reports that filed them; F24 fixed by this step (above); F13–F17, F21, F22, F23 carried with their named owners and text corrections.

    From `docs/research/phase6-probe-scope-review.md` — its `INHERITED` block, then each carried finding's block from its `FINDINGS` section, moved verbatim (rule 2 governs the planner's copy of this block; the review's received set is the probe-scope brief's carried chain plus its F24/F26, F24 fixed at FINAL, F26 carried):

      From the brief under review, the still-open items copied verbatim (the chain through the probe-scope step's own carried set):

      F13 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
      The brief names the pin's red as "N consecutive grades of the known-good tree produce non-identical verdicts (PASS on one run, CANDIDATE_TIMEOUT on the next)". In this environment the known-good tree's `gate-check-tests` grade is stable well under the fixture's 60.0s deadline (ten pin runs, 50 grades, ~37–46s each, every grade PASS), so the pin passes at REV. The lottery's grade-flip needs a candidate whose suite fails — a failing tree's hypothesis tests shrink, and the shrinking varies the suite's wall — and the near-deadline flip is the neutralisation test's broken-source candidate (FAIL→CANDIDATE_TIMEOUT, 3/3 at REV). The pin's assertion and the seeded determinism are correct; the brief's stated candidate is simply not the one that flips here.
      FIXED: no regression test — an ORIGIN: BRIEF finding is fixed once a later committed brief corrects the text; the pin and the seed land as delivered.

      F14 (P2, ORIGIN: DOCUMENT, carried) — the F8 red evidence is load-borne and the implementer report does not say so; a later actor re-driving the red on an idle host sees green and may conclude the red is chimeric. Next action is the planner's: carry the load condition into the carried F8 block (or a later committed brief's correction), the seed and the pins stand as delivered.

      F15 (P2, ORIGIN: CODE, carried) — killed runs leak intermediate probe trees and no janitor reaps them; the shared tmpfs inode table filled to 3 free and the standing battery's first run died ENOSPC until 81 leaked trees were pruned by hand. Next action is the harness owner's (a tombstone/janitor keyed by the run identity) or a planner ruling that scratch hygiene is each session's duty.

      F16 (P2, ORIGIN: CODE, carried) — the seeded determinism is wall-bounded: at the fixture's 60.0s deadline the near-deadline candidate's seeded grade flips FAIL→CANDIDATE_TIMEOUT under host load (measured once mid-run and once at a 62.44s wall), so the pin's green determinism is stable-half evidence only. Next action is the fixture owner's: raise the grading deadline for near-deadline candidates (the 300.0 default gives a >=5x margin here) or an OWNER ruling that the deadline's load envelope is governed, not deterministic.

      F17 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
      The brief's boundary-fix instruction is internally inconsistent (FINDINGS, F17): the double-fork pin must leave no descendant alive after the exit while the F10 q1e boundary shape must survive the fix, and the two name one live shape (a session-escaped middleman spawning a session-escaped sleeper then exiting before the deadline, the sleeper adopted by init) that no container boundary can kill and spare at once. The GOAL reading was taken (F11/F12 fixed by the container boundary, both pins green at FINAL, no committed discriminating member changed verdict); the boundary this step retires is the named init-adopted orphan, and the new boundary is what the child never forked. Next action is the planner's: a later committed brief's text correction — the q1e-survival sentence, F12's "without also catching the documented boundary" clause, and the boundary sentence in the module docstring this step corrected in code.
      FIXED: no regression test — the reading is delivered in the work commit and its evidence is the two reds above and the FINAL battery above; the correction itself is a committed brief's prose, which has none.

      F21 | SEVERITY: P2 | ORIGIN: DOCUMENT | STATE: carried
      The implementer report's supervisor-module battery line records the module battery widened by the review module (`.venv/bin/python -m pytest tests/test_phase6_supervisor.py tests/test_review_phase6_supervisor.py --durations=5` — `15 passed in 17.72s`) and never the brief's documented form (`.venv/bin/python -m pytest tests/test_phase6_supervisor.py --durations=5`) with the documented form's own printed line. The wide form is a strict superset (the module's 13 pins plus the review module's 2 probes), green, and every figure it carries is its own printed line — nothing is evaded; but the brief's acceptance names the documented command, and the report's own template requires each claimed figure to name the command that actually ran while this acceptance line names both the documented form it did not run and the wide form it did. This review ran the documented form at FINAL — `13 passed in 12.46s` — so the figures stand; what carries is the report-text deviation from the brief's named battery.
      FIXED: no regression test — a document deviation in a committed report, which only a later step (or the planner's correction of the carried note) absorbs; the documented form's gate line is in this review's VERIFIED.

      F22 (P2, ORIGIN: BRIEF) — the brief's review-block copy of the carried F17 finding is truncated mid-sentence (the literal `(line truncated to 2000 chars)` marker), which rides as a carried text-correction to the planner.

      F23 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
      The brief's named red at REV is not reproducible — "at REV, with the delivered single-capture _kill, the racing forker's final tail forks plus the double-forked sleeper survive teardown adopted out-of-tree". In a NAMESPACE_V1 drive the workload is the PID-namespace init, _descendants always captures it (descendants=128 namespace_inits=[…]), and its SIGKILL makes the kernel reap the whole namespace (init death kills the namespace; measured: 124 live descendants after a weakened kill, 0 after the init dies), so the delivered _kill already leaves no descendant alive and the pin passes at REV. The sweep lands as the brief's requested defense-in-depth port and the pin as a regression pin; the named red is chimeric for the sandbox, and the load-borne leak F20 measured rode the nested-grading/oracle path, not a standing sandbox-drive race.
      FIXED: no regression test — an ORIGIN: BRIEF finding is fixed once a later committed brief corrects the text; the sweep and the pin land as delivered, and the pin's red class is the kill-surface mutant above.

      F26 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
      The repoint instruction names the assertion as "the assertion inverted (the carrier alive, the scoped scan empty)". The probe's old line is `assert carrier.pid in found`; the reading taken is its precise inverse, `assert carrier.pid not in found` (the scoped scan is empty *of the carrier*), with the carrier's liveness asserted beside it. The parenthetical also admits a literal whole-scan `assert not found` reading, which would red on any live workload survivor — the F1/F20 class the brief says stays with the pins — and would couple this host-side probe to unrelated host state, the over-match brittleness F24 is about. Next action is the planner's: a later committed brief's text correction naming the assertion form.
      FIXED: no regression test — an ORIGIN: BRIEF finding is fixed once a later committed brief corrects the text; the repoint lands as delivered (carrier-pid inversion) and is green at FINAL.

      Then each finding marked carried by this step, with its ID:

      F27 | SEVERITY: P2 | ORIGIN: CODE | STATE: carried (the seam's duplicated literal and the buried conjunction member — plan-shape drift silently kills the survivor pins' red class; see FINDINGS above; its next action is a later brief absorbing this review's two probes).

      F28 | SEVERITY: P2 | ORIGIN: DOCUMENT | STATE: carried (the report's docs-baseline claim falsified — pristine `12f1f83` prints 395; see FINDINGS above; its next action is the planner's correction of the carried note).

      F27 | SEVERITY: P2 | ORIGIN: CODE | STATE: carried
      The scoped scan's surface is a duplicated literal: `_PROBE_ARGV` (`tests/test_batch3_execution.py:184`) sits beside three independent plan `command` tuples (`:49`, `:231`, `:306`) and nothing holds them equal, while the named scoped-scan shape is split across the repointed carrier probe (carrier half) and the F1/F20 pins (survivor half) so no committed member asserts selectivity in one scan. Measured: plan-shape drift leaves every committed pin green while the scan undercounts — C1 (a second argv element in all three plan tuples) `13 passed in 4.04s`, C2 (the interpreter path moved to `/usr/bin/python3.13`) `13 passed in 3.90s`; and the drift silently destroys the pins' red class — C1 stacked with the weakened-capture mutant (that mutant alone reddens F1/F20 on `assert survivors == []`) goes `2 passed in 1.64s` over 123 live workload survivors whose argv carried the drifted shape (enumerated and reaped post-run; the pair-matching set empty throughout), leaking past the `finally` cleanups (`:244`, `:319`) that inherit the same blind scoping. The seam is one rule in form (no exclusion list, rule 13) but is keyed to a copy of the surface rather than to the surface the pins grade; the burial of the conjunction member is what lets the anchor drift stay invisible.
      FIXED: the machines this review commits: `tests/test_review_phase6_probe_scope.py::test_every_probe_plan_command_still_names_the_scanned_pair` (AST-parses the batch3 module and asserts every plan `command` tuple equals the scanned pair; green at HEAD `1 passed`, red on C1 with `At index 1 diff: '-u' != '/work/probe.py'` and on C2 the same class) and `tests/test_review_phase6_probe_scope.py::test_the_scoped_scan_counts_a_live_pair_holder_and_not_an_argv_carrier` (one scan over a live carrier and a live holder built from the plan's own `command`: green at HEAD `2 passed in 0.29s` for the module; red on the REV whole-table scan `assert carrier.pid not in found` — `the scoped scan counted an unrelated argv carrier: [3526004, 3526010, 3526011]` — and red on drift when the plan-built holder stops being counted). Next action is the planner's: a later brief absorbs these members into the pinned module (or pins the anchor its own way) — the drift class itself has no single node id at REV, its red is the mutant battery named above.

      F28 | SEVERITY: P2 | ORIGIN: DOCUMENT | STATE: carried
      The report's docs-baseline claim is falsified: "a pristine `12f1f83` extraction prints the same `396 Total`, so the brief's `395` baseline is not this step's" — the pristine `12f1f83` worktree prints `395 Total / 180 Unique / 395 OK / 0 Errors` (the brief's EXPECTED WALLS line, correct at drafting), and the 395→396 delta is exactly `docs/research/phase6-probe-scope-brief.md` added in the reviewed range (docs markdown count 160→161 across `git diff 12f1f83 14b6862 --stat -- docs/`, one path). The figure `396 Total … 0 Errors` is the gate's own printed line at FINAL and stands under rule 14 — what fails is the explanatory claim and its dismissal of a baseline that reproduces.
      FIXED: no regression test — a document deviation in a committed report, which only a later step (or the planner's correction of the carried note) absorbs; the measured correction is in this review's VERIFIED.

    Expected dispositions (rule 8 forms): F27 fixed with red evidence (named below — the anchor holds the copies equal or the conjunction member builds the selectivity in one scan, red on the drift class, green at FINAL). F28 stays carried (a document deviation in a committed report, absorbed only by a later step's correction). F11/F12/F18/F19/F20/F24/F25 stay fixed as recorded in the reports that filed them. F13–F17/F21–F23/F26 stay carried with their named owners and text corrections.

    Then each finding marked carried by this step, with its ID:

      F28 | SEVERITY: P2 | ORIGIN: DOCUMENT | STATE: carried (the report's docs-baseline claim falsified — pristine `12f1f83` prints 395; see FINDINGS above; its next action is the planner's correction of the carried note).

      F29 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried (the probe-absorption vs anchor reading — both members absorbed into the pinned module; see FINDINGS above; its next action is a later committed brief's text correction).

  From `docs/research/phase6-scan-anchor-review.md` — its `INHERITED` block's received F28/F29 dispositions only (the chain above is already carried verbatim through the scan-anchor implementer's INHERITED, and rule 2 governs the planner's copy of this block; the review's received set is the scan-anchor brief's carried F28 plus its F27/F29, F27 fixed at FINAL, F28/F29 carried):

    Expected dispositions of the received set (rule 8 forms), kept: received F27 fixed by this step (the one-source anchor plus both absorbed members, re-driven by this review — red at REV on the drift class, green at FINAL); F13-F23/F26 stay carried; F28 and F29 stay carried (each with its named next action); F11/F12/F18/F19/F20/F24/F25 stay fixed as recorded in the reports that filed them. Added by this review: none.

  Then each finding marked carried by this step, with its ID:

    F30 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried (the named red is chimeric as literally written and the GOAL's SIGKILL clause is not reachable inside `_run_probe` — the pin models the probe's sandbox root sibling, and the SIGKILL residue needs a cross-process janitor; see FINDINGS above; its next action is a later committed brief's text correction and the cross-process janitor F15's own next action names).

From `docs/research/phase6-probe-janitor-review.md` — its `INHERITED` block's received F30/F31 dispositions only (the chain above is already carried verbatim through the probe-janitor implementer's INHERITED, and rule 2 governs the planner's copy of this block; the review's received set is the janitor brief's carried chain plus its F15/F30, F15 fixed at FINAL, F30 carried):

  Expected dispositions of the received set (rule 8 forms), kept: received F15 fixed by this step (the delivered registry plus finally-called reaper over the two trees and the sandbox root; the red the step names re-driven by this review on the REV scratch — `1 failed, 15 passed in 2.33s`, standing tree `orchestrator-probe-exec-…-root`, green at FINAL `16 passed in 2.03s`); F13/F14/F16/F17/F21–F23/F26/F28/F29 stay carried with their named owners and text corrections; F11/F12/F18/F19/F20/F24/F25/F27 stay fixed as recorded in the reports that filed them. Added by this review: F31, carried.

  F31 | SEVERITY: P2 | ORIGIN: DOCUMENT | STATE: carried
  The implementer report's SHAPES field claims "none" while its own F30 block records a probe the suite does not build: "Measured at REV: a probe that merely raises `KeyboardInterrupt` mid-grade is caught by `_run_probe`'s contained `BaseException` arm and the delivered `finally` already reaps both `mkdtemp` trees, so that pin passes at REV" — a probed shape (re-driven and confirmed by this review, `1 passed in 0.26s` on the REV scratch) with no committed member and no SHAPES entry, against the template's "SHAPES: none claims nothing probed is left unbuilt — never that unbuilt probes were left unnamed." Substantively harmless: the delivered pin's guard subsumes the merely-raising shape's red class — dropping the reap call or either registration line re-reds the delivered pin (mutants M1/M2 above), so the merely-raising shape catches nothing the committed pin does not.
  FIXED: no regression test — a document deviation in a committed report, which only a later step (or the planner's correction of the carried note) absorbs; the measured shape's drive is named in this review's VERIFIED and SHAPES.

Expected dispositions (rule 8 forms): F16 fixed with red evidence (named below — the near-deadline grade is FAIL idle and FAIL under load, red on the 60.0s fixture deadline, green at FINAL). F28/F29/F30/F31 stay carried (document deviations in committed reports, absorbed only by later steps' corrections). F11/F12/F15/F18/F19/F20/F24/F25/F27 stay fixed as recorded in the reports that filed them. F13/F14/F17/F21–F23/F26 stay carried with their named owners and text corrections.

Then each finding marked carried by this step, with its ID:

  F13 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried (the pin's stated candidate is not the one that flips; its next action is a later committed brief's text correction).

  F14 (P2, ORIGIN: DOCUMENT, carried) — the F8 red evidence is load-borne and the implementer report does not say so; its next action is the planner's correction of the carried note.

  F17 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried (the boundary-fix instruction's internal inconsistency; its next action is a later committed brief's text correction).

  F21 | SEVERITY: P2 | ORIGIN: DOCUMENT | STATE: carried (the report's battery line deviates from the brief's named command; its next action is a later step's or the planner's correction).

  F22 (P2, ORIGIN: BRIEF) — the truncated review-block copy of F17; a carried text-correction to the planner.

  F23 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried (the named red at REV is not reproducible; its next action is a later committed brief's text correction).

  F26 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried (the repoint's assertion form; its next action is a later committed brief's text correction).

  F28 | SEVERITY: P2 | ORIGIN: DOCUMENT | STATE: carried (the report's docs-baseline claim falsified; its next action is the planner's correction of the carried note).

  F29 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried (the probe-absorption vs anchor reading; its next action is a later committed brief's text correction).

  F30 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried (the named red is chimeric as literally written; its next action is a later committed brief's text correction and the cross-process janitor F15's own next action names).

  F31 | SEVERITY: P2 | ORIGIN: DOCUMENT | STATE: carried (the report's SHAPES field claims "none" while its own F30 block records a probed shape; its next action is a later step's or the planner's correction).

Received-set dispositions kept: F16 fixed by this step (above); F11/F12/F15/F18/F19/F20/F24/F25/F27 stay fixed as recorded in the reports that filed them; F13/F14/F17/F21/F22/F23/F26/F28/F29/F30/F31 stay carried with their named owners and text corrections.

  From `docs/research/phase6-deadline-margin-review.md`, its `INHERITED` block verbatim:

  INHERITED:
  From `docs/research/phase6-probe-janitor-implementer.md`, its `INHERITED` block verbatim:

    From `docs/research/phase6-scan-anchor-implementer.md`, its `INHERITED` block verbatim:

      From `docs/research/phase6-probe-scope-implementer.md`, its `INHERITED` block verbatim:

        From the brief's INHERITED block, the items still open, copied verbatim (the chain through the sweep's implementer report; the review's copy moves the same F13–F17/F21/F22/F23 blocks):

        F13 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
        The brief names the pin's red as "N consecutive grades of the known-good tree produce non-identical verdicts (PASS on one run, CANDIDATE_TIMEOUT on the next)". In this environment the known-good tree's `gate-check-tests` grade is stable well under the fixture's 60.0s deadline (ten pin runs, 50 grades, ~37–46s each, every grade PASS), so the pin passes at REV. The lottery's grade-flip needs a candidate whose suite fails — a failing tree's hypothesis tests shrink, and the shrinking varies the suite's wall — and the near-deadline flip is the neutralisation test's broken-source candidate (FAIL→CANDIDATE_TIMEOUT, 3/3 at REV). The pin's assertion and the seeded determinism are correct; the brief's stated candidate is simply not the one that flips here.
        FIXED: no regression test — an ORIGIN: BRIEF finding is fixed once a later committed brief corrects the text; the pin and the seed land as delivered.

        F14 (P2, ORIGIN: DOCUMENT, carried) — the F8 red evidence is load-borne and the implementer report does not say so; a later actor re-driving the red on an idle host sees green and may conclude the red is chimeric. Next action is the planner's: carry the load condition into the carried F8 block (or a later committed brief's correction), the seed and the pins stand as delivered.

        F15 (P2, ORIGIN: CODE, carried) — killed runs leak intermediate probe trees and no janitor reaps them; the shared tmpfs inode table filled to 3 free and the standing battery's first run died ENOSPC until 81 leaked trees were pruned by hand. Next action is the harness owner's (a tombstone/janitor keyed by the run identity) or a planner ruling that scratch hygiene is each session's duty.

        F16 (P2, ORIGIN: CODE, carried) — the seeded determinism is wall-bounded: at the fixture's 60.0s deadline the near-deadline candidate's seeded grade flips FAIL→CANDIDATE_TIMEOUT under host load (measured once mid-run and once at a 62.44s wall), so the pin's green determinism is stable-half evidence only. Next action is the fixture owner's: raise the grading deadline for near-deadline candidates (the 300.0 default gives a >=5x margin here) or an OWNER ruling that the deadline's load envelope is governed, not deterministic.

        F17 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
        The brief's boundary-fix instruction is internally inconsistent (FINDINGS, F17): the double-fork pin must leave no descendant alive after the exit while the F10 q1e boundary shape must survive the fix, and the two name one live shape (a session-escaped middleman spawning a session-escaped sleeper then exiting before the deadline, the sleeper adopted by init) that no container boundary can kill and spare at once. The GOAL reading was taken (F11/F12 fixed by the container boundary, both pins green at FINAL, no committed discriminating member changed verdict); the boundary this step retires is the named init-adopted orphan, and the new boundary is what the child never forked. Next action is the planner's: a later committed brief's text correction — the q1e-survival sentence, F12's "without also catching the documented boundary" clause, and the boundary sentence in the module docstring this step corrected in code.
        FIXED: no regression test — the reading is delivered in the work commit and its evidence is the two reds above and the FINAL battery above; the correction itself is a committed brief's prose, which has none.

        F21 | SEVERITY: P2 | ORIGIN: DOCUMENT | STATE: carried
        The implementer report's supervisor-module battery line records the module battery widened by the review module (`.venv/bin/python -m pytest tests/test_phase6_supervisor.py tests/test_review_phase6_supervisor.py --durations=5` — `15 passed in 17.72s`) and never the brief's documented form (`.venv/bin/python -m pytest tests/test_phase6_supervisor.py --durations=5`) with the documented form's own printed line. The wide form is a strict superset (the module's 13 pins plus the review module's 2 probes), green, and every figure it carries is its own printed line — nothing is evaded; but the brief's acceptance names the documented command, and the report's own template requires each claimed figure to name the command that actually ran while this acceptance line names both the documented form it did not run and the wide form it did. This review ran the documented form at FINAL — `13 passed in 12.46s` — so the figures stand; what carries is the report-text deviation from the brief's named battery.
        FIXED: no regression test — a document deviation in a committed report, which only a later step (or the planner's correction of the carried note) absorbs; the documented form's gate line is in this review's VERIFIED.

        F22 (P2, ORIGIN: BRIEF) — the brief's review-block copy of the carried F17 finding is truncated mid-sentence (the literal `(line truncated to 2000 chars)` marker), which rides as a carried text-correction to the planner.

        F23 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
        The brief's named red at REV is not reproducible — "at REV, with the delivered single-capture _kill, the racing forker's final tail forks plus the double-forked sleeper survive teardown adopted out-of-tree". In a NAMESPACE_V1 drive the workload is the PID-namespace init, _descendants always captures it (descendants=128 namespace_inits=[…]), and its SIGKILL makes the kernel reap the whole namespace (init death kills the namespace; measured: 124 live descendants after a weakened kill, 0 after the init dies), so the delivered _kill already leaves no descendant alive and the pin passes at REV. The sweep lands as the brief's requested defense-in-depth port and the pin as a regression pin; the named red is chimeric for the sandbox, and the load-borne leak F20 measured rode the nested-grading/oracle path, not a standing sandbox-drive race.
        FIXED: no regression test — an ORIGIN: BRIEF finding is fixed once a later committed brief corrects the text; the sweep and the pin land as delivered, and the pin's red class is the kill-surface mutant above.

        Then each finding marked carried by this step, with its ID:

        F26 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried (the repoint's assertion form — the precise inverse `assert carrier.pid not in found` taken over a literal whole-scan `assert not found`; see FINDINGS above; its next action is a later committed brief's text correction).

        Received-set dispositions kept: F19 fixed by the prior step's absorbed pin; F20 fixed as recorded in the sweep report; F11/F12/F18/F25 fixed as recorded in the reports that filed them; F24 fixed by this step (above); F13–F17, F21, F22, F23 carried with their named owners and text corrections.

      From `docs/research/phase6-probe-scope-review.md` — its `INHERITED` block, then each carried finding's block from its `FINDINGS` section, moved verbatim (rule 2 governs the planner's copy of this block; the review's received set is the probe-scope brief's carried chain plus its F24/F26, F24 fixed at FINAL, F26 carried):

        From the brief under review, the still-open items copied verbatim (the chain through the probe-scope step's own carried set):

        F13 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
        The brief names the pin's red as "N consecutive grades of the known-good tree produce non-identical verdicts (PASS on one run, CANDIDATE_TIMEOUT on the next)". In this environment the known-good tree's `gate-check-tests` grade is stable well under the fixture's 60.0s deadline (ten pin runs, 50 grades, ~37–46s each, every grade PASS), so the pin passes at REV. The lottery's grade-flip needs a candidate whose suite fails — a failing tree's hypothesis tests shrink, and the shrinking varies the suite's wall — and the near-deadline flip is the neutralisation test's broken-source candidate (FAIL→CANDIDATE_TIMEOUT, 3/3 at REV). The pin's assertion and the seeded determinism are correct; the brief's stated candidate is simply not the one that flips here.
        FIXED: no regression test — an ORIGIN: BRIEF finding is fixed once a later committed brief corrects the text; the pin and the seed land as delivered.

        F14 (P2, ORIGIN: DOCUMENT, carried) — the F8 red evidence is load-borne and the implementer report does not say so; a later actor re-driving the red on an idle host sees green and may conclude the red is chimeric. Next action is the planner's: carry the load condition into the carried F8 block (or a later committed brief's correction), the seed and the pins stand as delivered.

        F15 (P2, ORIGIN: CODE, carried) — killed runs leak intermediate probe trees and no janitor reaps them; the shared tmpfs inode table filled to 3 free and the standing battery's first run died ENOSPC until 81 leaked trees were pruned by hand. Next action is the harness owner's (a tombstone/janitor keyed by the run identity) or a planner ruling that scratch hygiene is each session's duty.

        F16 (P2, ORIGIN: CODE, carried) — the seeded determinism is wall-bounded: at the fixture's 60.0s deadline the near-deadline candidate's seeded grade flips FAIL→CANDIDATE_TIMEOUT under host load (measured once mid-run and once at a 62.44s wall), so the pin's green determinism is stable-half evidence only. Next action is the fixture owner's: raise the grading deadline for near-deadline candidates (the 300.0 default gives a >=5x margin here) or an OWNER ruling that the deadline's load envelope is governed, not deterministic.

        F17 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
        The brief's boundary-fix instruction is internally inconsistent (FINDINGS, F17): the double-fork pin must leave no descendant alive after the exit while the F10 q1e boundary shape must survive the fix, and the two name one live shape (a session-escaped middleman spawning a session-escaped sleeper then exiting before the deadline, the sleeper adopted by init) that no container boundary can kill and spare at once. The GOAL reading was taken (F11/F12 fixed by the container boundary, both pins green at FINAL, no committed discriminating member changed verdict); the boundary this step retires is the named init-adopted orphan, and the new boundary is what the child never forked. Next action is the planner's: a later committed brief's text correction — the q1e-survival sentence, F12's "without also catching the documented boundary" clause, and the boundary sentence in the module docstring this step corrected in code.
        FIXED: no regression test — the reading is delivered in the work commit and its evidence is the two reds above and the FINAL battery above; the correction itself is a committed brief's prose, which has none.

        F21 | SEVERITY: P2 | ORIGIN: DOCUMENT | STATE: carried
        The implementer report's supervisor-module battery line records the module battery widened by the review module (`.venv/bin/python -m pytest tests/test_phase6_supervisor.py tests/test_review_phase6_supervisor.py --durations=5` — `15 passed in 17.72s`) and never the brief's documented form (`.venv/bin/python -m pytest tests/test_phase6_supervisor.py --durations=5`) with the documented form's own printed line. The wide form is a strict superset (the module's 13 pins plus the review module's 2 probes), green, and every figure it carries is its own printed line — nothing is evaded; but the brief's acceptance names the documented command, and the report's own template requires each claimed figure to name the command that actually ran while this acceptance line names both the documented form it did not run and the wide form it did. This review ran the documented form at FINAL — `13 passed in 12.46s` — so the figures stand; what carries is the report-text deviation from the brief's named battery.
        FIXED: no regression test — a document deviation in a committed report, which only a later step (or the planner's correction of the carried note) absorbs; the documented form's gate line is in this review's VERIFIED.

        F22 (P2, ORIGIN: BRIEF) — the brief's review-block copy of the carried F17 finding is truncated mid-sentence (the literal `(line truncated to 2000 chars)` marker), which rides as a carried text-correction to the planner.

        F23 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
        The brief's named red at REV is not reproducible — "at REV, with the delivered single-capture _kill, the racing forker's final tail forks plus the double-forked sleeper survive teardown adopted out-of-tree". In a NAMESPACE_V1 drive the workload is the PID-namespace init, _descendants always captures it (descendants=128 namespace_inits=[…]), and its SIGKILL makes the kernel reap the whole namespace (init death kills the namespace; measured: 124 live descendants after a weakened kill, 0 after the init dies), so the delivered _kill already leaves no descendant alive and the pin passes at REV. The sweep lands as the brief's requested defense-in-depth port and the pin as a regression pin; the named red is chimeric for the sandbox, and the load-borne leak F20 measured rode the nested-grading/oracle path, not a standing sandbox-drive race.
        FIXED: no regression test — an ORIGIN: BRIEF finding is fixed once a later committed brief corrects the text; the sweep and the pin land as delivered, and the pin's red class is the kill-surface mutant above.

        F26 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
        The repoint instruction names the assertion as "the assertion inverted (the carrier alive, the scoped scan empty)". The probe's old line is `assert carrier.pid in found`; the reading taken is its precise inverse, `assert carrier.pid not in found` (the scoped scan is empty *of the carrier*), with the carrier's liveness asserted beside it. The parenthetical also admits a literal whole-scan `assert not found` reading, which would red on any live workload survivor — the F1/F20 class the brief says stays with the pins — and would couple this host-side probe to unrelated host state, the over-match brittleness F24 is about. Next action is the planner's: a later committed brief's text correction naming the assertion form.
        FIXED: no regression test — an ORIGIN: BRIEF finding is fixed once a later committed brief corrects the text; the repoint lands as delivered (carrier-pid inversion) and is green at FINAL.

        Then each finding marked carried by this step, with its ID:

        F27 | SEVERITY: P2 | ORIGIN: CODE | STATE: carried (the seam's duplicated literal and the buried conjunction member — plan-shape drift silently kills the survivor pins' red class; see FINDINGS above; its next action is a later brief absorbing this review's two probes).

        F28 | SEVERITY: P2 | ORIGIN: DOCUMENT | STATE: carried (the report's docs-baseline claim falsified — pristine `12f1f83` prints 395; see FINDINGS above; its next action is the planner's correction of the carried note).

        F27 | SEVERITY: P2 | ORIGIN: CODE | STATE: carried
        The scoped scan's surface is a duplicated literal: `_PROBE_ARGV` (`tests/test_batch3_execution.py:184`) sits beside three independent plan `command` tuples (`:49`, `:231`, `:306`) and nothing holds them equal, while the named scoped-scan shape is split across the repointed carrier probe (carrier half) and the F1/F20 pins (survivor half) so no committed member asserts selectivity in one scan. Measured: plan-shape drift leaves every committed pin green while the scan undercounts — C1 (a second argv element in all three plan tuples) `13 passed in 4.04s`, C2 (the interpreter path moved to `/usr/bin/python3.13`) `13 passed in 3.90s`; and the drift silently destroys the pins' red class — C1 stacked with the weakened-capture mutant (that mutant alone reddens F1/F20 on `assert survivors == []`) goes `2 passed in 1.64s` over 123 live workload survivors whose argv carried the drifted shape (enumerated and reaped post-run; the pair-matching set empty throughout), leaking past the `finally` cleanups (`:244`, `:319`) that inherit the same blind scoping. The seam is one rule in form (no exclusion list, rule 13) but is keyed to a copy of the surface rather than to the surface the pins grade; the burial of the conjunction member is what lets the anchor drift stay invisible.
        FIXED: the machines this review commits: `tests/test_review_phase6_probe_scope.py::test_every_probe_plan_command_still_names_the_scanned_pair` (AST-parses the batch3 module and asserts every plan `command` tuple equals the scanned pair; green at HEAD `1 passed`, red on C1 with `At index 1 diff: '-u' != '/work/probe.py'` and on C2 the same class) and `tests/test_review_phase6_probe_scope.py::test_the_scoped_scan_counts_a_live_pair_holder_and_not_an_argv_carrier` (one scan over a live carrier and a live holder built from the plan's own `command`: green at HEAD `2 passed in 0.29s` for the module; red on the REV whole-table scan `assert carrier.pid not in found` — `the scoped scan counted an unrelated argv carrier: [3526004, 3526010, 3526011]` — and red on drift when the plan-built holder stops being counted). Next action is the planner's: a later brief absorbs these members into the pinned module (or pins the anchor its own way) — the drift class itself has no single node id at REV, its red is the mutant battery named above.

        F28 | SEVERITY: P2 | ORIGIN: DOCUMENT | STATE: carried
        The report's docs-baseline claim is falsified: "a pristine `12f1f83` extraction prints the same `396 Total`, so the brief's `395` baseline is not this step's" — the pristine `12f1f83` worktree prints `395 Total / 180 Unique / 395 OK / 0 Errors` (the brief's EXPECTED WALLS line, correct at drafting), and the 395→396 delta is exactly `docs/research/phase6-probe-scope-brief.md` added in the reviewed range (docs markdown count 160→161 across `git diff 12f1f83 14b6862 --stat -- docs/`, one path). The figure `396 Total … 0 Errors` is the gate's own printed line at FINAL and stands under rule 14 — what fails is the explanatory claim and its dismissal of a baseline that reproduces.
        FIXED: no regression test — a document deviation in a committed report, which only a later step (or the planner's correction of the carried note) absorbs; the measured correction is in this review's VERIFIED.

      Expected dispositions (rule 8 forms): F27 fixed with red evidence (named below — the anchor holds the copies equal or the conjunction member builds the selectivity in one scan, red on the drift class, green at FINAL). F28 stays carried (a document deviation in a committed report, absorbed only by a later step's correction). F11/F12/F18/F19/F20/F24/F25 stay fixed as recorded in the reports that filed them. F13–F17/F21–F23/F26 stay carried with their named owners and text corrections.

      Then each finding marked carried by this step, with its ID:

        F28 | SEVERITY: P2 | ORIGIN: DOCUMENT | STATE: carried (the report's docs-baseline claim falsified — pristine `12f1f83` prints 395; see FINDINGS above; its next action is the planner's correction of the carried note).

        F29 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried (the probe-absorption vs anchor reading — both members absorbed into the pinned module; see FINDINGS above; its next action is a later committed brief's text correction).

    From `docs/research/phase6-scan-anchor-review.md` — its `INHERITED` block's received F28/F29 dispositions only (the chain above is already carried verbatim through the scan-anchor implementer's INHERITED, and rule 2 governs the planner's copy of this block; the review's received set is the scan-anchor brief's carried F28 plus its F27/F29, F27 fixed at FINAL, F28/F29 carried):

      Expected dispositions of the received set (rule 8 forms), kept: received F27 fixed by this step (the one-source anchor plus both absorbed members, re-driven by this review — red at REV on the drift class, green at FINAL); F13-F23/F26 stay carried; F28 and F29 stay carried (each with its named next action); F11/F12/F18/F19/F20/F24/F25 stay fixed as recorded in the reports that filed them. Added by this review: none.

    Then each finding marked carried by this step, with its ID:

      F30 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried (the named red is chimeric as literally written and the GOAL's SIGKILL clause is not reachable inside `_run_probe` — the pin models the probe's sandbox root sibling, and the SIGKILL residue needs a cross-process janitor; see FINDINGS above; its next action is a later committed brief's text correction and the cross-process janitor F15's own next action names).

  From `docs/research/phase6-probe-janitor-review.md` — its `INHERITED` block's received F30/F31 dispositions only (the chain above is already carried verbatim through the probe-janitor implementer's INHERITED, and rule 2 governs the planner's copy of this block; the review's received set is the janitor brief's carried chain plus its F15/F30, F15 fixed at FINAL, F30 carried):

    Expected dispositions of the received set (rule 8 forms), kept: received F15 fixed by this step (the delivered registry plus finally-called reaper over the two trees and the sandbox root; the red the step names re-driven by this review on the REV scratch — `1 failed, 15 passed in 2.33s`, standing tree `orchestrator-probe-exec-…-root`, green at FINAL `16 passed in 2.03s`); F13/F14/F16/F17/F21–F23/F26/F28/F29 stay carried with their named owners and text corrections; F11/F12/F18/F19/F20/F24/F25/F27 stay fixed as recorded in the reports that filed them. Added by this review: F31, carried.

    F31 | SEVERITY: P2 | ORIGIN: DOCUMENT | STATE: carried
    The implementer report's SHAPES field claims "none" while its own F30 block records a probe the suite does not build: "Measured at REV: a probe that merely raises `KeyboardInterrupt` mid-grade is caught by `_run_probe`'s contained `BaseException` arm and the delivered `finally` already reaps both `mkdtemp` trees, so that pin passes at REV" — a probed shape (re-driven and confirmed by this review, `1 passed in 0.26s` on the REV scratch) with no committed member and no SHAPES entry, against the template's "SHAPES: none claims nothing probed is left unbuilt — never that unbuilt probes were left unnamed." Substantively harmless: the delivered pin's guard subsumes the merely-raising shape's red class — dropping the reap call or either registration line re-reds the delivered pin (mutants M1/M2 above), so the merely-raising shape catches nothing the committed pin does not.
    FIXED: no regression test — a document deviation in a committed report, which only a later step (or the planner's correction of the carried note) absorbs; the measured shape's drive is named in this review's VERIFIED and SHAPES.

  Expected dispositions (rule 8 forms): F16 fixed with red evidence (named below — the near-deadline grade is FAIL idle and FAIL under load, red on the 60.0s fixture deadline, green at FINAL). F28/F29/F30/F31 stay carried (document deviations in committed reports, absorbed only by later steps' corrections). F11/F12/F15/F18/F19/F20/F24/F25/F27 stay fixed as recorded in the reports that filed them. F13/F14/F17/F21–F23/F26 stay carried with their named owners and text corrections.

  Then each finding marked carried by this step, with its ID:

    F32 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried (the red clause's load regime; see FINDINGS above; its next action is a later committed brief's text correction, absorbed by F14's pending load-condition carry).

    F33 | SEVERITY: P2 | ORIGIN: DOCUMENT | STATE: carried (the report's docs-line file-count narrative; see FINDINGS above; its next action is the planner's correction of the carried note).

  Received-set dispositions kept: F16 fixed by this step (the delivered margin re-driven by this review: the fixture's own deadline is the seam — the `:215`/`:216` `60.0` literal removed, the delivered `300.0` default driving the manifest, the corpus/seed/N untouched — and the determinism-under-load pin red at REV on its FAIL-verdict assertion under the loaded regime, green at FINAL); F13/F14/F17/F21/F22/F23/F26/F28/F29/F30/F31 stay carried with their named owners and text corrections; F11/F12/F15/F18/F19/F20/F24/F25/F27 stay fixed as recorded in the reports that filed them. Added by this review: F32, F33, carried.
Then each finding marked carried by this step, with its ID: F13, F14, F17, F21, F22, F23, F26, F28, F29, F30, F31, F32, F33 (received carried, kept carried — this step touches neither the brief-text defects they name nor any code path they cite), and F1, F2 (filed by this report, carried — brief-text defects the planner's later committed correction fixes).

  Then each finding marked carried by this review, with its ID: F13, F14, F17, F21, F22, F23, F26, F28, F29, F30, F31, F32, F33 (received carried, kept carried — this review touched neither the brief-text defects they name nor any code path they cite), F1 and F2 (received carried from the implementer report's own filings — both re-verified in this review's VERIFIED: F1's reading reproduces its claimed check-scope line exactly and its two fields were finalized by `36e42a4` as the reading states; F2's code and record premises hold and the scan covered every store that exists; their next actions stay the planner's), and F3, F4 (filed by this review, carried — a document figure in a committed report and a commit-form lapse in the step's two commits; both absorbed only by later corrections).
