IMPLEMENTER BRIEF — phase5-run-entry-fixes-9 (Phase 5: FFR-4's mutant prediction corrected; Phase 5 status current)

GOAL: FFR-4 is closed by this brief's own text under rule 8 — the fixes-8 review brief's mutant-(b) parenthetical "(the pin red on that member)" is corrected to the measured member (the pin reds on the empty member first; the whitespace member would red only in a matrix that reached it) — and `docs/self-host.md`'s Phase 5 status names the fixes-8 round so the exit gate's input is current. No code changes: the seam is delivered, the pin is green, and the mutant boundary it pins stands as measured.

CONTEXT: The fixes-8 step closed out (its review raises no P0 and no P1; [record.md](../record.md)'s row at REV `49e9840…`, Fixed 4 / Red 1 / Carried 1 / Declined 0 / Reviews 1). FFR-4 (P2, ORIGIN: BRIEF, carried by the fixes-8 review) is the loop's last carried finding — the loop's exit condition ("no P1 or P2 finding remains", the `Carried` column) is what this step pays. FFR-4's mechanism: the fixes-8 review brief's QUESTIONS TO ATTACK item 3 predicted the no-`strip()` mutant reds the pin "on that member" (the whitespace-only member the question is about), but without `strip()` the empty, whitespace-only, and tab members all pass the type test, and the loop-form pin reds on the empty member first since 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 — measured at `tests/test_run_entry_kernel_id_refusal.py:86` as `Failed: FRK-1: a empty kernel_id was admitted by validate_run_spec`. 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. The FFR-3 class: a mutant prediction in a committed review brief's prose has no regression test, so per rule 8's ORIGIN: BRIEF close form this committed brief corrects the prediction text. Pre-existing since the fixes-8 review brief's own authoring (`3862fbb`), not a regression of any code step. Gates measured at REV `49e9840` (this step's base): `scripts/check-tests --fast` prints `963 passed, 106 deselected in 65.91s (0:01:05)`; `scripts/check-docs` prints `372 Total (in 1s 79ms) 172 Unique 372 OK 0 Errors`; `scripts/check-static` exits 0 with the advisory line `Found 104 errors.`; the loader battery prints `7 passed` (2 new kernel-id cases + 2 envelope cases + 3 probes) and `54 passed` (the four earlier modules). No `docs/residuals.md` trigger glob matches this brief's IN SCOPE (the `PILOT-R*` triggers name `planning_pilot.py`, `controller.py`, `reducer.py`, `decomposition.py`, `model.py`, and `derive_obligations.py`; the store is byte-verified against `docs/residuals.md` before this brief's commit, rule 2). This brief touches no file under `tests/` or `scripts/`, so the standing `tests/test_phase3_project_oracle.py` line is not owed (it is named only for a brief that adds a file under `tests/` or `scripts/`). The Phase 5 status names seven reports through fixes-7 while nine rounds (through fixes-8) have closed — the status line is amended by the OWNER's own status-current convention (an OWNER commit, rule 5, like the fixes-7 closeout's `b68be80`), so this brief's DIVERGENCES names it and the implementer does not touch it.

INHERITED:

From `docs/research/phase5-run-entry-fixes-8-implementer.md`, its `INHERITED` block verbatim:

  INHERITED:
  none — the received INHERITED carried exactly four open items (FRK-1, FFR-1, FFR-2, FFR-3, moved into this brief's body). All four are disposed by this step: FRK-1 is fixed by this step's work (FINDINGS, FRK-1), and FFR-1, FFR-2, FFR-3 close by this brief's own text under rule 8 (FINDINGS). Nothing is carried forward and nothing new is left open.

From `docs/research/phase5-run-entry-fixes-8-review.md`, its `INHERITED` block verbatim:

  INHERITED:
  Nothing from the received set is still open: FRK-1 is fixed by the step under review (its red→green pair re-measured above), FFR-1, FFR-2, FFR-3 close by the brief under review's own text as R11 and rule 8 prescribe (each close adjudicated above), and F41 was closed at the fixes-7 closeout (no action). One new item is still open and carried forward by this review:
    FFR-4 (STATE: carried) — the review brief's mutant-(b) parenthetical "(the pin red on that member)" is falsified as written (the pin reds on the empty member first); a later committed brief corrects the prediction to the measured member.

The copied blocks' resolutions and the still-open finding are moved verbatim here so the brief is the actor's only input, each with this brief's disposition stated after the moved block. FRK-1, FFR-1, FFR-2, FFR-3 are fixed and closed — no action.

  FFR-4 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
  The 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 (`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` 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); a later committed brief corrects the prediction to the measured member (the pin reds on the empty member first; the whitespace member would red only in a matrix that reached it).
  This brief's disposition: this brief's own text IS the correcting text — the mutant-(b) correction below states the measured member (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), so per rule 8's ORIGIN: BRIEF close form, in your report FFR-4's `STATE` is `fixed` and its `FIXED:` line reads `no regression test` and names **this brief's commit** — obtain the sha before your work commit: `git rev-parse HEAD` is this brief's commit (the tree's tip at dispatch; cross-check with `git log -1 --format=%H -- docs/research/phase5-run-entry-fixes-9-brief.md`, which names the same sha). No code work belongs to FFR-4.

IN SCOPE: docs/self-host.md

RESIDUALS:

none — rule 3 selection for this brief's `IN SCOPE`: no `docs/residuals.md` trigger glob matches `docs/self-host.md` (the `PILOT-R*` triggers name `planning_pilot.py`, `controller.py`, `reducer.py`, `decomposition.py`, `model.py`, and `derive_obligations.py`; the store is byte-verified against `docs/residuals.md` before this brief's commit, rule 2). No residual row rides, so the residual half of `scripts/check-scope` has nothing to carry here and it prints `tripped: none` — the line your report's `TRIPPED` field copies.

OUT OF SCOPE:
- Editing this brief file (`docs/research/phase5-run-entry-fixes-9-brief.md`). A committed brief is never modified; a re-cut is a new file.
- `docs/self-host.md` beyond the Phase 5 status paragraph: only the status lines naming the recorded rounds change (fixes-8 added to the report list, F26–FRK-1/FFR-1–FFR-4 disposed, R11 consumed — the `b68be80` status-current form). The Phase 5 goal, exit gate, Phase 6/7/8 sections, and every other phase's status are untouched. If the status needs any other change, stop and report `IN SCOPE` as insufficient.
- `src/orchestrator/run_entry.py` in full: the seam is delivered (the six `kernel_id` guard lines, byte-identical to FINAL `ca9a25a` — diff it). No code is written, read-for-edit, or re-derived here. If acceptance needs a code change, stop and report `IN SCOPE` as insufficient.
- Every committed test module — `tests/test_run_entry_kernel_id_refusal.py` (the pin stays green as a maintained pin), `tests/test_run_entry_loader_envelope.py`, `tests/test_phase5_run_entry_fixes_6_review.py`, `tests/test_phase5_run_entry_fixes_5_review.py`, `tests/test_phase5_run_entry_fixes_4_review.py`, `tests/test_run_entry.py`, and `tests/test_phase5_run_entry_fixes_2_review.py` are read-only here. No test file is created or edited. If a pin would have to change for acceptance to pass, stop and report `IN SCOPE` as insufficient.
- `tests/open_defects.yaml` and the registry's meta-tests: no registration rides (FFR-4 is ORIGIN: BRIEF with no regression test, the FFR-3 class).
- Every other document: no `docs/tables/*` change and no table regeneration, no `docs/event-catalogue.md` change and no new event type, no `docs/control-plane.md` edit, no `docs/residuals.md` or `docs/record.md` edit, no `docs/method.md` or `docs/templates/` edit.
- The controller stack, the store, the experiment harness, `scripts/orchestrate.py`, `experiment_target.build_target`, `schemas.py`.
- Registry and control files: `tests/counterexamples.yaml`, `tests/guard_mutation_matrix.yaml`, `tests/fixture_fidelity.yaml`, `tests/verifier_registry.yaml`, `tests/spend_paths.yaml`, `tests/invariants.py`, `tests/helpers.py`, `pytest.ini`, tool configuration.
- No new dependencies, no tooling configuration, no reformatting. No new exception class and no `*Executor`/`*ModelClient` class or provider-registry registration.
- Name no test `test_bug_*` (the open-defect registry would then own it).

ACCEPTANCE: Commands (run every one and paste what each prints into `VERIFIED`; expected result is green, exit 0, for each):

    scripts/check-tests --fast
    .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
    .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
    scripts/check-static
    scripts/check-docs
    scripts/check-scope 49e98407fbe3c96ecbc093afafd2ff8b8e5185aa <FINAL> docs/research/phase5-run-entry-fixes-9-brief.md

Every `pytest` line names `.venv/bin/python -m pytest` deliberately (F17's carried correction: the bare `pytest` on PATH has no `pytest-timeout` and `pytest.ini`'s `strict_config = true` rejects it on this host — run these lines exactly as written and claim them under these names). The kernel-id module shares a line with the envelope module and the three absorbed probes — expected at FINAL: 7 passed (2 kernel-id cases + 2 envelope cases + 3 probes), exit 0. The four earlier modules are the loader's whole committed battery and must not regress (54 passed). The fast suite's expected shape: 963 passed, 106 deselected (the kernel-id module's two cases ride slow). The docs gate is expected green with 0 errors — and every count figure you write in `VERIFIED` is the gate's own printed line, never the REV line quoted in this brief's CONTEXT and never recomputed from memory (rule 14, the F41 class). The scope line is expected green, exit 0, printing `tripped: none` (and the `claimed:` line the parser prints). `REV` below names the step's base — the parent of this brief commit — and is not claimed to be `FINAL`'s parent (F4's lesson).

There is no red probe in the tree for FFR-4 (an ORIGIN: BRIEF prose defect has no regression test, the FFR-3 class): the step's red evidence is the fixes-8 review's own VERIFIED mutant-(b) measurement — without `strip()` the pin reds 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 empty member, not the whitespace member the review brief's parenthetical names). Re-measure it on a scratch copy if you wish (narrow the delivered check to `isinstance(kernel_id, str)`, diff-verified against `git show ca9a25a:src/orchestrator/run_entry.py`, run the kernel-id module); `FIXED` reads `no regression test` and names this brief's commit (obtained as for FFR-1 at fixes-8), never a node id. The pin is green at `FINAL` with no code change.

Mutant-(b) correction (FFR-4's close): narrow the delivered `kernel_id` check to `isinstance(kernel_id, str)` without the `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` so the loop never reaches the whitespace member. The whitespace-only member does pass (the review brief's main clause holds); the strip test covers empty/whitespace. A mutant prediction names the first member the runner reaches, not the member the question is about.

Maintained unchanged (no new test owed; green in the battery lines): the `kernel_id load refusal` pin, the `kernel_id fallback` pin, the envelope property (`Loader-refusal envelope`), the `Read-refusal pin`, and the absorbed typed-scalar probes (F38/F39/F40) — all green at `FINAL`, none edited; no code is touched, so every surface is undisturbed.

REV: 49e98407fbe3c96ecbc093afafd2ff8b8e5185aa
CLOSE OUT: yes
DIVERGENCES: the Phase 5 status paragraph in `docs/self-host.md` still names seven reports through fixes-7 while nine rounds (through fixes-8) have closed — amended by the OWNER's status-current convention (an OWNER commit, rule 5, like the fixes-7 closeout's `b68be80`); the implementer does not touch it.
REVIEW: one session — FFR-4's text-close above all: does this brief's mutant-(b) correction name the measured member (empty first, whitespace unreachable) with the node id, the named translation, and the matrix order as evidence, and does it restate no new mutant prediction of its own; is the `IN SCOPE` line plain with scope green; are the docs figures the gate's own printed lines (rule 14, no predicted total); is `run_entry.py` byte-identical to `ca9a25a` (the seam untouched — diff it) with every battery module green and no test edit; the full-suite and module counts and the report's forms (rules 7 and 14); and the Phase 5 exit gate's operator classes only where the validation stage touches them (a wrong-typed spec through the documented `start` head refuses at load with the store absent).

You implement one brief. You do not plan, re-scope, or decide what the work is. Read every file
in IN SCOPE before editing it; if what you find contradicts the brief, report that instead of
guessing. Modify only what IN SCOPE names. If you find uncommitted changes in the tree, stop and say
so. Stop and report rather than improvise when IN SCOPE is
insufficient, the brief contradicts the code, you have already failed twice at this goal, or the
requirement is ambiguous and no single reading is consistent with the rest of the brief. If exactly
one reading is consistent, take it and file a FINDING with ORIGIN: BRIEF that names the reading you
took. No new dependencies, no tooling configuration, no reformatting. Run every ACCEPTANCE command;
fix what is in scope and report what is not.

A defect in the brief is a FINDING, never METHOD FRICTION. METHOD FRICTION is only for the method and
its templates: any place you deviated from them, found them ambiguous, or found them silent. Report
friction you worked around — that is the section the method learns from.

Commit your own work. When ACCEPTANCE passes, commit the files you changed, and only those, in one
commit whose message ends with the trailer `Actor: IMPLEMENTER`. That commit's full sha is FINAL.
Then append docs/templates/report.txt verbatim, fill it in, write it to
docs/research/<phase>-<subject>-implementer.md, and commit it in a second commit with the same
trailer. Do not amend the first commit to add the report: FINAL must not change after the report
names it. If you cannot commit, stop and say so; do not leave work uncommitted for someone else to
commit.

# report.txt

REPORT — <phase>-<subject>-<role>
STEP: <implementer brief subject>
REV: <copied from the brief's REV — the step's base, not FINAL's parent>   FINAL: <implementer: sha of your work commit, never the commit that holds this report;
  reviewer: the sha under review, copied from the review brief>
CHANGED: <files, one line each>
VERIFIED: <command, duration, counts>
         Every VERIFIED and ACCEPTANCE claim names the command that actually ran — never a
         substituted interpreter, wrapper, or narrowed form. If the documented form cannot run in
         your environment, record both commands and the documented form's separate check.
NOT VERIFIED: <why, or none>
FINDINGS: none | one block each:
  ID | SEVERITY: P0|P1|P2 | ORIGIN: BRIEF|CODE|DOCUMENT | STATE: fixed|declined|carried
  <root cause, one line>
  FIXED: <node id, command, and the named failing assertion at REV — or "no regression test">
         An error or a collection failure is not red. The assertion has to be the thing that
         failed; a run that merely crashed proves nothing.
  STATE means: fixed (above); declined = not a defect, with the reason; carried = a real defect
  left unfixed, passed on in INHERITED. A defect you will not fix now is carried, never declined.
  An ORIGIN: BRIEF finding is fixed once a later committed brief corrects the text: FIXED: names
  that brief's commit and reads "no regression test". Carried means a future actor has something to
  do with it; at closeout a finding with no possible next action is closed — a defect in an
  already-committed report reads FIXED: recorded in the review that filed it, and an authoring
  lesson from a finished brief goes into record.md's Observations. IDs are stable keys: the F<n>
  sequence is the default, and a prefix must name its origin.
SHAPES: <shapes probed that the suite does not build, or none with a reason>
        Every shape this report names needs a test or an entry here: a hand measurement is not a
        test. A facet claimed unchanged is re-driven at FINAL when your fix touches its surface.
        SHAPES: none claims nothing probed is left unbuilt — never that unbuilt probes were left
        unnamed.
TRIPPED: <copied from check-scope's tripped: line>
PROPOSED ROWS: <ledger rows, or none>
METHOD FRICTION: none | <where you deviated from the method or its templates, misread them, or
  found them silent. A defect in the brief is a FINDING, not friction. This form is exhaustive:
  every field is filled and nothing outside it is added. A departure from the form is friction
  even when it changes no outcome — silence is not compliance.>
INHERITED:
<<every INHERITED item you received that is still open, copied verbatim; then each
  finding you marked carried, with its ID>>
Rule 2 governs the planner's copy of this block. What goes in it is yours: an implementer or
reviewer who received an obligation, finding, entry or trigger carries it forward verbatim, and
adds anything new that is still open. A block reading `none` is correct only when nothing came in
and nothing is open. INHERITED never carries residual rows; they are re-selected from the store per
brief.
