REPORT — phase6-deadline-margin-review
STEP: phase6-deadline-margin (Phase 6: the grading deadline holds under load — F16)
REV: a1d4e07   FINAL: ba0d09bdca0fcdb3e551c170e2144679faba2b1a (the work commit; the report commit f5bc2d2 does not name FINAL — verified by git log)
CHANGED: docs/research/phase6-deadline-margin-review.md — this report only; no review test files committed (every red this review produces is a scratch re-drive of the already-committed pin's own assertion class; the scratch instruments are named in SHAPES and removed with their scratch trees).
VERIFIED: scripts/check-scope a1d4e07bf198bd11fae20a32cb9767facdf08793 ba0d09bdca0fcdb3e551c170e2144679faba2b1a docs/research/phase6-deadline-margin-brief.md — exit 0, `claimed: tests/test_phase3_project_oracle.py`, `tripped: none`, `scope: ok (2 path(s) in a1d4e07bf198bd11fae20a32cb9767facdf08793..ba0d09bdca0fcdb3e551c170e2144679faba2b1a)`. This is the method's gated check and it ran first.
VERIFIED: `git diff a1d4e07bf… ba0d09bd… --stat` touches exactly `docs/research/phase6-deadline-margin-brief.md` (+184 lines) and `tests/test_phase3_project_oracle.py` (+55/−1) — the IN SCOPE file plus the brief; no committed test edit outside it. The one deletion is the fixture's `gate_timeout_seconds=60.0,` line (`:216` of the pre-image) and `build_project_oracle` keeps the delivered `gate_timeout_seconds: float = 300.0` default (`src/orchestrator/project_oracle.py:583` region, unchanged) — the seam is the fixture's own deadline, and the seed (`424242` argv'd), the five-case corpus and the determinism pin's `runs = 5` are untouched by the commit's own diff.
VERIFIED: scripts/check-tests --fast — `984 passed, 110 deselected in 107.50s (0:01:47)` (exit 0). First attempt, recorded: `10 failed, 910 passed, 110 deselected, 64 errors in 70.08s` — it began with the shared /tmp tmpfs at 3 free inodes (100%) and 1-min loadavg ~29 (this session's scratch teardown burst plus an external writer `/tmp/opencode`); after reclaiming pipeline scratch residue (this script's own pytest roots, the surviving `/tmp/kilo`, `/tmp/dm-cal-womhjinj` — the implementer's own scratch leftover) a sampled failing module re-passes green in isolation on the reclaimed tmpfs (`.venv/bin/python -m pytest tests/test_verifier_mutations.py -q -p no:cacheprovider` — `41 passed in 0.92s`), so the first line is the F15 ENOSPC class on the standing battery, environment and not a value change.
VERIFIED: the deselection-delta contrast — `scripts/check-tests --fast` from a pristine `git archive a1d4e07` extraction (the shared `.venv` symlinked in) — `984 passed, 109 deselected in 101.92s (0:01:41)`. FINAL−REV is exactly the one added slow-marked pin: `passed` constant at 984, deselected 109→110.
VERIFIED: .venv/bin/python -m pytest tests/test_phase3_project_oracle.py --durations=5 -p no:cacheprovider — `7 passed in 895.99s (0:14:55)`; slowest five `476.91s` `test_project_oracle_classifies_the_five_case_corpus_on_a_real_repository`, `190.81s` `test_grading_gate_grades_one_candidate_identically_across_consecutive_runs`, `146.79s` `test_gate_config_and_test_corpus_neutralization_is_rejected`, `65.69s` `test_near_deadline_candidate_grades_fail_under_host_contention`, `12.29s` `test_registry_identity_floors_reject_compensated_replacements` — the module's 7 members (6 + the pin), the same composition the report names with walls ~6% above its line (ambient).
VERIFIED: scripts/check-static — exit 0, gated `All checks passed!`, advisory `Found 104 errors.` (unchanged from the brief's EXPECTED WALLS and the report's line; the added pin draws nothing new).
VERIFIED: scripts/check-docs — exit 0; at HEAD `403 Total (in 979ms) 🔗 180 Unique ✅ 403 OK 🚫 0 Errors`. The pristine `ba0d09b` extraction (the shared `.venv` symlinked in) prints `402 Total (in 1s 77ms) 🔗 180 Unique ✅ 402 OK 🚫 0 Errors` — the report's figure reproduces at its own FINAL tree; HEAD's +1 is the review-plan commit's added brief file. Note for F33: the gate's `Total` is lychee's link-check count, not a file count (402 checks over 176 worktree `.md` files at the pristine tree; 403 over 179 at HEAD).
VERIFIED: scripts/check-tests — the standing battery in full — `1094 passed in 1291.04s (0:21:31)` (exit 0); the suite's every member green at HEAD, whose fixture file is FINAL's.
VERIFIED: the margin (a) — the delivered node re-driven at FINAL: `.venv/bin/python -m pytest tests/test_phase3_project_oracle.py::test_near_deadline_candidate_grades_fail_under_host_contention -q -p no:cacheprovider` → `1 passed in 69.21s (0:01:09)` idle ambient, `1 passed in 72.83s (0:01:12)` under a genuine external 12-worker busy pool (`timeout 600 sh -c 'for w in 1 2 3 4 5 6 7 8 9 10 11 12; do .venv/bin/python -c "while True: pass" & done; wait'`; pool verified live by process count before the drive). The verdict under both is the pin's asserted FAIL (`assert verdict == oracle.GRADE_FAIL`, `:680`): the near-deadline candidate's seeded grade stays FAIL under host load at the delivered 300.0s default.
VERIFIED: the instrumented wall probe (a scratch file on the REV scratch — `tests/test_zz_review_probe.py`, the fixture's own construction with `gate_timeout_seconds` made selectable, removed with the scratch): at `deadline=300.0`, idle ambient — `wall=51.47s verdict=FAIL` (busy_before=0, busy_after=0): the near-deadline grade's natural wall on this host sits ~8.5s under the regression's 60.0s wall. At `deadline=60.0` with the same external 12-worker pool verified live (busy counts 15, loadavg 8.39→18.16 across the drive): `wall=60.04s verdict=CANDIDATE_TIMEOUT` — the flip, reproducing on this review's own watch the F16 class the grading-seed review measured at 62.44s and the implementer measured 3/3 at 60.06–60.08s.
VERIFIED: the red (b) — the delivered pin re-driven on the REV scratch (the delivered pin's text appended to `git show a1d4e07:tests/test_phase3_project_oracle.py` with `import sys`; diff vs the REV pre-image shows exactly that; the scratch module vs the delivered FINAL file differs only in the fixture's `gate_timeout_seconds=60.0,` line and two trailing blank lines): on the idle host `.venv/bin/python -m pytest tests/…::test_near_deadline_candidate_grades_fail_under_host_contention -q -p no:cacheprovider` → `1 passed in 69.71s` and `1 passed in 67.92s` — the named red does NOT reproduce idle (the grade fits under 60.0s); under the external pool above the scratch red exactly as the implementer measured: `.venv/bin/python -m pytest …` on the seam scratch below — `1 failed` on the FAIL-verdict assertion.
VERIFIED: the seam (c) — the FINAL scratch archive with the fixture's single line `gate_timeout_seconds=60.0,` re-added (`diff` vs `git show ba0d09bd…:tests/test_phase3_project_oracle.py` shows exactly that one line): both pins idle → `2 passed in 264.77s (0:04:24)` (`-rA`: `test_grading_gate_grades_one_candidate_identically_across_consecutive_runs` PASSED, `test_near_deadline_candidate_grades_fail_under_host_contention` PASSED) — the fixture's 60.0s wall alone does not red the module on an idle host; under the external pool the same node → `1 failed in 66.41s (0:01:06)` — `E AssertionError: the near-deadline candidate graded CANDIDATE_TIMEOUT under host contention, not FAIL: the fixture's grading deadline, not the seed, decided the verdict` / `E assert 'CANDIDATE_TIMEOUT' == 'FAIL'` at the delivered FAIL-verdict assertion (`:680`; scratch line `:681`, the re-added fixture line shifting it) — the pin that reds on the seam's regression is exactly the delivered determinism-under-load pin, on its FAIL-verdict assertion, and the same load keeps FINAL's 300.0s default green (the `1 passed in 72.83s` drive above).
NOT VERIFIED: none
FINDINGS:
  F32 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
  The brief's red clause under-specifies the regime: "at REV, with the fixture's 60.0s deadline, the near-deadline candidate's seeded grade under the test's own contention flips FAIL→CANDIDATE_TIMEOUT" — on an idle host the pin's own pool alone does not cross the 60.0s wall: the grade's measured natural wall at the delivered deadline is 51.47s (probe, VERIFIED) and the pool keeps it under 60.0 (pin drives on the REV scratch green 2/2, grades ≈58–59s; idle seam drives green). The CANDIDATE_TIMEOUT flip reproduced only with an external 12-worker busy pool run beside the pin's own (probe `wall=60.04s verdict=CANDIDATE_TIMEOUT`; seam drive `1 failed` on `:680`) — the mid-run regime the implementer's red (60.06–60.08s, 3/3) and the grading-seed review's 62.44s wall measured. A later actor re-driving the red on an idle host sees green and may conclude the red is chimeric — the F14 warning class, measured here against this step's own named red.
  FIXED: no regression test — an ORIGIN: BRIEF finding is fixed once a later committed brief corrects the text; F14's pending load-condition carry names the class and absorbs this note. Next action is the planner's.
  F33 | SEVERITY: P2 | ORIGIN: DOCUMENT | STATE: carried
  The report's docs-line explanation narrates the gate's `Total` as a file-set delta ("the brief's `401` baseline predates the brief commit, whose added `docs/research/phase6-deadline-margin-brief.md` is the one-path 401→402 delta (the F28 class)"): the gate's `Total` is lychee's link-check count, not a file count — measured 402 checks over 176 worktree `.md` files at the pristine `ba0d09b` tree and 403 over 179 at HEAD — and the markdown corpus is identical between the 401 line's own session anchor and `ba0d09b` (the work commit adds only the fixture file), so the one-path attribution of the 401→402 delta is unverifiable as written. The figures themselves stand: the pristine-tree run reproduces the report's `402 Total / 180 Unique / 402 OK / 0 Errors` and HEAD prints `403 … / 0 Errors` — rule 14 holds on every figure claimed.
  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 pristine-tree line is in this review's VERIFIED. Next action is the planner's.
SHAPES: two probed shapes the suite does not build, named here:
  1. The graded wall's magnitude and load dependence, at selectable deadline values — the scratch probe (VERIFIED): natural wall `51.47s` (FAIL, idle, 300.0s) against the regression's crossing `60.04s` (CANDIDATE_TIMEOUT, 60.0s, external pool beside the pin's own). No committed member asserts the wall's magnitude; the committed pin guards the seam itself (the assertion at `:680`), which subsumes the class — the instrument existed only in the scratch and rides in this file, matching the report's SHAPES precedent (F31's reading); its removal with the scratch is why it is named here and not filed as a node id.
  2. The seam-regressed configuration (FINAL code with the fixture's `60.0` literal re-added) driving both pins: the red member is exactly `test_near_deadline_candidate_grades_fail_under_host_contention` on its FAIL-verdict assertion (`1 failed in 66.41s` under the external pool) and the determinism pin stays green (the `2 passed in 264.77s` idle pair) — the committed suite cannot build this configuration (its own fixture is the margin) so the member-level claim (which pin reds on the seam) had to be a scratch drive and is recorded in VERIFIED.
TRIPPED: none
PROPOSED ROWS: none
METHOD FRICTION: none — the embedded brief matched the committed standalone brief byte-for-byte (only the `--- END BRIEF UNDER REVIEW ---` copy-delimiter line differs); no template field deviates from docs/templates/report.txt.
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.
