REPORT — phase6-probe-janitor-review
STEP: phase6-probe-janitor (Phase 6: killed probe runs are reaped — F15)
REV: e2271de   FINAL: 8e9d6af9865837df064b0f6f930116a49c8ce525
CHANGED: docs/research/phase6-probe-janitor-review.md — this report. No review code rides: every attack re-drove the delivered pin, REV/FINAL scratch copies diff-verified byte-identical against `git show <rev>:…` before use, or scratch mutants of those copies; the chimeric-red re-drives ran on one scratch-only probe file (named in SHAPES), so no new test file is offered.
VERIFIED: REVIEW ACCEPTANCE run first (the method's only gated check): `scripts/check-scope e2271de17c3cd14a54bafda7d3f20dd8bb0d0331 8e9d6af9865837df064b0f6f930116a49c8ce525 docs/research/phase6-probe-janitor-brief.md` — exit 0, `claimed: src/orchestrator/oracle.py tests/test_probe_oracle.py`, `tripped: none`, `scope: ok (3 path(s) in e2271de17c3cd14a54bafda7d3f20dd8bb0d0331..8e9d6af9865837df064b0f6f930116a49c8ce525)`. The review tree is clean at the plan commit `8d00b4b`; `git diff 8e9d6af… 8d00b4b… --stat` names only the implementer report and this brief's file — the src/test trees are byte-identical between FINAL and the review tree. `git diff e2271de… 8e9d6af… --stat` names exactly three paths — the two IN SCOPE files plus `docs/research/phase6-probe-janitor-brief.md` (added by the planner's `bf2fc20` inside the range) — no committed test edit outside IN SCOPE. The brief's embedded copy (review-brief lines 20–189) is byte-identical to the committed `docs/research/phase6-probe-janitor-brief.md` (170 lines each) — no ORIGIN: BRIEF divergence rides. The work commit `8e9d6af…` and the report commit `d1ca08f` both carry `Actor: IMPLEMENTER`; this session wrote none of the commits under review; FINAL is the work commit, never the report commit.
VERIFIED: Q1(a) — the kill-path pin re-driven in both directions on scratch copies. REV scratch (`/tmp/kilo/rev-scratch`, `git archive e2271de | tar -x`; `src/orchestrator/oracle.py` and `tests/test_probe_oracle.py` each diff-verified identical to `git show e2271de:…`; the shared `.venv` symlinked in; the delivered pin module copied over and diff-verified to `git show 8e9d6af:tests/test_probe_oracle.py`; the imported oracle confirmed to be the scratch's own file with no `_reap_probe_trees` on it): `.venv/bin/python -m pytest tests/test_probe_oracle.py --durations=5 -q` (workdir the scratch) → `1 failed, 15 passed in 2.33s` — the named failing assertion is the pin's emptiness assertion `assert _probe_tree_names() - before == set()` (`tests/test_probe_oracle.py:170`), `AssertionError: assert {'orchestrato…-root'} == set()`, extra item `orchestrator-probe-exec-1dl2yglx-root` — the sandbox-root sibling stands after the contained kill path under the finally-only reaping, an assertion failure and not an error or a hang, and it is the same class as the implementer's own red line (`{'orchestrator-probe-exec-v3kazh9h-root'}`, replayed in kind). FINAL scratch (`git archive 8e9d6af | tar -x`, byte-verified, the imported oracle confirmed with the reaper): the same node inside the module `16 passed in 2.03s`. Red at REV and green at FINAL, both re-driven by this review — attacked-and-not-falsified.
VERIFIED: Q1(b) — the seam is one registry the teardown calls rather than a caller contract, and each registration is individually pinned. Grep over `src/`: `_register_probe_tree` is called only inside `_run_probe` (`src/orchestrator/oracle.py:665`, `:725`, `:726`), `_reap_probe_trees` only from `_run_probe`'s `finally` (`:784`); the registry `_PROBE_TREES` (`:611`) and `_PROBE_TREE_PREFIXES` (`:612`) are module-level and imported by no other module — the caller of `_run_probe` names nothing. Mutant M1 at the FINAL scratch, both `:725`–`:726` registration lines dropped (the mutant's diff is exactly `725,726d724`, those two lines): `.venv/bin/python -m pytest tests/test_probe_oracle.py --durations=5 -q` → `1 failed, 15 passed in 1.98s` — the janitor pin is the one member that reddens, on the emptiness assertion `:170`, with the execution copy and its sandbox root standing (`orchestrator-probe-exec-u7urxjnf`, `orchestrator-probe-exec-u7urxjnf-root`); no other member of the module changes verdict. Mutant M2, only the sandbox-root registration `:726` dropped (diff exactly `726d725`): the same pin on the same assertion with only `orchestrator-probe-exec-wttd_mph-root` standing (`1 failed in 0.18s`). Each member of the registration pair is held by the committed pin — no caller contract, not even a two-line one.
VERIFIED: Q1(c) — the reaped set is exactly the run's own trees; attacked-and-not-falsified. Function-level probes against the FINAL scratch oracle in one process: an unregistered prefix-matching direct child of the system tempdir survives the reap; a registered path whose parent is not the tempdir survives; a registered basename without the prefix survives; a registered tree whose removal must fail (parent chmod 0500) survives silently; a registered nonexistent path is silent; the positive control (registered, prefix-matching, direct child) is reaped; the registry is drained after the reap. Instrumented with a `shutil.rmtree` spy plus a `sys.addaudithook` trace: the reaper's `shutil.rmtree` targets registered paths only. The first probe round observed an "unregistered" path removed — falsified as this review's own probe bug (that path sat inside the script's registration loop); the instrumented re-run removes nothing unregistered. Blast radius: only the three names `_run_probe` registers — the `orchestrator-probe-` mkdtemp (`:665`), the `orchestrator-probe-exec-` mkdtemp (`:725`), and the `f"{execution_copy}-root"` sibling (`:726`) — and the third tree is real: `hidden_oracle.py:233` builds `new_root=f"{tree_path}-root"` and reaps it there only on settled paths (`hidden_oracle.py:257`).
VERIFIED: Q2 — F30's chimeric-red claim holds on both re-drives, and the janitor is not vacuous. (i) The merely-raising probe against the delivered finally-only reaping at REV: a scratch-only probe (`tests/test_scratch_merely_raising.py::test_merely_raising_probe_against_finally_only_reaping` in the REV scratch, the module's `_check`/`_run` surface, a probe that only raises `KeyboardInterrupt`, assertion `assert _tree_names() - before == set()`) → `1 passed in 0.26s` — green: the interrupt is contained to `GRADE_INFRASTRUCTURE_ERROR` and the delivered `finally` already reaps both mkdtemp trees, so the brief's named red as literally written does not reproduce. (ii) The sandbox-root shape at REV: the delivered pin's own red above — the third tree stands. Adjudication: the delivered red class is the unnamed third tree the delivered `finally` did not name, so the step does fix a leak class the prior reaping did not close — on the in-process kill paths (the contained `KeyboardInterrupt` arm and the SIGALRM `_Deadline` arm, both of which return through the `finally`) the grade now leaves nothing. The GOAL's "a SIGKILLed … grade cannot fill the shared tmpfs inode table" clause is not delivered and is not deliverable inside `_run_probe`: a SIGKILLed runner executes no Python, the registry dies with the process and the trees stand — the SIGKILL residue still needs the cross-process tombstone/janitor F15's own next action names, out of this brief's IN SCOPE. The second consistent reading exists and is the one delivered: the red exists on the sandbox-root sibling shape (`new_root`, the way `hidden_oracle` builds it); the brief's red prescription is simply wrong as written and rides as the carried F30 text correction. Not a return to planning: the delivery matches the brief's own delivery paragraph (registry plus a finally-called reaper over the two trees and the sandbox root), and both red directions were re-driven by this review.
VERIFIED: Q3 — the report's forms and counts, every figure the gate's own printed line (rule 14), and FINAL is the work commit `8e9d6af9865837df064b0f6f930116a49c8ce525`, never the report commit `d1ca08f` (line 3; both commits' trailers inspected). Re-run at the review tree (src/test-identical to FINAL): `scripts/check-tests --fast` — `984 passed, 109 deselected in 97.39s (0:01:37)`, exit 0 — the report's count, the delta over the brief's `983 passed` REV baseline exactly the one janitor pin; `.venv/bin/python -m pytest tests/test_probe_oracle.py --durations=5` — `16 passed in 1.99s` (slowest five `0.51s`/`0.50s`/`0.25s`/`0.22s`/`0.21s`; the janitor pin not among the slowest five (under the `0.21s` fifth wall), well inside its `timeout(120)`); `scripts/check-static` — exit 0, gated `All checks passed!`, advisory `Found 104 errors.` — the report's figures, unchanged from REV; `scripts/check-docs` — `401 Total / 180 Unique / 401 OK / 0 Errors` at the review tree, and at the pristine FINAL scratch `400 Total / 180 Unique / 400 OK / 0 Errors` — the report's figure is the gate's own printed line at the tree it names (the review tree's +1 is the docs commits after FINAL's tree; each figure stands where it was printed); `scripts/check-scope` — `tripped: none`, matching the report's TRIPPED field. The report's CHANGED line numbers verified against the delivered files (`_PROBE_TREES` `:611`, `_PROBE_TREE_PREFIXES` `:612`, `_register_probe_tree` `:615`, `_reap_probe_trees` `:620`, registrations `:665`/`:725`/`:726`, the finally's reaper call `:784`; `_probe_tree_names` `:138`, the pin `:150`, the assertion `:170`). The report's red-at-REV scratch construction re-driven as it describes (git archive extraction; the shared `.venv` symlinked in; the delivered pin module copied over). The inherited F15: the received carried rows move verbatim in the report's INHERITED and the disposition lands in FINDINGS — fixed with the named node id, command, failing assertion, and delivered lines (`:611`–`:637`, `:665`, `:725`–`:726`, `:784`), the brief's expected rule-8 form ("F15 fixed with red evidence"); the received dispositions otherwise kept; F30 filed and carried. Every field of the template present and filled, nothing outside it.
VERIFIED: standing battery — `scripts/check-tests` (no arguments, the full run, this review's falsification ground): the first run died in fixture setup with `OSError: could not create numbered dir with prefix … in /tmp/pytest-of-ruben/pytest-202 after 10 tries` — the shared /tmp at 100% inodes (3 free), the leaked class F15's CONTEXT names live on this host (54 standing `orchestrator-probe-*` trees measured before the prune; the taxonomy's contention row — isolation, never a value change). After freeing this review's scratch (91,236 files) and the leaked trees, the full run: `1093 passed in 1012.56s (0:16:52)` — the counted whole (984 fast pins + 109 slow), all green, no skip and no flake; `tests/test_probe_oracle.py ................` green inside it.
NOT VERIFIED: the report's live hook line (the work commit's pre-commit hook: parallel phase `950 passed in 21.56s`, serial phase `34 passed in 12.66s`) is not re-driven in that exact form — re-committing would touch the history under review; its class (the delivered tree green across the whole battery) is re-driven by this review's fast run (984 passed, 109 deselected) and the full standing battery (1093 passed). Everything else the report claims was re-driven or inspected at the named revisions.
FINDINGS:
  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.
SHAPES: two probed, both left unbuilt with reasons. (1) The merely-raising kill-path shape at REV (F30's measurement, re-driven by this review on the REV scratch): the delivered pin builds the sandbox-root variant only; the merely-raising shape's guard is subsumed by the delivered pin (M1/M2), so nothing distinct is left uncovered — listed for the planner's absorption decision alongside F31. (2) The reaper's no-over-reach scoping (an unregistered prefix-matching direct child of the tempdir must survive the reap; a registered out-of-tempdir or no-prefix path must survive): probed at the function level, unbuilt — the over-reach class can only arise from registry contents, whose three writers sit inside `_run_probe` and are covered by the janitor pin, but a drift of `_PROBE_TREE_PREFIXES` or of the tempdir guard itself would be unguarded by the committed suite; for the planner's absorption decision. The mutation drives (M1/M2) are red evidence for Q1(b), not shapes to build.
TRIPPED: none
PROPOSED ROWS: none
METHOD FRICTION: none — the scratch-tree `.venv` resolution gap the prior report recorded was applied as that recorded workaround from the start (the shared `.venv` symlinked into both scratch trees before any gate line was trusted); no other deviation from the method or its templates. (A first REV drive ran at the wrong workdir and was discarded before any claim; its figures appear nowhere in this report.)
INHERITED:

From `docs/research/phase6-probe-janitor-brief.md` (the step's own committed brief), its `INHERITED` block verbatim — the chain through the scan-anchor implementer, the probe-scope review, and the scan-anchor review's received F28/F29 dispositions:

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.

Expected dispositions (rule 8 forms): F15 fixed with red evidence (named below — the killed run's trees are gone after the kill, red on the delivered `finally`-only reaping, green at FINAL). F28/F29 stay carried (document deviations in committed reports, absorbed only by later steps' corrections). F11/F12/F18/F19/F20/F24/F25/F27 stay fixed as recorded in the reports that filed them. F13/F14/F16/F17/F21–F23/F26 stay carried with their named owners and text corrections.

Then each finding this review leaves carried, 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` — both re-driven and adjudicated by this review: the delivered red class is the unnamed third tree, the sandbox-root sibling `f"{execution_copy}-root"`; see this review's VERIFIED Q1(a)/Q2; 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 none-claim vs its own F30 merely-raising measurement — see FINDINGS above; its next action is the planner's correction of the carried note).

Received-set dispositions (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.
