REPORT — phase5-exit-gate-implementer
STEP: phase5-exit-gate (Phase 5: claim the exit gate — the loop's exit is the gate)
REV: 21d891aaa6d572adcfcb24fd6f762b6b0485040a   FINAL: b6bc9f3a6de41df4ffed0ef6b10110ff0d3c5ceb
CHANGED: docs/self-host.md — the Phase 5 status paragraph claims the exit gate: the status marker flips from "in progress" to "delivered" and the exit-gate sentence ("The exit gate is not yet claimed") is replaced by the claim with its evidence (the five operator classes re-driven live at FINAL through the documented `python3 scripts/orchestrate.py` heads against a real frozen repository, `run_entry.py` byte-identical to `ca9a25a`, the pin battery green). The ten-round delivery sentence and the disposal sentence stand; the goal, the exit-gate definition, and every other phase's status are untouched. No code, no test, and no other document is touched — `git diff ca9a25a b6bc9f3a6de41df4ffed0ef6b10110ff0d3c5ceb -- src/orchestrator/run_entry.py` is empty (the seam byte-identical to the fixes-8 step's FINAL `ca9a25a`).
VERIFIED: scripts/check-tests --fast — 963 passed, 106 deselected in 96.01s (0:01:36), 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 7.24s, 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 25.67s, 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 "376 Total (in 1s 89ms) 174 Unique 376 OK 0 Errors" — the gate's own printed line at FINAL (the count is unchanged from REV's 376/174/376/0: the status edit adds no links, so only the gate's line is cited, never a predicted total).
VERIFIED: scripts/check-scope 21d891aaa6d572adcfcb24fd6f762b6b0485040a b6bc9f3a6de41df4ffed0ef6b10110ff0d3c5ceb docs/research/phase5-exit-gate-brief.md — exit 0. Prints `claimed: docs/self-host.md`, `tripped: none`, `scope: ok (2 path(s) in 21d891aaa6d572adcfcb24fd6f762b6b0485040a..b6bc9f3a6de41df4ffed0ef6b10110ff0d3c5ceb)` (the two paths are the brief itself, added under `docs/research/` at `a44cb9f` and allowed implicitly, and the in-scope `docs/self-host.md`).
VERIFIED: the gate claim re-driven live at FINAL — the five operator classes as subprocesses through the documented `python3 scripts/orchestrate.py` heads against a real frozen repository (each created via `git init`/`add`/`commit`, one derivable component), 43 checks, 0 failures: (a) accept — `start` exits 0, JSON `accepted: true`, `outcome: ACCEPTANCE_CLAIMED`, no traceback, and the document's outcome equals a fresh connection's `replay_fresh` outcome; (b) failing-command refusal — exit 1, `accepted: false`, `outcome: INFEASIBLE`, no traceback, the document equal to the durable fresh outcome, and `stop` on the settled run exits 0 with the outcome un-re-written; (c) wall-clock timeout (`limits.wall_clock_seconds: 1`, a sleeping command) — exit 1, `INFEASIBLE`, no traceback, the document equal to the durable fresh outcome; (d) mid-run cancel — the second process's documented `stop` head exits 0 and the launcher exits 1 with `accepted: false`, `outcome: CANCELLED`, the document equal to the durable fresh replay; (e) the validation-stage face — a wrong-typed spec (a dict `project_kernel.kernel_id`) through the documented `start` head refuses at load with the store absent (terminal exception `orchestrator.run_entry.RunSpecError: project_kernel.kernel_id must be a non-empty string is invalid: {'a': 1}`); `inspect` reads clean in every externally drivable case.
VERIFIED: `git diff ca9a25a -- src/orchestrator/run_entry.py` is empty — the seam is byte-identical to `ca9a25a`, and no test module is edited.
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-9 report's standing form.
FINDINGS:
  F1 | SEVERITY: P2 | ORIGIN: BRIEF | STATE: fixed
  The brief's OUT OF SCOPE parenthetical names only the exit-gate sentence replacement and the ten-round sentence standing, and does not name the status marker; keeping "Status: **in progress.**" beside "The exit gate is claimed" would be self-contradictory and would not record the claim the GOAL requires.
  FIXED: no regression test — a committed brief's prose has none; the reading taken is the one consistent with the brief's GOAL ("the Phase 5 status records the claim"): a claimed exit gate is a delivered phase (the Phases 1/2/3 convention), so the status marker flips from "in progress" to "delivered" as the claim's necessary companion, in the same work commit as the exit-gate sentence replacement. No brief text correction is needed because no other reading keeps the GOAL's sentence true. Named 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").
SHAPES: none — every shape the re-drive probed has its pin in the committed battery: the accept face is `test_start_shape_authorises_acceptance` and `test_settled_start_shape_relative_workdir`; the failing-command-refusal face is `test_start_shape_records_a_refusal_without_authorising`; the wall-clock-timeout face is `test_settled_start_shape_wall_clock_overrun`; the mid-run-cancel face (the second process's `stop`, the launcher's exit 1, `outcome: CANCELLED`) is `test_cancelled_launcher_shape` and the `test_cancel_race_class_shape`/`test_cancel_race_shape_stop_after_observation`/`test_stale_admission_race_log_replays` class; the validation-stage face (a wrong-typed spec refusing at load with the store absent) is `test_kernel_id_load_refusal`'s file-backed drive and the fixes-8/9 reviews' runners; and the injected-`ProtocolViolation` class is `test_protocol_violation_refusal_shape`. The re-drive drives the documented heads as subprocesses against a real frozen repository — the same shape the suite's pins build (`_run_cli` runs the documented interpreter and script; `_make_repo` creates the `git init`/`add`/`commit` repository) — measured live, not an unbuilt shape; the "document == durable fresh replay" check is the implementation's construction (the printed document is read from the durable store), pinned by the outcome checks. 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 is the fixes-9 review's clean block (nothing carried, FFR-4/`DIVERGENCES CLOSED: document amended (b68be80…)` closed at the fixes-9 closeout). F1 is fixed, not carried (FINDINGS, F1). Nothing came in, nothing is open, and nothing is carried forward.
