REPORT — harness-copying-fixture-seam-review
STEP: harness-copying-fixture-seam (the fast-suite copying-fixture spawns route through the refusal seam)
REV: 360ba3f   FINAL: 2de53712f13fadeb7d37e36d696b58c542a55b22 (the sha under review, copied from the review brief; the range `360ba3f..2de5371` additionally holds the step's own brief commit `ab7b482`, and the implementer report rides outside the reviewed range in `4a2e78d`, per the prior steps' pattern)
CHANGED: docs/research/harness-copying-fixture-seam-review.md — this report only; no review test files committed. Every red this review produces is a scratch re-drive of the committed pin's own assertion class; the scratch instruments are named in SHAPES and removed with their scratch trees, the two sorted scratch clones standing as the evidence locations.
VERIFIED: scripts/check-scope 360ba3f 2de5371 docs/research/harness-copying-fixture-seam-brief.md — ran first (the method's only gated check), 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)`.
VERIFIED: the commit form — `git show --no-patch --format='%H%n%an%n%B' 2de53712` names the work commit `Route every fast-suite copying fixture spawn through the refusal seam` with author `gituser` and the `Actor: IMPLEMENTER` trailer; the report commit `4a2e78d` carries the same trailer and this review session authored neither (`git log --oneline 360ba3f..2de5371` is exactly the brief commit `ab7b482` and the work commit `2de5371`). `git diff --name-status 360ba3f..2de5371` is exactly `A docs/research/harness-copying-fixture-seam-brief.md`, `M src/orchestrator/conformance.py`, `M tests/test_derive_obligations.py`, `M tests/test_hook_env_scrub.py`, `M tests/test_milestone3_acceptance.py`, `M tests/test_milestone8_readiness.py` — no other file.
VERIFIED: the embedded brief copy (`docs/research/harness-copying-fixture-seam-review-brief.md` between its BEGIN/END markers, extracted to 2589 lines) is byte-identical to the committed standalone `docs/research/harness-copying-fixture-seam-brief.md` (`diff` empty) — no `ORIGIN: BRIEF` finding from the copy; review proceeds against the committed file. A reader-side hazard is recorded in METHOD FRICTION: the CONTEXT line is 2507 bytes and this session's file reader clips at 2000 characters, which first presented themselves as an in-file truncation marker; the diff is the authority.
VERIFIED: the routing, structurally at FINAL — all six raw `{**os.environ, **GIT_ENVIRONMENT}` sites reroute: `src/orchestrator/conformance.py:82`, `tests/test_derive_obligations.py:38`, `tests/test_milestone3_acceptance.py:66`, `tests/test_milestone3_acceptance.py:495`, `tests/test_milestone8_readiness.py:51`, `tests/test_milestone8_readiness.py:156` each now build `environment = _git_environment(GIT_ENVIRONMENT)` with function-level imports, and each file's follow-up `rev-parse HEAD` read rides `env=environment` (the four identity reads F2's reading named). `GIT_ENVIRONMENT`'s fixture identity is unchanged in conformance (the diff touches only the import and the merge lines), `tests/test_milestone8_readiness.py` keeps importing worktree's dict, and `src/orchestrator/worktree.py`'s seam is byte-identical REV..FINAL (outside the diff). The FOCUS's missed-merge question (Q1): a tree-wide scan finds the remaining `{**os.environ, …}` copies only in the seam itself (`worktree.py:71`), the pin's own intended controls, the three slow-marked out-of-scope files the implementer names, and `tests/test_check_scope.py:350` — that one is a bash script-driver spawn outside IN SCOPE and outside the in-scope import graph; it is measured in SHAPES and filed as F37.
VERIFIED: red at REV — scratch `/tmp/kilo/hcf-rev` (`git archive 360ba3f | tar -x`; all five in-scope files `cmp`-verified against `git show 360ba3f:<path>`; the FINAL pin module copied over it, `cmp`-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.35s`, each red at its named assertion — the behavioral member `AssertionError: the copying fixture's spawn steered the shared config outside its tmpdir` and the source anchor `AssertionError: a fast-suite copying fixture still merges os.environ around the refusal seam: ['src/orchestrator/conformance.py:82', 'tests/test_derive_obligations.py:37', 'tests/test_milestone3_acceptance.py:66', 'tests/test_milestone3_acceptance.py:491', 'tests/test_milestone8_readiness.py:51', 'tests/test_milestone8_readiness.py:152']`. The full module on the REV scratch → `2 failed, 9 passed in 0.74s` — the nine prior members green at REV as the report claims (Q2 part 1).
VERIFIED: the behavioral red is a true behavioral steer, not a silent missing (Q2 part 2) — re-driven by hand at the REV scratch, importing the scratch's `conformance`: the sentinel repository, its real linked worktree and the faithful five-leak reproduce the pin's shape; `_fixture_repo` steered (the child's `git commit` raised rc 1) and the sentinel's `.git/config` gained exactly one line — `worktree = /tmp/.../sentinel-linked` — the concrete mutation the scrub-2 statement measured and the pin's byte-identity assertion grades. At FINAL the same hand drive lands green: the fixture returns, the sentinel config is byte-identical, the child serves its own `.git`.
VERIFIED: the R18 reading the implementer's F1 defers to this review (Q-F1) — both quoted measurements reproduce exactly on this host: `env GIT_DIR= git -C <repo> rev-parse HEAD` → rc 128, `fatal: not a git repository: ''`; with `GIT_DIR` at the linked worktree's gitdir (plus its index/work-tree/parameters ride), the same `rev-parse` against an unrelated repository exits 0 and prints the linked worktree's own HEAD (`... == linked's HEAD: True`). The routing reading is the only one consistent with everything measured here (the dict carrying the refused keys is refused by the seam IN ADDITION to routing; the seam's refusal is what the refused child observes), and the carried F2 stays carried with this review's endorsement.
VERIFIED: green at FINAL — `.venv/bin/python -m pytest tests/test_hook_env_scrub.py -q` → exit 0, `11 passed in 0.71s` (the gate's own printed line); `--durations=5 -q` → `0.09s` read-children, `0.07s` tar-fetch, `0.07s` source anchor, `0.05s` copying-fixture, `0.05s` gitops (all sub-second, the wall drift ambient against the report's `0.58s`).
VERIFIED: scripts/check-tests --fast — exit 0, `1080 passed, 111 deselected in 114.23s (0:01:54)` (the report's own count: `1078` at the scrub-2 baseline plus exactly the two new nodes; the wall drifts ambient).
VERIFIED: scripts/check-static — exit 0, gated `All checks passed!`, advisory `Found 104 errors.` (both lines the gate's own; unchanged against the scrub-2 baseline and the report's line — the routing and the two new nodes draw no new advisory).
VERIFIED: scripts/check-docs — exit 0, `409 Total (in 841ms) 🔗 183 Unique ✅ 409 OK 🚫 0 Errors` (the brief's `409 / 183 / 409 / 0` baseline holds pre-report).
VERIFIED: the mutants (rule: every mutant on a scratch copy, each applied run restored `cmp`-identical, with a pre-run cleanliness assertion over all five in-scope files after this review's own driver first accumulated mutations across iterations — the first two attempts' numbers were discarded before any figure was reconciled; scratch `/tmp/kilo/hcf-final`, `git archive 2de5371 | tar -x`, `cmp`-verified): M1 conformance's merge reverted → the behavioral member AND the anchor red (`2 failed, 9 passed in 0.86s`, anchor names exactly `conformance.py:82`); M2 conformance's rev-parse `env=` removed (merge stays routed) → only the behavioral member reds, at the returned-commit assertion, anchor stays green (full module `1 failed, 10 passed in 0.65s`; targeted `-k copying_fixture_spawn` `1 failed, 10 deselected in 0.27s` — the read rides the scrubbed copy for a reason); M3 derive's merge reverted → anchor only (`tests/test_derive_obligations.py:38`, `1 failed, 10 passed in 0.85s`); M4 milestone-3's first merge reverted → anchor only (`:66`, `0.79s`); M5 milestone-3's second merge reverted → anchor only (`:495`, `0.94s`); M6 milestone-8's first merge reverted → anchor only (`:51`, `0.84s`); M7 milestone-8's second merge reverted → anchor only (`:156`, `0.79s`). Q3: the anchor names all six at REV, reds exactly the reverted site on every per-site revert, names no clean site at FINAL, and per the identity reads M2 grades the read half — the exactness claim holds site by site.
VERIFIED: the nine prior members stay red-classed on their named mutants (Q5) — the same scratch, one revert-mutant per prior red class: N1 both `_git_environment` pop loops removed → `8 failed, 3 passed in 0.71s` (the fixture-child, spawn-seam, riding-hooks-path, tar-fetch, gitops, read, extra-overlay and copying members red; the hook, caller and anchor members stay green as designed); N2 only the overlay pop removed → only `test_the_seam_refuses_five_riding_in_the_extra_overlay` reds (`1 failed, 10 passed in 0.76s`, the scrub-2 M-extra record); N3 the `_git` caller scrub removed → only the caller member reds at its steer assertion (`1 failed, 10 passed in 0.90s`); N4 the hook's `unset` line removed → only the hook member reds listing exactly the five (`1 failed, 10 passed in 0.72s`); N5 `git_ops._git` reverted to the raw merge → only the gitops member reds (steered commit, `ExperimentError`, `1 failed, 10 passed in 0.77s`); N6 the derive read spawns reverted to ambient inheritance → only the read member reds (diverted `ls-tree`, `DerivationError: cannot list ... fatal: not a tree object`, `1 failed, 10 passed in 0.84s`); N7 `materialise` reverted to ambient inheritance → only the tar-fetch member reds (diverted archive, `ProtocolViolation: ... fatal: not a tree object`, `1 failed, 10 passed in 0.90s`). No prior member lost its red class; the delivery touched none of their surfaces.
VERIFIED: the five in-scope files' whole spawn surface enumerated by this review (Q4) — every `subprocess` site swept: after the step zero raw merges remain; the only env-less git readings left in-scope are `tests/test_milestone3_acceptance.py:454` (`git … rev-parse HEAD~1`) and `tests/test_milestone8_readiness.py:138` (`git … ls-tree -r --name-only HEAD`), both post-hook verification reads inside test bodies; the pin's own controls (`:213-:214` the stub-hook PATH control's environment display, `:249` the riding-parameters suppression control, `:455` the steering control) are the intended leak shapes, not spawns to route. The two env-less reads are measured under the faithful leak — each silently serves the FOREIGN tree's bytes at rc 0 (the `rev-parse` returned the foreign repository's parent sha; the `ls-tree` returned the foreign repository's file list `['a.txt', 'b.txt']` instead of the child's) — and the surrounding assertions turn them loud (never a wrong-green observed). F2's fix covered exactly the four fixture-building identity reads; these two are the class's residual, filed as F34.
VERIFIED: the member placements (Q6) — the three consumers of the two routed milestone-8 inline spawns (`test_candidate_git_metadata_is_rejected_before_import`, `test_import_preserves_excluded_content_and_persists_candidate`, `test_import_handles_file_and_directory_kind_swaps`) run plain and fast, re-driven at the scratch: `3 passed, 27 deselected in 0.65s`, no `NAMESPACE_V1`/skip gate anywhere in the file; the routing itself is positively member-exercised, the leak-behavioral drive for those two sites is not (the report's justification clause is falsified, F36). The three out-of-scope copying files are genuinely slow-marked (`pytestmark = pytest.mark.slow` at `tests/test_run_entry.py:34`, `tests/test_phase5_run_entry_fixes_2_review.py:52`, `tests/test_phase5_run_entry_fixes_4_review.py:22`) — deselected by the fast gate exactly as the report states (Q6, Q7's placement half).
VERIFIED: Q7 (figures are the gates' own printed lines) — every figure quoted in the report's VERIFIED that this review re-ran matches the corresponding line this review printed (counts identical, walls drift ambient where walls drift), and no figure in the report rides from another run's text.
VERIFIED: scripts/check-tests (the full standing battery) — exit 0, `1191 passed in 1224.25s (0:20:24)` (the gate's own printed line on the second attempt; the selection is the 1080 fast nodes plus the 111 slow nodes, zero failures). Two attempts were spent: the first's background record vanished from this session's tracker without a printed line (state unrecoverable; no figure is recorded from it), and the recorded line is the second attempt's own output, read from its final summary line.
NOT VERIFIED: none
FINDINGS:
  F34 | SEVERITY: P2 | ORIGIN: CODE | STATE: carried
  Two in-scope git reads still spawn WITHOUT the scrubbed environment: `tests/test_milestone3_acceptance.py:454` (`git -C <wt-check worktree> rev-parse HEAD~1`) and `tests/test_milestone8_readiness.py:138` (`git -C <integration> ls-tree -r --name-only HEAD` — both no `env=` kwarg). F2's fix covered the four fixture-BUILDING identity reads; these post-hook verification reads are the same class's residual: under the faithful five-leak both silently serve another tree's bytes at rc 0 (the `rev-parse` the foreign parent sha, the `ls-tree` the foreign listing), and the surrounding assertions make them loud — fail-closed today on every driven shape, no wrong-green anywhere. Production-unreachable while the hook scrubs the parent (the linked-worktree drive), but they sit inside IN SCOPE and outside the anchor's reach.
  FIXED: no regression test — the anchor's scan grades merges only. Next action is a later brief's: route the two reads through `_git_environment(GIT_ENVIRONMENT)` (one line each — the same fix F2's fix applied to the identity reads) or add the caller-level drive named in SHAPES.
  F35 | SEVERITY: P2 | ORIGIN: CODE | STATE: carried
  The source anchor is exact only over the dict-display cast of the copying expression: the end-of-module scan (`_environ_merge_lines`) matches `ast.Dict` nodes whose star-values are the `os.environ` attribute and misses every other copy form. Measured by injecting variants into a scratch copy of `src/orchestrator/conformance.py` and re-running the anchor: V1 `from os import environ` + `{**environ, **GIT_ENVIRONMENT}` → green (miss); V2 `dict(os.environ, **GIT_ENVIRONMENT)` → green (miss); V3 `env = os.environ.copy(); env.update(GIT_ENVIRONMENT)` → green (miss); the control copy (`{**os.environ, **GIT_ENVIRONMENT}`) → red at the injected line. The four in-scope files contain zero such variants today (this review's scan), so the GOAL holds as shipped; the coupling is the surface-copies-the-surface drift class the chain already carries elsewhere (F22-class fidelity of text-to-anchor).
  FIXED: no regression test — a negative-regex-style AST pin is exactly the exact known cast. Next action is a later brief's: either broaden `_environ_merge_lines` (any attribute/name access of `environ` inside a Dict or a call, plus a clean-site allowlist) or record the cast-limited red class explicitly in the anchor's docstring.
  F36 | SEVERITY: P2 | ORIGIN: DOCUMENT | STATE: carried
  The implementer report's SHAPES(2) justification "(their surrounding tests need NAMESPACE_V1)" is false as written: the three tests that consume the two routed milestone-8 inline spawns are plain fast tests requiring no sandbox profile (re-driven `3 passed, 27 deselected in 0.65s`; no `NAMESPACE_V1`, no skip gate, no capabilities probe in the file). The UNBUILT substance stands correctly — no committed member drives those two inline sequences under a faithful leak, so the leak-red class for the milestone-8 lane exists only through the source anchor — but the placeholder justification misstates what the consumers need, in the same class as the carried brief-correction set (F33-class placeholder landing intact).
  FIXED: no regression test — an ORIGIN: DOCUMENT finding is fixed when the report's wording is corrected. Next action is the next disposition cycle's: re-read SHAPES(2) with the corrected reasoning (the routing is member-exercised positively; the leak-behavioral drive is the unbuilt shape; nothing about NAMESPACE_V1).
  F37 | SEVERITY: P2 | ORIGIN: CODE | STATE: carried
  The fast suite still carries an unseamed git-spawn surface outside this brief's four-file enumeration: `tests/test_check_scope.py`'s `_git` helper inherits the ambient environment for every spawn, and `:350` builds the script driver's environment as `{**os.environ, "GIT_DISCOVERY_ACROSS_FILESYSTEM": "1"}` — under the faithful five-leak the script's own git reads (it resolves `--show-toplevel`, verifies both revisions and diffs the range) run gifted the leaked values. Measured: with the five riding the module's environment, ALL 20 members error at setup (`20 errors in 1.41s`) — the sandbox fixture's seed commit lands as a steered child — and the focused copy of `test_run_from_a_subdirectory_still_finds_the_store` errors before it can complete; on every driven shape the outcome is a loud refuse, never a silent verdict. The module is a fast-suite member (no slow mark) and is neither in this brief's IN SCOPE nor an importer of the in-scope modules.
  FIXED: no regression test — the brief's surface enumeration named the fixture-identity copying expression only. Next action is a later brief's: route the module's spawn surface through the seam (the sandbox fixture's `_git`, the script driver's env) or extend the anchor's file list with the provider-consumers.
SHAPES: probed shapes the suite does not build, named here (nothing probed by this review is left unnamed):
  1. The behavioral member's red class as concretely built: the steered fixture leaves `worktree = <linked path>` in the sentinel's shared config (re-measured by hand at the REV scratch, the mutation diff printed) — the delivery's own built shape, re-measured.
  2. The anchor's six-name red class and its per-site revert table (M1–M7 above) as built — each of the six sites is individually grading-red.
  3. The env-less read steer on the two residual reads (F34): both silently serve foreign bytes at rc 0 under the faithful leak (this review's probe script printed the foreign sha and the foreign listing) — unbuilt: the reads' time-to-loud is the assertions, a committed member would belong with F34's route fix.
  4. The check-scope module-class leak-fragility (F37): the whole file red-over-error under a riding five — unbuilt (the module's spawns are outside this brief's surfaces; a pin belongs with F37's action).
  5. The anchor's variant-cast misses (F35): three variant copy forms injected and green through the anchor, the known cast red — attempted unbuilt (the drift coupling, named for a later brief).
  6. The implementer's own named-unbuilt shapes remain correctly unbuilt: the slow-marked `_GIT_ENV` copies (three files `slow` pytestmarks verified) and the milestone-8 leak-behavioral drive (its justification now corrected per F36). Nothing probed — by the implementer or by this review — is left unnamed: two built members delivered by this step, six of this review's probes (3–5) filed above, plus the implementer's two.
TRIPPED: none
PROPOSED ROWS: none
METHOD FRICTION: two entries. (1) This session's file reader clips displayed lines at 2000 characters and adds its own clipping marker, which first read as an in-file truncation marker in the review brief's CONTEXT line; the copy's byte-identity had to come from `diff` against the committed file (it is identical) — the F22-class lesson again: the stored text, not the displayed text, is the record. (2) The multi-minute batteries (the fast `114.23s`, the full standing battery) ran through the session's background-process tooling as the chain's preceding friction entries record; the command lines ran exactly as documented. This review's mutant drivers discarded two polluted attempt-summaries before the clean battery was achieved (the leftover-state assert noted above) and their numbers are not in this report.
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).


    Then each finding marked carried by this review, with its ID:
    F34 (P2, ORIGIN: CODE, carried) — two in-scope git reads still spawn WITHOUT the scrubbed environment: `tests/test_milestone3_acceptance.py:454` (`git … rev-parse HEAD~1`) and `tests/test_milestone8_readiness.py:138` (`git … ls-tree -r --name-only HEAD`, both no `env=` kwarg) — F2's fix covered the four fixture-BUILDING identity reads; these post-hook verification reads are the same class's residual. Under the faithful five-leak both silently serve ANOTHER tree's bytes at rc 0 (the `rev-parse` returned the foreign repository's parent sha; the `ls-tree` returned the foreign listing `['a.txt', 'b.txt']`), and the surrounding assertions turn them loud — fail-closed on every driven shape, no wrong-green anywhere. Production-unreachable while the hook scrubs the parent (the linked-worktree drive), but they sit inside IN SCOPE and outside the anchor's reach. Next action is a later brief's: route the two reads through `_git_environment(GIT_ENVIRONMENT)` (one line each — the same fix F2's fix applied to the identity reads) or add the caller-level drive named in SHAPES.
    F35 (P2, ORIGIN: CODE, carried) — the source anchor is exact only over the dict-display cast of the copying expression: `_environ_merge_lines` matches `ast.Dict` nodes whose star-values are the `os.environ` attribute, and misses every other copy form. Measured by injecting variants into a scratch copy of `src/orchestrator/conformance.py`: V1 `from os import environ` + `{**environ, **GIT_ENVIRONMENT}` → green (miss); V2 `dict(os.environ, **GIT_ENVIRONMENT)` → green (miss); V3 `os.environ.copy()` + `update()` → green (miss); the control `{**os.environ, **GIT_ENVIRONMENT}` → red at the injected line. The four in-scope files contain zero such variants today (this review's scan), so the GOAL holds as shipped; the coupling is the surface-copies-the-surface drift class the chain already carries (the F22-class fidelity of text-to-anchor). Next action is a later brief's: either broaden `_environ_merge_lines` (any attribute/name access of `environ` inside a Dict or a call, with a clean-site allowlist) or record the cast-limited red class explicitly in the anchor's docstring.
    F36 (P2, ORIGIN: DOCUMENT, carried) — the implementer report's SHAPES(2) justification "(their surrounding tests need NAMESPACE_V1)" is false as written: the three tests consuming the two routed milestone-8 inline spawns are plain fast tests requiring no sandbox profile (re-driven `3 passed, 27 deselected in 0.65s`; no `NAMESPACE_V1`, no skip gate, no capabilities probe in the file). The unbuilt substance stands correctly — no committed member drives those two inline sequences under a faithful leak, so the milestone-8 lane's leak-red class exists only through the source anchor — but the placeholder justification misstates what the consumers need. Next action is the next disposition cycle's: re-read SHAPES(2) with the corrected reasoning (the routing is member-exercised positively; the leak-behavioral drive is the unbuilt shape; nothing about NAMESPACE_V1).
    F37 (P2, ORIGIN: CODE, carried) — the fast suite still carries an unseamed git-spawn surface outside this brief's four-file enumeration: `tests/test_check_scope.py`'s `_git` helper inherits the ambient environment for every spawn, and `:350` builds the script driver's environment as `{**os.environ, "GIT_DISCOVERY_ACROSS_FILESYSTEM": "1"}` whose script's own git reads (it resolves `--show-toplevel`, verifies both revisions and diffs the range) then run gifted the leaked values. Measured: with the five riding the module's environment, ALL 20 members error at setup (`20 errors in 1.41s`, the sandbox's seed commit landing as a steered child), and the focused `test_run_from_a_subdirectory_still_finds_the_store` copy errors before it can complete; on every driven shape the outcome is a loud refuse, never a silent verdict. The module is a fast-suite member (no slow mark) and is neither in this brief's IN SCOPE nor an importer of the in-scope modules. Next action is a later brief's: route the module's spawn surface through the seam (the sandbox `_git`, the script driver's env) or extend the anchor's file list with the provider-consumers.
Received-set dispositions kept: this review's received carried set — the step's own F1 (the R18 reading) kept carried with the reading endorsed by this review's VERIFIED (the routing reading is the consistent one; both the brief's quoted measurements reproduce) and rides the implementer report's carried block verbatim below as its dispositions recorded — the phase6 chains' F13/F14/F17/F21/F22/F23/F26/F28/F29/F30/F31/F32/F33 and the scrub chains' scrub F2 (the disposable-worktree ordering; the step's delivery followed the recorded reading and this review's drives end-to-end used it) and scrub-review F3 (the review FOCUS parenthetical) 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; the run-entry chains' findings are not received by this step and are not carried. Added by this review: F34, F35, F36, F37, carried.
