REPORT — phase5-run-entry-fixes-9-implementer
STEP: phase5-run-entry-fixes-9 (Phase 5: FFR-4's mutant prediction corrected; Phase 5 status current)
REV: 49e98407fbe3c96ecbc093afafd2ff8b8e5185aa   FINAL: ea9c3b000683d673dfd09336cb2f7b6a732c3a7a
CHANGED: docs/self-host.md — the Phase 5 status paragraph names the fixes-8 round: nine recorded rounds (fixes-8 added to the report list), F26–FRK-1/FFR-1–FFR-4 disposed, R11 consumed (FRK-1 refused at load; FFR-1–FFR-4 closed by the fixes-8 and fixes-9 briefs' text) — the `b68be80` status-current form the brief's OUT OF SCOPE names. No other line of the document changes; no code, no test, and no other document is touched — `git diff ca9a25a ea9c3b000683d673dfd09336cb2f7b6a732c3a7a -- src/orchestrator/run_entry.py` is empty (the seam's six `kernel_id` guard lines byte-identical to the fixes-8 step's FINAL `ca9a25a`).
VERIFIED: scripts/check-tests --fast — 963 passed, 106 deselected in 75.95s (0:01:15), exit 0 (the kernel-id module's two cases ride slow, so the fast suite's shape is unchanged from REV's 963 passed, 106 deselected).
VERIFIED: .venv/bin/python -m pytest tests/test_run_entry_kernel_id_refusal.py tests/test_run_entry_loader_envelope.py tests/test_phase5_run_entry_fixes_6_review.py — 7 passed in 5.51s, exit 0 (2 kernel-id cases + 2 envelope cases + 3 probes).
VERIFIED: .venv/bin/python -m pytest tests/test_phase5_run_entry_fixes_5_review.py tests/test_phase5_run_entry_fixes_4_review.py tests/test_run_entry.py tests/test_phase5_run_entry_fixes_2_review.py — 54 passed in 22.86s, exit 0 (the loader's whole committed battery, no regression).
VERIFIED: scripts/check-static — exit 0. The gated `ruff check --select BLE001,S110 src/orchestrator` prints "All checks passed!"; the advisory line prints "Found 104 errors." (unchanged from REV's 104).
VERIFIED: scripts/check-docs — exit 0. Prints "374 Total (in 918ms) 173 Unique 374 OK 0 Errors" — the gate's own printed line at FINAL (the brief's CONTEXT quoted REV's 372 before the fixes-9 brief's own links landed at `40d102b`; the count drifts as `docs/research/` grows, the FFR-2/rule-14 class, so only the gate's line is cited, never a predicted total).
VERIFIED: scripts/check-scope 49e98407fbe3c96ecbc093afafd2ff8b8e5185aa ea9c3b000683d673dfd09336cb2f7b6a732c3a7a docs/research/phase5-run-entry-fixes-9-brief.md — exit 0. Prints `claimed: docs/self-host.md`, `tripped: none`, `scope: ok (2 path(s) in 49e98407fbe3c96ecbc093afafd2ff8b8e5185aa..ea9c3b000683d673dfd09336cb2f7b6a732c3a7a)` (the two paths are the brief itself, added under `docs/research/` at `40d102b` and allowed implicitly, and the in-scope `docs/self-host.md`).
NOT VERIFIED: the full `scripts/check-tests` (no `--fast`): this brief's ACCEPTANCE names the `--fast` form, and the review's own check covers the full-suite counts (the brief's REVIEW names "the full-suite and module counts"), so the full run is the reviewer's, per the fixes-8 report's standing form.
FINDINGS:
  FFR-4 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: fixed
  The fixes-8 review brief's mutant-(b) prediction — "narrow the check to `isinstance(kernel_id, str)` without the `strip()` — does the whitespace-only member pass (the pin red on that member)" — is falsified as written on the red-member attribution: without `strip()` the empty, whitespace-only, and tab members all pass the type test, and the pin reds on the empty member first (`Failed: FRK-1: a empty kernel_id was admitted by validate_run_spec` at `tests/test_run_entry_kernel_id_refusal.py:86`), because empty precedes whitespace in `_WRONG_TYPED_KERNEL_IDS` (`tests/test_run_entry_kernel_id_refusal.py:60-68`) so the loop never reaches the whitespace member. The whitespace-only member does pass (the question's main clause holds) and the seam boundary the mutant pins is as stated (the strip test covers empty/whitespace); only which member names the red is wrong. Source: `docs/research/phase5-run-entry-fixes-8-review-brief.md`, QUESTIONS TO ATTACK item 3 (commit `3862fbb325932bb335f6fd13f95ff2ba4fb686d9`).
  FIXED: no regression test — a mutant prediction in a committed review brief's prose has none (the FFR-3 class); the correcting text is this brief's own mutant-(b) correction (the pin reds on the empty member first, at `tests/test_run_entry_kernel_id_refusal.py:86` with `Failed: FRK-1: a empty kernel_id was admitted by validate_run_spec`; the whitespace-only member passes but the loop never reaches it, and would red only in a matrix that reached it), fixed by this brief's commit `40d102b7d05d2a8a61240f8e5765b0b4d3d21636` (`git rev-parse HEAD` at dispatch, cross-checked with `git log -1 --format=%H -- docs/research/phase5-run-entry-fixes-9-brief.md`, which names the same sha). The red is re-measured on a diff-verified scratch copy: the mutant's diff against `git show ca9a25a:src/orchestrator/run_entry.py` is exactly the `strip()` removal at `src/orchestrator/run_entry.py:214`, and `.venv/bin/python -m pytest tests/test_run_entry_kernel_id_refusal.py -v` on the scratch copy fails at `tests/test_run_entry_kernel_id_refusal.py:86` with `Failed: FRK-1: a empty kernel_id was admitted by validate_run_spec` (1 failed, 1 passed in 0.42s — the fallback case is untouched by the mutant). The pin is green at FINAL with no code change (VERIFIED above).
  F43 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: fixed
  The brief's DIVERGENCES clause ("the implementer does not touch it") contradicts the brief's own work definition: GOAL ("`docs/self-host.md`'s Phase 5 status names the fixes-8 round so the exit gate's input is current"), IN SCOPE (`docs/self-host.md`), the OUT OF SCOPE status-line specification (fixes-8 added to the report list, F26–FRK-1/FFR-1–FFR-4 disposed, R11 consumed — the `b68be80` status-current form), ACCEPTANCE (`scripts/check-scope` requires a non-empty `REV..FINAL` diff, which an untouched `docs/self-host.md` cannot supply — it exits 1 naming FINAL), and the commit instructions (a work commit whose sha is FINAL) all assign the implementer the status-line edit, so the requirement is ambiguous and exactly one reading is consistent with the rest of the brief: the implementer applies the OWNER's `b68be80` status-current form to the status lines the OUT OF SCOPE bullet names and does not touch the status-current convention itself (rule 5 remains the OWNER's; the commit carries the `Actor: IMPLEMENTER` trailer the brief's commit instructions prescribe).
  FIXED: no regression test — a committed brief's prose has none, and this brief is the chain's last (the loop's exit condition is paid by FFR-4's close), so no later committed brief corrects the clause; the reading taken is named in this finding per the brief's own instruction ("If exactly one reading is consistent, take it and file a FINDING with ORIGIN: BRIEF that names the reading you took"), and the divergence the clause describes is closed by this step's work (the Phase 5 status names the fixes-8 round at FINAL, VERIFIED above) — the closeout form for a finding with no possible next action.
SHAPES: none — every shape the brief names has a test: the wrong-typed `kernel_id` matrix (dict, list, int, bool, explicit null, empty, whitespace-only) through `validate_run_spec` and the file-backed `load_run_spec` refusal with the store absent from the tmp dir are `test_kernel_id_load_refusal`'s loop and drive, and the missing-key fallback through `run_configuration` against a stub target is `test_kernel_id_fallback`; the envelope property (`Loader-refusal envelope`), the `Read-refusal pin`, and the absorbed typed-scalar probes (F38/F39/F40) ride the battery modules, all green at FINAL. The one shape probed that the suite does not build is the no-`strip()` mutant variant itself — FFR-4's counterfactual, measured on a diff-verified scratch copy as the finding's red evidence (FINDINGS, FFR-4); the suite must not build it, because the delivered check's `strip()` is the boundary the pin guards. No facet is claimed unchanged on a surface the fix touches — the fix touches no code surface, so every code facet is undisturbed by construction and re-driven green in the battery lines.
TRIPPED: none
PROPOSED ROWS: none
METHOD FRICTION: none
INHERITED:
none — the received INHERITED carried one open item (FFR-4, moved into this brief's body), closed by this brief's own text under rule 8 (FINDINGS, FFR-4). F43 is fixed, not carried (FINDINGS, F43). Nothing is carried forward and nothing new is left open.
