REPORT — phase5-run-entry-fixes-7-implementer
STEP: phase5-run-entry-fixes-7 (the loader's refusal envelope — F38–F42)
REV: b7a010a1cbc984493033d9bd4872d7aeacfe9b48   FINAL: 00577a4e14fcb03e61f5868d9a8cbef7e195e1e2
CHANGED: src/orchestrator/run_entry.py — `load_run_spec`'s two except clauses collapse to the seam and its docstring plus `RunSpecError`'s docstring name the host-resource boundary; every other function and the module docstring are byte-identical to REV.
CHANGED: tests/test_run_entry_loader_envelope.py — new module: the `Loader-refusal envelope` generated-input property and the `Read-refusal pin`, both slow-marked.
VERIFIED: scripts/check-tests --fast — 961 passed, 104 deselected in 68.27s, exit 0 (passed unchanged from REV's 961; deselected grew from 102 by this module's two cases).
VERIFIED: .venv/bin/python -m pytest tests/test_run_entry_loader_envelope.py tests/test_phase5_run_entry_fixes_6_review.py — 5 passed in 4.34s, exit 0 (2 new cases + the three absorbed probes, green with no test edit).
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.32s, exit 0 (the loader's whole committed battery, no regression).
VERIFIED: .venv/bin/python -m pytest tests/test_phase3_project_oracle.py — 5 passed in 213.88s (0:03:33), exit 0.
VERIFIED: scripts/check-static — exit 0. Gated `ruff check --select BLE001,S110 src/orchestrator` prints "All checks passed!"; the advisory `ruff check --select B,SIM --exit-zero src/orchestrator tests` prints "Found 104 errors" (104 advisory rows, unchanged from the fixes-6 step).
VERIFIED: scripts/check-docs — exit 0. Prints "Checking table formatting... Verifying generated tables... Table verification passed. Linting Markdown... Checking documentation links... 363 Total (in 789ms) 170 Unique 363 OK 0 Errors". The total is 363, not the brief's predicted 361: lychee scans `**/*.md`, and this brief's own two `[record.md](../record.md)` links add exactly two (see FFR-2).
VERIFIED: scripts/check-scope b7a010a1cbc984493033d9bd4872d7aeacfe9b48 00577a4e14fcb03e61f5868d9a8cbef7e195e1e2 docs/research/phase5-run-entry-fixes-7-brief.md — exit 1, NOT green: prints `scope: src/orchestrator/run_entry.py is in the diff and not in IN SCOPE`, `scope: tests/test_run_entry_loader_envelope.py is in the diff and not in IN SCOPE`, then `tripped: none`. The substantive half passes (the two changed paths are exactly the brief's intended files) and the failure is the brief's IN SCOPE text format, not an out-of-scope change (see FFR-1). Expected green could not be achieved by any in-scope action.
NOT VERIFIED: the full `scripts/check-tests` (no `--fast`): the brief's standing rule assigns the full run to the reviewer and the implementer does not re-run it. `scripts/check-scope`'s expected green exit 0: it exits 1 on the brief's own IN SCOPE formatting (FFR-1); the `tripped: none` line it prints is the report's TRIPPED value.
FINDINGS:
  F38 | SEVERITY: P1 | ORIGIN: CODE | STATE: fixed
  A malformed typed scalar (`!!int`/`!!float`) failed the safe constructor's own conversion and raised a raw `ValueError` out of `yaml.safe_load`; not a `yaml.YAMLError`, it escaped the delivered `(yaml.YAMLError, UnicodeDecodeError, RecursionError)` tuple and `load_run_spec` raw.
  FIXED: tests/test_phase5_run_entry_fixes_6_review.py::test_review_f38_int_float_typed_scalar_refused_as_a_named_run_spec_error — at REV `.venv/bin/python -m pytest tests/test_phase5_run_entry_fixes_6_review.py -v` failed at tests/test_phase5_run_entry_fixes_6_review.py:35 with `Failed: F38: an ill-typed int scalar is refused as ValueError, not the documented named \`RunSpecError\`: ValueError("invalid literal for int() with base 10: 'garbage'")`; at FINAL the same command is green with no test edit — the whole-face seam catches it.
  F39 | SEVERITY: P1 | ORIGIN: CODE | STATE: fixed
  A malformed `!!timestamp` typed scalar raised a raw `AttributeError` (`'NoneType' object has no attribute 'groupdict'`) or `ValueError` out of the safe constructor, escaping the tuple raw.
  FIXED: tests/test_phase5_run_entry_fixes_6_review.py::test_review_f39_timestamp_typed_scalar_refused_as_a_named_run_spec_error — at REV the same command failed at tests/test_phase5_run_entry_fixes_6_review.py:55 with `Failed: F39: an ill-typed timestamp scalar (nope) is refused as AttributeError, not the documented named \`RunSpecError\`: AttributeError("'NoneType' object has no attribute 'groupdict'")`; green at FINAL with no test edit.
  F40 | SEVERITY: P1 | ORIGIN: CODE | STATE: fixed
  A malformed `!!bool` typed scalar raised a raw `KeyError` out of the safe constructor, escaping the tuple raw.
  FIXED: tests/test_phase5_run_entry_fixes_6_review.py::test_review_f40_boolean_typed_scalar_refused_as_a_named_run_spec_error — at REV the same command failed at tests/test_phase5_run_entry_fixes_6_review.py:71 with `Failed: F40: an ill-typed bool scalar is refused as KeyError, not the documented named \`RunSpecError\`: KeyError('garbage')`; green at FINAL with no test edit.
  F41 | SEVERITY: P2 | ORIGIN: DOCUMENT | STATE: carried
  The fixes-6 implementer report's `VERIFIED` figure "links 364/364 OK" does not match what the gate prints for the committed content: `scripts/check-docs` measures `366 Total / 366 OK / 0 Errors` on the REV and FINAL trees, and the range's own diff adds the brief's single local `../record.md` request — no content state in the measured neighbourhood prints 364. A copied-or-guessed figure rather than a run record (J-class, a direction that changed nothing material).
  FIXED: no regression test — a prose figure in a committed report has none; the close form is the review that filed this one and, at closeout, a record.md Observations line for the count-figure class. Nobody edits a committed report; carried verbatim, no implementer action.
  F42 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: fixed
  The malformed-class corpus was counted at nineteen in the fixes-6 review brief's QUESTIONS line and the fixes-5 review's banner while the fixes-5 review's own VERIFIED corpus line names exactly seventeen.
  FIXED: no regression test — the correcting text is this brief's own CONTEXT paragraph, which names the corpus size from the fixes-5 review's VERIFIED list as **seventeen named classes** and never as nineteen; fixed by this brief's commit `76a37a50431c04eb4d1c3a343b4710bb0ee5e678`.
  FFR-1 | SEVERITY: P1 | ORIGIN: BRIEF | STATE: carried
  The brief's `IN SCOPE:` line wraps both intended paths in backticks inside one prose line (`` `src/orchestrator/run_entry.py` … `tests/test_run_entry_loader_envelope.py` …``); `scripts/check-scope`'s awk extractor tokenises on commas/whitespace but does not strip backticks, so the claimed patterns are the literal strings `` `src/orchestrator/run_entry.py` `` / `` `tests/test_run_entry_loader_envelope.py` `` and match no path. The gate therefore exits 1 naming both intended files "not in IN SCOPE", and the ACCEPTANCE line requiring it green cannot be satisfied by any in-scope action (editing the brief is OUT OF SCOPE; the two files are the only diff).
  FIXED: no regression test — a committed brief's prose has none; per rule 8's ORIGIN: BRIEF close form a later committed brief corrects the IN SCOPE text to plain, un-backticked paths on their own lines as the fixes-6 brief does, after which `scripts/check-scope` is green. The residual half already prints `tripped: none`.
  FFR-2 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: carried
  The brief's ACCEPTANCE sentence says the docs gate's printed total at REV (361 total, 361 OK, 0 errors) "is expected to hold"; at FINAL `scripts/check-docs` prints 363 total / 363 OK / 0 errors. The +2 is the brief's own two `[record.md](../record.md)` links, which lychee counts because it scans `**/*.md` and the brief is itself committed in `docs/research/`. The gate is green and 0-errors; only the predicted figure is stale.
  FIXED: no regression test — a count figure in a committed brief's prose has none; a later committed brief corrects or drops the predicted figure, naming the gate's own printed line (the F41 class).
SHAPES: none — every shape the brief names has a test. `Loader-refusal envelope` and `Read-refusal pin` are this module's two cases; `Absorbed typed-scalar probes` are the three committed `test_review_f38/f39/f40` probes, green at FINAL with no test edit. Maintained unchanged and green in the battery line: F34 (`ParserError`), F37 (`UnicodeDecodeError`), F36 (`RecursionError`).
TRIPPED: none
PROPOSED ROWS: none
METHOD FRICTION: none
INHERITED:
From `docs/research/phase5-run-entry-fixes-6-implementer.md`, its `INHERITED` block verbatim:
  INHERITED:
  none — the received INHERITED carried exactly one open item, F36 (the fixes-5 review's carried P2, moved into this brief's body). It is fixed in this step (FINDINGS, F36); nothing is carried forward and nothing new is left open.
From `docs/research/phase5-run-entry-fixes-6-review.md`, its `INHERITED` block verbatim:
  INHERITED:
  F38, F39, F40, F41, F42 are filed carried by this review and live in its FINDINGS above. Nothing else is still open: what this review received is fully disposed — F36 (the only item carried by the fixes-5 review's INHERITED) is fixed by the step under review (its red probe green in both full runs with no test edit), F37 is fixed at the fixes-5 step and green as a maintained pin, the fixes-5 implementer's INHERITED block reads none with nothing open, and the brief's two copied blocks resolve to those same two findings.
Still open and carried forward by this step:
  F41 (STATE: carried) — the fixes-6 implementer report's "links 364/364 OK" figure; a defect in an already-committed report, carried verbatim above, closed by the planner at this step's closeout (no implementer action).
  FFR-1 (STATE: carried) — the brief's backticked IN SCOPE line defeats `scripts/check-scope`; a later committed brief corrects the IN SCOPE text.
  FFR-2 (STATE: carried) — the brief's predicted docs total 361 is 363 at FINAL; a later committed brief corrects the figure.
