REPORT — phase6-probe-janitor-implementer
STEP: phase6-probe-janitor (Phase 6: killed probe runs are reaped — F15)
REV: e2271de   FINAL: 8e9d6af9865837df064b0f6f930116a49c8ce525
CHANGED: src/orchestrator/oracle.py — the janitor: `_PROBE_TREES` registry (`:611`), `_PROBE_TREE_PREFIXES` (`:612`), `_register_probe_tree` (`:615`) and `_reap_probe_trees` (`:620`) beside `_run_probe`; `_run_probe` registers `copy` the moment it is created (`:665`), registers `execution_copy` and the probe's sandbox root `f"{execution_copy}-root"` (`:725`–`:726`), and its `finally` calls `_reap_probe_trees()` (`:784`) in place of the two direct `shutil.rmtree`s — no signature, probe-shape, deadline, or digest change.
CHANGED: tests/test_probe_oracle.py — `_probe_tree_names` (`:138`) and `test_killed_probe_grade_reaps_every_intermediate_tree` (`:150`, the module's test after the containment matrix), carrying `@pytest.mark.timeout(120)`; it reuses `_check`/`_run` with a probe that builds its sandbox root then raises `KeyboardInterrupt`, and asserts the temp dir's probe-tree after-set minus before-set is empty (`:170`).
VERIFIED: scripts/check-tests --fast — `984 passed, 109 deselected in 89.47s (0:01:29)` (exit 0); the +1 on the brief's 983 baseline is this step's added pin.
VERIFIED: .venv/bin/python -m pytest tests/test_probe_oracle.py --durations=5 — `16 passed in 2.06s`; slowest five `0.51s` `test_harness_deadline_beats_the_probe_budget_review_n3`, `0.50s` `test_probe_deadline_and_base_exception_are_contained`, `0.27s` `test_flooding_candidate_is_bounded_and_graded`, `0.26s` `test_candidate_mutation_of_its_graded_copy_is_a_fail`, `0.21s` `test_expected_values_never_reach_the_candidate_process` (the new janitor pin is 0.09s).
VERIFIED: scripts/check-static — exit 0, gated `All checks passed!`, advisory `Found 104 errors.` (unchanged; the added janitor draws no new advisory).
VERIFIED: scripts/check-docs — `400 Total / 180 Unique / 400 OK / 0 Errors` (exit 0); the figure is the gate's own printed line — the brief's `399` baseline predates the brief commit, whose added `docs/research/phase6-probe-janitor-brief.md` is the one-path 399→400 delta (the F28 class).
VERIFIED: scripts/check-scope e2271de 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 e2271de..8e9d6af)`.
VERIFIED: red at REV on a scratch tree — `git archive e2271de | tar -x` into `/tmp/kilo/probe-janitor-rev` (`oracle.py` diff-verified byte-identical to `git show e2271de:src/orchestrator/oracle.py`; the shared `.venv` symlinked in; the delivered pin module copied over). `.venv/bin/python -m pytest tests/test_probe_oracle.py::test_killed_probe_grade_reaps_every_intermediate_tree -q` → `1 failed in 0.17s`, the named failing assertion `assert _probe_tree_names() - before == set()` with `AssertionError: assert {'orchestrator-probe-exec-v3kazh9h-root'} == set()` — the probe's sandbox root stands after the contained kill path under the finally-only reaping. Green at FINAL: the same node `1 passed` (module `16 passed in 2.06s`).
VERIFIED: green at FINAL, the commit's own hook — the work commit's pre-commit hook ran the standing battery at the committed tree: parallel phase `950 passed in 21.56s` and serial phase (batch3 + milestone3 modules) `34 passed in 12.66s`.
NOT VERIFIED: none
FINDINGS:
  F15 | SEVERITY: P2 | ORIGIN: CODE | STATE: fixed
  `_run_probe`'s `finally` named and reaped only the two `mkdtemp` trees, so the probe's sandbox root (`f"{execution_copy}-root"`, the `new_root` shape `hidden_oracle` builds) stood after a grade that did not return through a teardown naming it.
  FIXED: `tests/test_probe_oracle.py::test_killed_probe_grade_reaps_every_intermediate_tree` (`:150`, assertion `:170`), command `.venv/bin/python -m pytest tests/test_probe_oracle.py::test_killed_probe_grade_reaps_every_intermediate_tree`. At REV, on the scratch tree above, the named failing assertion is `assert _probe_tree_names() - before == set()` — `AssertionError: assert {'orchestrator-probe-exec-v3kazh9h-root'} == set()`. Green at FINAL: `1 passed`; the module `16 passed in 2.06s`. Delivered at `src/orchestrator/oracle.py:611`–`:637`, `:665`, `:725`–`:726`, `:784`.
  F30 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
  The brief's named red is chimeric as literally written and its GOAL overstates what an in-`_run_probe` reaper can do. 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 (`_run_probe` returns `GRADE_INFRASTRUCTURE_ERROR`, after-minus-before empty); the grading-seed review measured the same ("the cleanup is correct on every path this review exercised"). The reading taken: the pin models the probe's sandbox root sibling (`f"{execution_tree}-root"`, `hidden_oracle.py:233`'s `new_root`), the tree the finally-only reaping does not name and the one the emptiness assertion catches at REV. Separately, the GOAL's "a SIGKILLed ... grade cannot fill the shared tmpfs" clause is not reachable inside `_run_probe`: a SIGKILLed runner executes no Python and runs no reaper, so the SIGKILL residue F15 names still needs the cross-process tombstone/janitor F15's own next action names — out of this brief's IN SCOPE.
  FIXED: no regression test — an ORIGIN: BRIEF finding is fixed once a later committed brief corrects the text; the janitor lands as described (registry + finally-called reaper over the two trees and the sandbox root) and is green at FINAL.
SHAPES: none — the one named shape (`Probe-janitor shape` (F15): a killed probe run's trees are gone after the grade) is built by `test_killed_probe_grade_reaps_every_intermediate_tree`: the run's sandbox root stands at REV on the finally-only reaping and is reaped at FINAL.
TRIPPED: none
PROPOSED ROWS: none
METHOD FRICTION: none
INHERITED:

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