REPORT — harness-copying-fixture-seam-implementer
STEP: harness-copying-fixture-seam (route every fast-suite copying fixture spawn through the five-variable refusal seam; the copying fixture spawn becomes the pin)
REV: 360ba3fd62e2424053d5357be5d3befe445334cc   FINAL: 2de53712f13fadeb7d37e36d696b58c542a55b22
CHANGED: src/orchestrator/conformance.py — `_fixture_repo` builds its child environment through `worktree._git_environment(GIT_ENVIRONMENT)` instead of `{**os.environ, **GIT_ENVIRONMENT}`, and its follow-up `rev-parse HEAD` rides the same scrubbed copy. Fixture identity (names and fixed dates) is unchanged; the seam's `GIT_CONFIG_*`/`GIT_ATTR_NOSYSTEM`/`GIT_TERMINAL_PROMPT`/`GIT_OPTIONAL_LOCKS` base keys ride with it by construction (worktree's `GIT_ENVIRONMENT` is byte-identical).
CHANGED: tests/test_milestone3_acceptance.py — both copying spawns (`build_fixture_repo` and the hidden-tests member) route through `_git_environment(GIT_ENVIRONMENT)`; their `rev-parse HEAD` reads ride the same copy.
CHANGED: tests/test_milestone8_readiness.py — both copying spawns (`_fixture_repo_with_protected_content` and the kind-swap member) route through `_git_environment(GIT_ENVIRONMENT)`; their `rev-parse HEAD` reads ride the same copy.
CHANGED: tests/test_derive_obligations.py — `_repo_with` routes through `_git_environment(GIT_ENVIRONMENT)` (function-level imports, the read-path precedent).
CHANGED: tests/test_hook_env_scrub.py — two new committed members: `test_a_copying_fixture_spawn_refuses_the_five_variable_leak` (behavioral: drives `conformance._fixture_repo` under the faithful five-leak and asserts shared config/HEAD byte-identical, child `.git` present and returned commit its own) and `test_no_fast_suite_copying_fixture_merge_bypasses_the_seam` (source anchor: AST-scans the four fast-suite modules for a raw `os.environ` dict merge). The nine prior members are byte-identical and unweakened. The module docstring names the new lane.
VERIFIED: .venv/bin/python -m pytest tests/test_hook_env_scrub.py -q — exit 0, `11 passed in 0.58s` at FINAL (post-commit, working tree clean).
VERIFIED: .venv/bin/python -m pytest tests/test_hook_env_scrub.py -q --durations=5 — exit 0, `11 passed in 0.57s`. Slowest five: `0.06s call test_a_linked_worktree_leak_cannot_steer_read_children_into_another_tree`, `0.05s call test_no_fast_suite_copying_fixture_merge_bypasses_the_seam`, `0.04s call test_a_copying_fixture_spawn_refuses_the_five_variable_leak`, `0.04s call test_the_materialise_tar_fetch_refuses_a_diverting_parent`, `0.04s call test_a_linked_worktree_leak_cannot_move_a_fixture_child_outside_its_tmpdir`.
VERIFIED: red at REV on a byte-identical scratch (`git archive 360ba3f | tar -x -C /tmp/kilo/hcf-rev`; the four routed files `cmp`-verified against `git show 360ba3f:<path>` as REV-identical, and the FINAL pin file overlaid with `diff -q` identical): `.venv/bin/python -m pytest tests/test_hook_env_scrub.py -q -k "copying_fixture_spawn or bypasses_the_seam"` → `2 failed, 9 deselected in 0.23s`. The behavioral member reds at `AssertionError: the copying fixture's spawn steered the shared config outside its tmpdir` (the shared config gained `worktree = <linked path>`); the anchor reds naming the six raw merges (`src/orchestrator/conformance.py:82`, `tests/test_derive_obligations.py:37`, `tests/test_milestone3_acceptance.py:66` and `:491`, `tests/test_milestone8_readiness.py:51` and `:152`). The nine prior members stay green on the REV scratch (9 deselected for the targeted run; the module's full REV run is not claimed).
VERIFIED: green at FINAL — the same FINAL pin file against the FINAL tree: `11 passed in 0.58s` (above). Under the faithful five-leak the copying spawn refuses fail-closed: the child serves its own gitdir, its commit is its own, and the sentinel's shared config and HEAD are byte-identical.
VERIFIED: mutants on a FINAL-identical scratch (`/tmp/kilo/hcf-final`; all five changed files `cmp`-verified against `git show 2de5371:<path>`; each mutant copy reverts exactly one site and runs `.venv/bin/python -m pytest tests/test_hook_env_scrub.py -q` unless noted): M1 (conformance merge reverted to `{**os.environ, **GIT_ENVIRONMENT}`) → `2 failed, 9 passed in 0.61s`, behavioral member at the shared-config assertion and the anchor at `src/orchestrator/conformance.py:82`; M2 (only the conformance `rev-parse` `env=` removed, `.venv/bin/python -m pytest tests/test_hook_env_scrub.py -q -k copying_fixture_spawn`) → `1 failed, 10 deselected in 0.18s` at `AssertionError: the copying fixture returned another tree's commit: returned '27f12aa69193d72c3e148cf6b134112caa4e18ab' != child 'a4f68d72a72f803cd91090f925496f47d33e6901'`; M3 (derive merge reverted) → `1 failed, 10 passed in 0.64s` (anchor only); M4 (milestone-3 first merge reverted) → `1 failed, 10 passed in 0.45s` (anchor only); M5 (milestone-3 second merge reverted) → `1 failed, 10 passed in 0.45s` (anchor only); M6 (milestone-8 first merge reverted) → `1 failed, 10 passed in 0.45s` (anchor only); M7 (milestone-8 second merge reverted) → `1 failed, 10 passed in 0.47s` (anchor only). Each site is proved necessary; no prior member reddens under any mutant.
VERIFIED: scripts/check-tests --fast — exit 0, `1080 passed, 111 deselected in 91.74s (0:01:31)` (the gate's own printed line; +2 over the scrub-2 FINAL `1078/111` baseline is exactly this step's two new nodes). Slowest five (the gate prints its own): `8.75s call test_phase2_non_self_repository_runs_end_to_end`, `7.17s call test_patch_mode_never_batches_review_n7`, `6.54s call test_the_group_kill_reaches_the_grandchild_before_the_supervisor_exits`, `6.04s call test_unterminated_file_refuses_the_markerless_eof_reply_review_n2`, `5.81s call test_crlf_base_refuses_the_lf_context_reply_review_f1`.
VERIFIED: scripts/check-static — exit 0, gated `All checks passed!`, advisory `Found 104 errors.` (unchanged; the routing and the two new members add no advisory).
VERIFIED: scripts/check-docs — exit 0, `409 Total (in 940ms) 🔗 183 Unique ✅ 409 OK 🚫 0 Errors` (measured with this report in place; the research report file does not move the Total).
VERIFIED: scripts/check-scope 360ba3fd62e2424053d5357be5d3befe445334cc 2de53712f13fadeb7d37e36d696b58c542a55b22 docs/research/harness-copying-fixture-seam-brief.md — exit 0, `claimed: src/orchestrator/conformance.py tests/test_derive_obligations.py tests/test_hook_env_scrub.py tests/test_milestone3_acceptance.py tests/test_milestone8_readiness.py`, `tripped: none`, `scope: ok (6 path(s) in 360ba3f..2de5371)` (the sixth path is the brief itself, implicitly allowed under `docs/research/`).
VERIFIED: the main-tree commit path — the work commit `2de5371` was made through the REAL `scripts/hooks/pre-commit`: `Table verification passed.`, oracle internal gate `1046 passed in 26.39s`, sandbox tail `34 passed in 12.54s`, commit landed, exit 0.
NOT VERIFIED: the full standing battery `scripts/check-tests` (without `--fast`) — not driven; the falsification ground is the fast selection above. The three slow-marked `_GIT_ENV` copies are out of scope and not driven (named in SHAPES). The milestone-8 inline spawns have no separate behavioral drive (named in SHAPES); their routing is held by the anchor.
FINDINGS:
F1 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
R18's candidate shape — "`GIT_ENVIRONMENT` itself carries the refusal, so every copying fixture inherits the scrub" — cannot be built as literally worded: the fixture identity is a plain dict of names and dates, and a dict cannot drop ambient variables after the copy. The brief's measured alternative (unconditional empty values) fails clean callers (`env GIT_DIR= git -C <repo> rev-parse HEAD` → `fatal: not a git repository: ''`, rc 128), so the one consistent reading is seam routing: every in-scope fixture builds its child environment through `_git_environment(GIT_ENVIRONMENT)`, so the pop runs over the merged copy and clean callers are preserved. Next action is the planner's: a later committed brief's text correction names the reading taken (dict-carries-refusal vs seam routing).
F2 | SEVERITY: P2 | ORIGIN: CODE | STATE: fixed
The copying fixtures' follow-up `rev-parse HEAD` reads spawned without the scrubbed environment, so even with the merge routed the fixture returned another tree's commit under the faithful leak: `git -C <child> rev-parse HEAD` read the leaked `GIT_DIR` at the sentinel and returned the sentinel's `27f12aa…` while the child's own HEAD was `a4f68d7…`. All fixture-building `rev-parse` reads in the five in-scope files now ride the scrubbed copy.
FIXED: tests/test_hook_env_scrub.py::test_a_copying_fixture_spawn_refuses_the_five_variable_leak, `.venv/bin/python -m pytest tests/test_hook_env_scrub.py -q -k copying_fixture_spawn` on mutant M2 (FINAL tree with only the conformance `rev-parse` `env=` removed): `1 failed, 10 deselected in 0.18s` at `AssertionError: the copying fixture returned another tree's commit: returned '27f12aa69193d72c3e148cf6b134112caa4e18ab' != child 'a4f68d72a72f803cd91090f925496f47d33e6901'`; green at FINAL (`11 passed in 0.58s`).
FINDINGS note: the received set's dispositions are unchanged by this step; F1 is the brief-text reading the REVIEW asked to be filed, and F2 is the unseamed read surface this step's pin found and fixed. Nothing else was found open.
SHAPES: three shapes are named, none silently passed. (1) The three slow-marked `_GIT_ENV` copies (`tests/test_run_entry.py:71`/`:90`, `tests/test_phase5_run_entry_fixes_2_review.py:57`/`:74`, `tests/test_phase5_run_entry_fixes_4_review.py:26`/`:47`) still merge `{**os.environ, **_GIT_ENV}` and are deliberately out of scope; a faithful leak could steer them outside the fast suite and the oracle internal gate. Unbuilt: routing them is outside this brief's IN SCOPE; next action is a later brief's (or a slow-marked pin's) if the slow lanes are to inherit the refusal. (2) The milestone-8 inline spawns (`tests/test_milestone8_readiness.py:51` and `:152`) are routed and held by the source anchor, but no committed member behaviorally drives those two inline sequences (their surrounding tests need NAMESPACE_V1); unbuilt: a caller-level behavioral drive would need a module-level fixture helper. (3) The routed fixtures inherit the seam's base identity keys (`GIT_CONFIG_NOSYSTEM`, `GIT_CONFIG_GLOBAL`, `GIT_CONFIG_SYSTEM`, `GIT_ATTR_NOSYSTEM`, `GIT_TERMINAL_PROMPT`, `GIT_OPTIONAL_LOCKS`) in addition to their unchanged fixture names/dates; measured green at FINAL on the two pin members and the fast suite, with no committed member asserting the exact child key set.
SHAPES note: nothing else was probed. The two built members red at REV and green at FINAL with per-site mutant proof above; the nine prior members are byte-identical and green.
TRIPPED: none
PROPOSED ROWS: none
METHOD FRICTION: none
INHERITED:
INHERITED note: what follows is the brief's `INHERITED:` block copied verbatim (the planner's mechanical copy of `docs/research/harness-hook-env-scrub-2-implementer.md`'s block plus that delivery's own FINDINGS/SHAPES dispositions), then the one finding this step carries forward.
<<copy every prior report's INHERITED block, in order, verbatim — at minimum the full INHERITED block of docs/research/harness-hook-env-scrub-2-implementer.md (from its `INHERITED:` line) plus that delivery's own FINDINGS/SHAPES dispositions; the planner pastes them at dispatch from that file, not from any summary. Still open per that file's own dispositions (FINDINGS lines 19-26, SHAPES line 27): scrub F1 fixed before this step (gitops seam, re-verified at scrub-2 FINAL) and scrub-review F4 fixed before this step (absorption member, re-verified) — neither carries from any step; scrub F2 (P2, BRIEF — the disposable-worktree ordering ambiguity) carried; scrub-review F3 (P2, BRIEF — the review FOCUS parenthetical) carried; F13–F17, F21–F23, F26, F28–F33 carried with their named owners and text corrections; and the copying-fixture steering shape unbuilt (fixed by this step). Nothing else is open: F11/F12/F15/F18/F19/F20/F24/F25/F27 stay fixed as recorded in the reports that filed them (per the same disposition lines).>>
  INHERITED:
  From `docs/research/phase7-shadow-tag-universe-implementer.md`, its `INHERITED` block verbatim:

  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).

    From `docs/research/phase6-exit-gate-runs-review.md`, its `INHERITED` block verbatim:

    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).

  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 edits one informative Status paragraph and touches neither the brief-text defects they name nor any code path they cite). Received-set dispositions kept: F16 fixed by the report that filed it (the deadline-margin review's delivered margin); F11/F12/F15/F18/F19/F20/F24/F25/F27 stay fixed as recorded in the reports that filed them; F1/F2/F3/F4 remain closed actionless by the R15 closeout (`docs/record.md`, the row above).

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

    INHERITED:
    From `docs/research/phase6-deadline-margin-review.md` (the exit-gate-runs chain's carried set, the review brief's INHERITED as received — the chain's carried blocks verbatim), the still-open findings, each with its block as the brief moves it:

      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).

      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).

    From `docs/research/phase6-exit-gate-runs-review.md`, its find-blocks' received-carried items verbatim (the chain's F1/F2 are the exit-gate-runs implementer report's filings; F3/F4 its review's filings — all carried, none with an action a step of this chain has taken yet):
      F1 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
      The brief's CONTEXT and RESIDUALS make the report commit the step's content commit and say `FINAL` names it, but the template also requires the report to paste the `check-scope` line, whose range carries `FINAL`'s sha — a sha that cannot be known before the commit that carries the report exists, and cannot be written into that commit's own tree (a fixed point). A one-commit realization is impossible.
      FIXED: no regression test — a committed brief's prose has none. Reading taken: the commit that first carries the report is `FINAL`; the report's two self-referential fields (`FINAL`'s value in the header and the `check-scope` VERIFIED line's range) are finalized in the immediately following commit, so `scripts/check-scope c418342 <FINAL> docs/research/phase6-exit-gate-runs-brief.md` reproduces the report's pasted line exactly against `FINAL`. Next action is the planner's: a later committed brief's text correction (rule 8's form) — this step delivers the reading and cannot correct the brief itself.
      F2 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
      The brief's step-3 store list names "the debug transcript" among the stores to scan, and `docs/record.md`'s campaign paragraph says the scan includes it, but the contract's "export exactly these" block omits `ORCHESTRATOR_DEBUG_TRANSCRIPT`, so the transcript (opt-in, default off; `resolve_transcript_path` returns `""` and nothing is written) does not exist for this run.
      FIXED: no regression test — a committed brief's text has none. Reading taken: the contract's exact export list governs, and the scan covers every store present (the transcript's absence is the contract's own omission, not a scan gap — the secret is proven absent from every file that exists). Next action is the planner's: align step 3's store list with the contract (or add the export if the transcript is wanted scanned).
      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.

    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); the exit-gate-runs chain's F1, F2 (received carried, kept carried — re-verified in the exit-gate-runs review's own VERIFIED and their premises unchanged here); its F3, F4 (received carried, kept carried — the trailer lapse its F4 filed recurs in this step's two commits as this report's own F1, and the six-vs-seven figure stands as re-derived); and this report's F1, F2, F3, F4 (filed by this review, carried — a commit-form lapse in the step's two commits, a battery-member scan-coupling in the janitor pin, a falsified hash cell in the exit-gate-runs Record row, and the brief's mandated "stores" noun — each with its named next action).

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

  From the review brief `docs/research/phase6-janitor-window-review-brief.md` — its INHERITED block's still-open copy, taken verbatim: the exit-gate-runs chain's carried set as the closeout-status review's INHERITED presents it (the chain's carried blocks verbatim), then the exit-gate-runs find-blocks and that review's own carry line, as the brief moves them:
      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).

      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).

    From `docs/research/phase6-exit-gate-runs-review.md`, its find-blocks' received-carried items verbatim (the chain's F1/F2 are the exit-gate-runs implementer report's filings; F3/F4 its review's filings — all carried, none with an action a step of this chain has taken yet):
      F1 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
      The brief's CONTEXT and RESIDUALS make the report commit the step's content commit and say `FINAL` names it, but the template also requires the report to paste the `check-scope` line, whose range carries `FINAL`'s sha — a sha that cannot be known before the commit that carries the report exists, and cannot be written into that commit's own tree (a fixed point). A one-commit realization is impossible.
      FIXED: no regression test — a committed brief's prose has none. Reading taken: the commit that first carries the report is `FINAL`; the report's two self-referential fields (`FINAL`'s value in the header and the `check-scope` VERIFIED line's range) are finalized in the immediately following commit, so `scripts/check-scope c418342 <FINAL> docs/research/phase6-exit-gate-runs-brief.md` reproduces the report's pasted line exactly against `FINAL`. Next action is the planner's: a later committed brief's text correction (rule 8's form) — this step delivers the reading and cannot correct the brief itself.
      F2 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
      The brief's step-3 store list names "the debug transcript" among the stores to scan, and `docs/record.md`'s campaign paragraph says the scan includes it, but the contract's "export exactly these" block omits `ORCHESTRATOR_DEBUG_TRANSCRIPT`, so the transcript (opt-in, default off; `resolve_transcript_path` returns `""` and nothing is written) does not exist for this run.
      FIXED: no regression test — a committed brief's text has none. Reading taken: the contract's exact export list governs, and the scan covers every store present (the transcript's absence is the contract's own omission, not a scan gap — the secret is proven absent from every file that exists). Next action is the planner's: align step 3's store list with the contract (or add the export if the transcript is wanted scanned).
      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.

    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); the exit-gate-runs chain's F1, F2 (received carried, kept carried — re-verified in the exit-gate-runs review's own VERIFIED and their premises unchanged here); its F3, F4 (received carried, kept carried — the trailer lapse its F4 filed recurs in this step's two commits as this report's own F1, and the six-vs-seven figure stands as re-derived); and this report's F1, F2, F3, F4 (filed by this review, carried — a commit-form lapse in the step's two commits, a battery-member scan-coupling in the janitor pin, a falsified hash cell in the exit-gate-runs Record row, and the brief's mandated "stores" noun — each with its named next action).

  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); the exit-gate-runs chain's F1, F2 (received carried, kept carried — both re-verified in the exit-gate-runs review's own VERIFIED, their premises unchanged here: this review's step touched neither the report fields they describe nor the store-scan contract they govern, and the delivered pin's re-scope touches only the battery member's window); and F3, F4 (received carried, kept carried — the six-vs-seven figure stands as re-derived by its own review and was closed actionless only by name, the substance waiting on the planner's carried-note correction; F4's premise extends: the planner's brief for this step, `e9a37db`, also carries no `Actor:` trailer — the sixth consecutive trailerless commit in the backlog F4 filed — while this step's own two commits under review (`a14afb2`, `819ddde`) carry their `Actor: IMPLEMENTER` trailer as that discipline asks).

  The one fixing absorption this chain took: the closeout-status review's F2 — the janitor pin's whole-`gettempdir()` scan coupling, whose row cell named "a later brief's re-scope or serial-set move" — is fixed by this step: the later brief (`e9a37db`) took the re-scope reading and the implementer delivered it (its own F2, fixed with red evidence), re-driven red at REV and green at FINAL by this review (VERIFIED above). The closeout-status review's F1 (its step's trailer lapse), F3 (the exit-gate-runs REV-cell hash, corrected in the closeout write itself) and F4 (the "2326 stores" noun, corrected in the same write) remain closed actionless as the closeout row records them.

  Received-set dispositions kept: F16 fixed by the report that filed it (the deadline-margin review's delivered margin, its red re-driven there); the closeout-status review's F2 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/F32/F33 stay carried with their named owners and text corrections; the exit-gate-runs chain's F1–F4 stay carried with their named planner next actions.

  Then each finding marked carried by this step, with its ID:
  F1 (P1, ORIGIN: CODE, carried) — the pre-commit hook's inherited `GIT_DIR` corrupts a linked-worktree branch and the shared config; next action is the harness owner's (see FINDINGS).
  F2 (P2, ORIGIN: BRIEF, carried) — the bare non-specific `!` reading under "every non-plain tag"; next action is the planner's (see FINDINGS).


  From `docs/research/phase7-shadow-tag-universe-review.md`, its `INHERITED` block verbatim:

  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).

    From `docs/research/phase6-exit-gate-runs-review.md`, its `INHERITED` block verbatim:

    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).

  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 edits one informative Status paragraph and touches neither the brief-text defects they name nor any code path they cite). Received-set dispositions kept: F16 fixed by the report that filed it (the deadline-margin review's delivered margin); F11/F12/F15/F18/F19/F20/F24/F25/F27 stay fixed as recorded in the reports that filed them; F1/F2/F3/F4 remain closed actionless by the R15 closeout (`docs/record.md`, the row above).

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

    INHERITED:
    From `docs/research/phase6-deadline-margin-review.md` (the exit-gate-runs chain's carried set, the review brief's INHERITED as received — the chain's carried blocks verbatim), the still-open findings, each with its block as the brief moves it:

      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).

      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).

    From `docs/research/phase6-exit-gate-runs-review.md`, its find-blocks' received-carried items verbatim (the chain's F1/F2 are the exit-gate-runs implementer report's filings; F3/F4 its review's filings — all carried, none with an action a step of this chain has taken yet):
      F1 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
      The brief's CONTEXT and RESIDUALS make the report commit the step's content commit and say `FINAL` names it, but the template also requires the report to paste the `check-scope` line, whose range carries `FINAL`'s sha — a sha that cannot be known before the commit that carries the report exists, and cannot be written into that commit's own tree (a fixed point). A one-commit realization is impossible.
      FIXED: no regression test — a committed brief's prose has none. Reading taken: the commit that first carries the report is `FINAL`; the report's two self-referential fields (`FINAL`'s value in the header and the `check-scope` VERIFIED line's range) are finalized in the immediately following commit, so `scripts/check-scope c418342 <FINAL> docs/research/phase6-exit-gate-runs-brief.md` reproduces the report's pasted line exactly against `FINAL`. Next action is the planner's: a later committed brief's text correction (rule 8's form) — this step delivers the reading and cannot correct the brief itself.
      F2 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
      The brief's step-3 store list names "the debug transcript" among the stores to scan, and `docs/record.md`'s campaign paragraph says the scan includes it, but the contract's "export exactly these" block omits `ORCHESTRATOR_DEBUG_TRANSCRIPT`, so the transcript (opt-in, default off; `resolve_transcript_path` returns `""` and nothing is written) does not exist for this run.
      FIXED: no regression test — a committed brief's text has none. Reading taken: the contract's exact export list governs, and the scan covers every store present (the transcript's absence is the contract's own omission, not a scan gap — the secret is proven absent from every file that exists). Next action is the planner's: align step 3's store list with the contract (or add the export if the transcript is wanted scanned).
      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.

    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); the exit-gate-runs chain's F1, F2 (received carried, kept carried — re-verified in the exit-gate-runs review's own VERIFIED and their premises unchanged here); its F3, F4 (received carried, kept carried — the trailer lapse its F4 filed recurs in this step's two commits as this report's own F1, and the six-vs-seven figure stands as re-derived); and this report's F1, F2, F3, F4 (filed by this review, carried — a commit-form lapse in the step's two commits, a battery-member scan-coupling in the janitor pin, a falsified hash cell in the exit-gate-runs Record row, and the brief's mandated "stores" noun — each with its named next action).

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

  From the review brief `docs/research/phase6-janitor-window-review-brief.md` — its INHERITED block's still-open copy, taken verbatim: the exit-gate-runs chain's carried set as the closeout-status review's INHERITED presents it (the chain's carried blocks verbatim), then the exit-gate-runs find-blocks and that review's own carry line, as the brief moves them:
      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).

      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).

    From `docs/research/phase6-exit-gate-runs-review.md`, its find-blocks' received-carried items verbatim (the chain's F1/F2 are the exit-gate-runs implementer report's filings; F3/F4 its review's filings — all carried, none with an action a step of this chain has taken yet):
      F1 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
      The brief's CONTEXT and RESIDUALS make the report commit the step's content commit and say `FINAL` names it, but the template also requires the report to paste the `check-scope` line, whose range carries `FINAL`'s sha — a sha that cannot be known before the commit that carries the report exists, and cannot be written into that commit's own tree (a fixed point). A one-commit realization is impossible.
      FIXED: no regression test — a committed brief's prose has none. Reading taken: the commit that first carries the report is `FINAL`; the report's two self-referential fields (`FINAL`'s value in the header and the `check-scope` VERIFIED line's range) are finalized in the immediately following commit, so `scripts/check-scope c418342 <FINAL> docs/research/phase6-exit-gate-runs-brief.md` reproduces the report's pasted line exactly against `FINAL`. Next action is the planner's: a later committed brief's text correction (rule 8's form) — this step delivers the reading and cannot correct the brief itself.
      F2 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
      The brief's step-3 store list names "the debug transcript" among the stores to scan, and `docs/record.md`'s campaign paragraph says the scan includes it, but the contract's "export exactly these" block omits `ORCHESTRATOR_DEBUG_TRANSCRIPT`, so the transcript (opt-in, default off; `resolve_transcript_path` returns `""` and nothing is written) does not exist for this run.
      FIXED: no regression test — a committed brief's text has none. Reading taken: the contract's exact export list governs, and the scan covers every store present (the transcript's absence is the contract's own omission, not a scan gap — the secret is proven absent from every file that exists). Next action is the planner's: align step 3's store list with the contract (or add the export if the transcript is wanted scanned).
      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.

    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); the exit-gate-runs chain's F1, F2 (received carried, kept carried — re-verified in the exit-gate-runs review's own VERIFIED and their premises unchanged here); its F3, F4 (received carried, kept carried — the trailer lapse its F4 filed recurs in this step's two commits as this report's own F1, and the six-vs-seven figure stands as re-derived); and this report's F1, F2, F3, F4 (filed by this review, carried — a commit-form lapse in the step's two commits, a battery-member scan-coupling in the janitor pin, a falsified hash cell in the exit-gate-runs Record row, and the brief's mandated "stores" noun — each with its named next action).

  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); the exit-gate-runs chain's F1, F2 (received carried, kept carried — both re-verified in the exit-gate-runs review's own VERIFIED, their premises unchanged here: this review's step touched neither the report fields they describe nor the store-scan contract they govern, and the delivered pin's re-scope touches only the battery member's window); and F3, F4 (received carried, kept carried — the six-vs-seven figure stands as re-derived by its own review and was closed actionless only by name, the substance waiting on the planner's carried-note correction; F4's premise extends: the planner's brief for this step, `e9a37db`, also carries no `Actor:` trailer — the sixth consecutive trailerless commit in the backlog F4 filed — while this step's own two commits under review (`a14afb2`, `819ddde`) carry their `Actor: IMPLEMENTER` trailer as that discipline asks).

  The one fixing absorption this chain took: the closeout-status review's F2 — the janitor pin's whole-`gettempdir()` scan coupling, whose row cell named "a later brief's re-scope or serial-set move" — is fixed by this step: the later brief (`e9a37db`) took the re-scope reading and the implementer delivered it (its own F2, fixed with red evidence), re-driven red at REV and green at FINAL by this review (VERIFIED above). The closeout-status review's F1 (its step's trailer lapse), F3 (the exit-gate-runs REV-cell hash, corrected in the closeout write itself) and F4 (the "2326 stores" noun, corrected in the same write) remain closed actionless as the closeout row records them.

  Received-set dispositions kept: F16 fixed by the report that filed it (the deadline-margin review's delivered margin, its red re-driven there); the closeout-status review's F2 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/F32/F33 stay carried with their named owners and text corrections; the exit-gate-runs chain's F1–F4 stay carried with their named planner next actions.

  Then each finding marked carried by this step, with its ID:
  F1 (P1, ORIGIN: CODE, carried) — the pre-commit hook's inherited `GIT_DIR` corrupts a linked-worktree branch and the shared config; next action is the harness owner's (see FINDINGS).
  F2 (P2, ORIGIN: BRIEF, carried) — the bare non-specific `!` reading under "every non-plain tag"; next action is the planner's (see FINDINGS).

    Then each finding marked carried by this review, with its ID:
    F3 (P2, ORIGIN: CODE, carried) — the spilled `GIT_CONFIG_PARAMETERS` in the hook environment extends F1's scrub set; next action is the harness owner's, with F1 (see FINDINGS).
  Then each finding marked carried by this step, with its ID:
  F1 (P2, ORIGIN: CODE, carried) — src/orchestrator/git_ops.py's `_git` bypasses the `_git_environment` seam and still inherits the five; out of IN SCOPE (see FINDINGS).
  F2 (P2, ORIGIN: BRIEF, carried) — the "removes it before committing" ordering; the reading taken is that the disposable linked worktree is the commit-path verification drive (see FINDINGS).

  --- harness-hook-env-scrub-review INHERITED verbatim (its own received chain, per the brief order) ---

  INHERITED:
    From `docs/research/phase7-shadow-tag-universe-implementer.md`, its `INHERITED` block verbatim:

    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).

      From `docs/research/phase6-exit-gate-runs-review.md`, its `INHERITED` block verbatim:

      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).

    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 edits one informative Status paragraph and touches neither the brief-text defects they name nor any code path they cite). Received-set dispositions kept: F16 fixed by the report that filed it (the deadline-margin review's delivered margin); F11/F12/F15/F18/F19/F20/F24/F25/F27 stay fixed as recorded in the reports that filed them; F1/F2/F3/F4 remain closed actionless by the R15 closeout (`docs/record.md`, the row above).

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

      INHERITED:
      From `docs/research/phase6-deadline-margin-review.md` (the exit-gate-runs chain's carried set, the review brief's INHERITED as received — the chain's carried blocks verbatim), the still-open findings, each with its block as the brief moves it:

        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).

        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).

      From `docs/research/phase6-exit-gate-runs-review.md`, its find-blocks' received-carried items verbatim (the chain's F1/F2 are the exit-gate-runs implementer report's filings; F3/F4 its review's filings — all carried, none with an action a step of this chain has taken yet):
        F1 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
        The brief's CONTEXT and RESIDUALS make the report commit the step's content commit and say `FINAL` names it, but the template also requires the report to paste the `check-scope` line, whose range carries `FINAL`'s sha — a sha that cannot be known before the commit that carries the report exists, and cannot be written into that commit's own tree (a fixed point). A one-commit realization is impossible.
        FIXED: no regression test — a committed brief's prose has none. Reading taken: the commit that first carries the report is `FINAL`; the report's two self-referential fields (`FINAL`'s value in the header and the `check-scope` VERIFIED line's range) are finalized in the immediately following commit, so `scripts/check-scope c418342 <FINAL> docs/research/phase6-exit-gate-runs-brief.md` reproduces the report's pasted line exactly against `FINAL`. Next action is the planner's: a later committed brief's text correction (rule 8's form) — this step delivers the reading and cannot correct the brief itself.
        F2 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
        The brief's step-3 store list names "the debug transcript" among the stores to scan, and `docs/record.md`'s campaign paragraph says the scan includes it, but the contract's "export exactly these" block omits `ORCHESTRATOR_DEBUG_TRANSCRIPT`, so the transcript (opt-in, default off; `resolve_transcript_path` returns `""` and nothing is written) does not exist for this run.
        FIXED: no regression test — a committed brief's text has none. Reading taken: the contract's exact export list governs, and the scan covers every store present (the transcript's absence is the contract's own omission, not a scan gap — the secret is proven absent from every file that exists). Next action is the planner's: align step 3's store list with the contract (or add the export if the transcript is wanted scanned).
        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.

      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); the exit-gate-runs chain's F1, F2 (received carried, kept carried — re-verified in the exit-gate-runs review's own VERIFIED and their premises unchanged here); its F3, F4 (received carried, kept carried — the trailer lapse its F4 filed recurs in this step's two commits as this report's own F1, and the six-vs-seven figure stands as re-derived); and this report's F1, F2, F3, F4 (filed by this review, carried — a commit-form lapse in the step's two commits, a battery-member scan-coupling in the janitor pin, a falsified hash cell in the exit-gate-runs Record row, and the brief's mandated "stores" noun — each with its named next action).

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

    From the review brief `docs/research/phase6-janitor-window-review-brief.md` — its INHERITED block's still-open copy, taken verbatim: the exit-gate-runs chain's carried set as the closeout-status review's INHERITED presents it (the chain's carried blocks verbatim), then the exit-gate-runs find-blocks and that review's own carry line, as the brief moves them:
        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).

        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).

      From `docs/research/phase6-exit-gate-runs-review.md`, its find-blocks' received-carried items verbatim (the chain's F1/F2 are the exit-gate-runs implementer report's filings; F3/F4 its review's filings — all carried, none with an action a step of this chain has taken yet):
        F1 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
        The brief's CONTEXT and RESIDUALS make the report commit the step's content commit and say `FINAL` names it, but the template also requires the report to paste the `check-scope` line, whose range carries `FINAL`'s sha — a sha that cannot be known before the commit that carries the report exists, and cannot be written into that commit's own tree (a fixed point). A one-commit realization is impossible.
        FIXED: no regression test — a committed brief's prose has none. Reading taken: the commit that first carries the report is `FINAL`; the report's two self-referential fields (`FINAL`'s value in the header and the `check-scope` VERIFIED line's range) are finalized in the immediately following commit, so `scripts/check-scope c418342 <FINAL> docs/research/phase6-exit-gate-runs-brief.md` reproduces the report's pasted line exactly against `FINAL`. Next action is the planner's: a later committed brief's text correction (rule 8's form) — this step delivers the reading and cannot correct the brief itself.
        F2 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
        The brief's step-3 store list names "the debug transcript" among the stores to scan, and `docs/record.md`'s campaign paragraph says the scan includes it, but the contract's "export exactly these" block omits `ORCHESTRATOR_DEBUG_TRANSCRIPT`, so the transcript (opt-in, default off; `resolve_transcript_path` returns `""` and nothing is written) does not exist for this run.
        FIXED: no regression test — a committed brief's text has none. Reading taken: the contract's exact export list governs, and the scan covers every store present (the transcript's absence is the contract's own omission, not a scan gap — the secret is proven absent from every file that exists). Next action is the planner's: align step 3's store list with the contract (or add the export if the transcript is wanted scanned).
        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.

      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); the exit-gate-runs chain's F1, F2 (received carried, kept carried — re-verified in the exit-gate-runs review's own VERIFIED and their premises unchanged here); its F3, F4 (received carried, kept carried — the trailer lapse its F4 filed recurs in this step's two commits as this report's own F1, and the six-vs-seven figure stands as re-derived); and this report's F1, F2, F3, F4 (filed by this review, carried — a commit-form lapse in the step's two commits, a battery-member scan-coupling in the janitor pin, a falsified hash cell in the exit-gate-runs Record row, and the brief's mandated "stores" noun — each with its named next action).

    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); the exit-gate-runs chain's F1, F2 (received carried, kept carried — both re-verified in the exit-gate-runs review's own VERIFIED, their premises unchanged here: this review's step touched neither the report fields they describe nor the store-scan contract they govern, and the delivered pin's re-scope touches only the battery member's window); and F3, F4 (received carried, kept carried — the six-vs-seven figure stands as re-derived by its own review and was closed actionless only by name, the substance waiting on the planner's carried-note correction; F4's premise extends: the planner's brief for this step, `e9a37db`, also carries no `Actor:` trailer — the sixth consecutive trailerless commit in the backlog F4 filed — while this step's own two commits under review (`a14afb2`, `819ddde`) carry their `Actor: IMPLEMENTER` trailer as that discipline asks).

    The one fixing absorption this chain took: the closeout-status review's F2 — the janitor pin's whole-`gettempdir()` scan coupling, whose row cell named "a later brief's re-scope or serial-set move" — is fixed by this step: the later brief (`e9a37db`) took the re-scope reading and the implementer delivered it (its own F2, fixed with red evidence), re-driven red at REV and green at FINAL by this review (VERIFIED above). The closeout-status review's F1 (its step's trailer lapse), F3 (the exit-gate-runs REV-cell hash, corrected in the closeout write itself) and F4 (the "2326 stores" noun, corrected in the same write) remain closed actionless as the closeout row records them.

    Received-set dispositions kept: F16 fixed by the report that filed it (the deadline-margin review's delivered margin, its red re-driven there); the closeout-status review's F2 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/F32/F33 stay carried with their named owners and text corrections; the exit-gate-runs chain's F1–F4 stay carried with their named planner next actions.

    Then each finding marked carried by this step, with its ID:
    F1 (P1, ORIGIN: CODE, carried) — the pre-commit hook's inherited `GIT_DIR` corrupts a linked-worktree branch and the shared config; next action is the harness owner's (see FINDINGS).
    F2 (P2, ORIGIN: BRIEF, carried) — the bare non-specific `!` reading under "every non-plain tag"; next action is the planner's (see FINDINGS).


    From `docs/research/phase7-shadow-tag-universe-review.md`, its `INHERITED` block verbatim:

    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).

      From `docs/research/phase6-exit-gate-runs-review.md`, its `INHERITED` block verbatim:

      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).

    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 edits one informative Status paragraph and touches neither the brief-text defects they name nor any code path they cite). Received-set dispositions kept: F16 fixed by the report that filed it (the deadline-margin review's delivered margin); F11/F12/F15/F18/F19/F20/F24/F25/F27 stay fixed as recorded in the reports that filed them; F1/F2/F3/F4 remain closed actionless by the R15 closeout (`docs/record.md`, the row above).

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

      INHERITED:
      From `docs/research/phase6-deadline-margin-review.md` (the exit-gate-runs chain's carried set, the review brief's INHERITED as received — the chain's carried blocks verbatim), the still-open findings, each with its block as the brief moves it:

        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).

        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).

      From `docs/research/phase6-exit-gate-runs-review.md`, its find-blocks' received-carried items verbatim (the chain's F1/F2 are the exit-gate-runs implementer report's filings; F3/F4 its review's filings — all carried, none with an action a step of this chain has taken yet):
        F1 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
        The brief's CONTEXT and RESIDUALS make the report commit the step's content commit and say `FINAL` names it, but the template also requires the report to paste the `check-scope` line, whose range carries `FINAL`'s sha — a sha that cannot be known before the commit that carries the report exists, and cannot be written into that commit's own tree (a fixed point). A one-commit realization is impossible.
        FIXED: no regression test — a committed brief's prose has none. Reading taken: the commit that first carries the report is `FINAL`; the report's two self-referential fields (`FINAL`'s value in the header and the `check-scope` VERIFIED line's range) are finalized in the immediately following commit, so `scripts/check-scope c418342 <FINAL> docs/research/phase6-exit-gate-runs-brief.md` reproduces the report's pasted line exactly against `FINAL`. Next action is the planner's: a later committed brief's text correction (rule 8's form) — this step delivers the reading and cannot correct the brief itself.
        F2 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
        The brief's step-3 store list names "the debug transcript" among the stores to scan, and `docs/record.md`'s campaign paragraph says the scan includes it, but the contract's "export exactly these" block omits `ORCHESTRATOR_DEBUG_TRANSCRIPT`, so the transcript (opt-in, default off; `resolve_transcript_path` returns `""` and nothing is written) does not exist for this run.
        FIXED: no regression test — a committed brief's text has none. Reading taken: the contract's exact export list governs, and the scan covers every store present (the transcript's absence is the contract's own omission, not a scan gap — the secret is proven absent from every file that exists). Next action is the planner's: align step 3's store list with the contract (or add the export if the transcript is wanted scanned).
        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.

      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); the exit-gate-runs chain's F1, F2 (received carried, kept carried — re-verified in the exit-gate-runs review's own VERIFIED and their premises unchanged here); its F3, F4 (received carried, kept carried — the trailer lapse its F4 filed recurs in this step's two commits as this report's own F1, and the six-vs-seven figure stands as re-derived); and this report's F1, F2, F3, F4 (filed by this review, carried — a commit-form lapse in the step's two commits, a battery-member scan-coupling in the janitor pin, a falsified hash cell in the exit-gate-runs Record row, and the brief's mandated "stores" noun — each with its named next action).

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

    From the review brief `docs/research/phase6-janitor-window-review-brief.md` — its INHERITED block's still-open copy, taken verbatim: the exit-gate-runs chain's carried set as the closeout-status review's INHERITED presents it (the chain's carried blocks verbatim), then the exit-gate-runs find-blocks and that review's own carry line, as the brief moves them:
        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).

        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).

      From `docs/research/phase6-exit-gate-runs-review.md`, its find-blocks' received-carried items verbatim (the chain's F1/F2 are the exit-gate-runs implementer report's filings; F3/F4 its review's filings — all carried, none with an action a step of this chain has taken yet):
        F1 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
        The brief's CONTEXT and RESIDUALS make the report commit the step's content commit and say `FINAL` names it, but the template also requires the report to paste the `check-scope` line, whose range carries `FINAL`'s sha — a sha that cannot be known before the commit that carries the report exists, and cannot be written into that commit's own tree (a fixed point). A one-commit realization is impossible.
        FIXED: no regression test — a committed brief's prose has none. Reading taken: the commit that first carries the report is `FINAL`; the report's two self-referential fields (`FINAL`'s value in the header and the `check-scope` VERIFIED line's range) are finalized in the immediately following commit, so `scripts/check-scope c418342 <FINAL> docs/research/phase6-exit-gate-runs-brief.md` reproduces the report's pasted line exactly against `FINAL`. Next action is the planner's: a later committed brief's text correction (rule 8's form) — this step delivers the reading and cannot correct the brief itself.
        F2 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
        The brief's step-3 store list names "the debug transcript" among the stores to scan, and `docs/record.md`'s campaign paragraph says the scan includes it, but the contract's "export exactly these" block omits `ORCHESTRATOR_DEBUG_TRANSCRIPT`, so the transcript (opt-in, default off; `resolve_transcript_path` returns `""` and nothing is written) does not exist for this run.
        FIXED: no regression test — a committed brief's text has none. Reading taken: the contract's exact export list governs, and the scan covers every store present (the transcript's absence is the contract's own omission, not a scan gap — the secret is proven absent from every file that exists). Next action is the planner's: align step 3's store list with the contract (or add the export if the transcript is wanted scanned).
        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.

      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); the exit-gate-runs chain's F1, F2 (received carried, kept carried — re-verified in the exit-gate-runs review's own VERIFIED and their premises unchanged here); its F3, F4 (received carried, kept carried — the trailer lapse its F4 filed recurs in this step's two commits as this report's own F1, and the six-vs-seven figure stands as re-derived); and this report's F1, F2, F3, F4 (filed by this review, carried — a commit-form lapse in the step's two commits, a battery-member scan-coupling in the janitor pin, a falsified hash cell in the exit-gate-runs Record row, and the brief's mandated "stores" noun — each with its named next action).

    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); the exit-gate-runs chain's F1, F2 (received carried, kept carried — both re-verified in the exit-gate-runs review's own VERIFIED, their premises unchanged here: this review's step touched neither the report fields they describe nor the store-scan contract they govern, and the delivered pin's re-scope touches only the battery member's window); and F3, F4 (received carried, kept carried — the six-vs-seven figure stands as re-derived by its own review and was closed actionless only by name, the substance waiting on the planner's carried-note correction; F4's premise extends: the planner's brief for this step, `e9a37db`, also carries no `Actor:` trailer — the sixth consecutive trailerless commit in the backlog F4 filed — while this step's own two commits under review (`a14afb2`, `819ddde`) carry their `Actor: IMPLEMENTER` trailer as that discipline asks).

    The one fixing absorption this chain took: the closeout-status review's F2 — the janitor pin's whole-`gettempdir()` scan coupling, whose row cell named "a later brief's re-scope or serial-set move" — is fixed by this step: the later brief (`e9a37db`) took the re-scope reading and the implementer delivered it (its own F2, fixed with red evidence), re-driven red at REV and green at FINAL by this review (VERIFIED above). The closeout-status review's F1 (its step's trailer lapse), F3 (the exit-gate-runs REV-cell hash, corrected in the closeout write itself) and F4 (the "2326 stores" noun, corrected in the same write) remain closed actionless as the closeout row records them.

    Received-set dispositions kept: F16 fixed by the report that filed it (the deadline-margin review's delivered margin, its red re-driven there); the closeout-status review's F2 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/F32/F33 stay carried with their named owners and text corrections; the exit-gate-runs chain's F1–F4 stay carried with their named planner next actions.

    Then each finding marked carried by this step, with its ID:
    F1 (P1, ORIGIN: CODE, carried) — the pre-commit hook's inherited `GIT_DIR` corrupts a linked-worktree branch and the shared config; next action is the harness owner's (see FINDINGS).
    F2 (P2, ORIGIN: BRIEF, carried) — the bare non-specific `!` reading under "every non-plain tag"; next action is the planner's (see FINDINGS).

      Then each finding marked carried by this review, with its ID:
      F3 (P2, ORIGIN: CODE, carried) — the spilled `GIT_CONFIG_PARAMETERS` in the hook environment extends F1's scrub set; next action is the harness owner's, with F1 (see FINDINGS).
    Then each finding marked carried by this step, with its ID:
    F1 (P2, ORIGIN: CODE, carried) — src/orchestrator/git_ops.py's `_git` bypasses the `_git_environment` seam and still inherits the five; out of IN SCOPE (see FINDINGS).
    F2 (P2, ORIGIN: BRIEF, carried) — the "removes it before committing" ordering; the reading taken is that the disposable linked worktree is the commit-path verification drive (see FINDINGS).
  Received-set dispositions kept: this step's received carried set — the implementer's F1 (the `git_ops._git` seam bypass) and F2 (the "removes it before committing" ordering) — kept carried, both re-verified in this review's VERIFIED (F1: the site read at FINAL, `env={**os.environ, **GIT_ENVIRONMENT}` at `src/orchestrator/git_ops.py`'s `_git`, importing `GIT_ENVIRONMENT` from `.worktree` and never routing through `_git_environment`, outside this brief's IN SCOPE and unreachable by the hook's scrub in production; F2: the only reading consistent with the rest of the brief — the work commit is made from the main tree and the disposable linked worktree is minted at FINAL purely as the commit-path verification drive, which the delivery and this review's own drive both did, the worktree removed afterwards); the phase6 chains' F13/F14/F17/F21/F22/F23/F26/F28/F29/F30/F31/F32/F33 and the exit-gate-runs chain's F1–F4 stay carried with their named owners and text corrections (this review touches neither the brief-text defects they name nor any code path they cite); F11/F12/F15/F18/F19/F20/F24/F25/F27 stay fixed as recorded in the reports that filed them. Added by this review: F3, F4, carried.

  --- review F3/F4 carried findings verbatim (docs/research/harness-hook-env-scrub-review.md FINDINGS) ---

    F3 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
    The review brief's FOCUS premise about the leak channel is falsified on git 2.47.3: "the parameter naming a missing hook dir must fail children, not silently pass" — measured twice, a riding `GIT_CONFIG_PARAMETERS='core.hooksPath=/nonexistent/missing-hooks'` does NOT fail the fixture-style children: at the REV merge and under the four-of-five seam mutant the child's commit exits 0, because git silently treats a hooksPath pointing at a missing directory as no hook at all (control measured: with a real failing `pre-commit` hook installed in the child repo the commit exits 1 without the parameter and 0 with it — the parameter's effect is silent hook SUPPRESSION, the opposite of the FOCUS's failure form). The delivered pin's parameters (`'user.email=leak@example.com' 'user.name=leak'`) also silently pass when they ride alone, and the only loud channel `GIT_CONFIG_PARAMETERS` affords is malformed parameters (`fatal: unable to parse command-line config`, measured) — which is not what the FOCUS names and not what a faithful `-c`-derived leak shape carries.
    FIXED: no regression test — an ORIGIN: BRIEF finding is fixed once a later committed brief corrects the text; this review's VERIFIED carries the measurements. Next action is the planner's: correct the review FOCUS's parenthetical (the missing-hook-dir form fails nothing; the loud forms are malformed parameters and the silent form is hook suppression).
    F4 | SEVERITY: P2 | ORIGIN: CODE | STATE: carried
    The delivered pin's `GIT_CONFIG_PARAMETERS`-channel refusal is observed only at the environment level: under a seam mutant dropping four of the five (the pop skipping only `GIT_CONFIG_PARAMETERS`), the fixture-child behavioral pin stays green — the riding `'user.email=leak@example.com' 'user.name=leak'` neither fails the child (its commit exits 0) nor leaves any byte-observable trace (the parameters are never written into any repo's config) — and the spawn-seam environment pin (`surviving == ['GIT_CONFIG_PARAMETERS']`) is the only committed member that reddens. The review FOCUS's demanded behavioral red for this channel as literally written is unconstructible on git 2.47.3 (F3), so the pin's shape cannot be made loud within the faithful-leak reading; what a later brief CAN pin is the suppression shape (a riding `core.hooksPath` silently disabling a real hook — the control above) or a child-exit-code assertion.
    FIXED: no regression test — the seam's refusal of all five is delivered and the environment member catches the single-channel ride; next action is a later brief's: either accept the environment-level observation as the channel's pin or add the suppression/exit-code member named in SHAPES.

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

F1 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
R18's candidate shape — "`GIT_ENVIRONMENT` itself carries the refusal, so every copying fixture inherits the scrub" — cannot be built as literally worded: the fixture identity is a plain dict of names and dates, and a dict cannot drop ambient variables after the copy. The brief's measured alternative (unconditional empty values) fails clean callers (`env GIT_DIR= git -C <repo> rev-parse HEAD` → `fatal: not a git repository: ''`, rc 128), so the one consistent reading is seam routing: every in-scope fixture builds its child environment through `_git_environment(GIT_ENVIRONMENT)`, so the pop runs over the merged copy and clean callers are preserved. Next action is the planner's: a later committed brief's text correction names the reading taken (dict-carries-refusal vs seam routing).
