Build ErsatzTV Image / CI toolchain image resolves (pull_request) Successful in 13s
Build ErsatzTV Image / Delimiter ban (release path) (pull_request) Successful in 22s
PR Gates / CI image pin matches docker/ci (pull_request) Successful in 15s
PR Gates / Docs update reminder (pull_request) Successful in 19s
PR Gates / decisions lifecycle (pull_request) Successful in 16s
PR Gates / Fix proofs (Proves trailers) (pull_request) Successful in 16s
review-verdict/h10 Awaiting review verdict for c1007d6
Review verdict / Set review-verdict status (pull_request_target) Successful in 21s
Build ErsatzTV Image / Build & test (.NET) (pull_request) Successful in 9m24s
PR Gates / Script lint and tests (ruff + pytest) (pull_request) Successful in 9m6s
Build ErsatzTV Image / EF migration integrity (SQLite + MySql) (pull_request) Successful in 6m28s
Build ErsatzTV Image / Build & push image (amd64) (pull_request) Skipped
Build ErsatzTV Image / Functional E2E (curl + UI contracts) (pull_request) Successful in 5m59s
Build ErsatzTV Image / API docs in sync (OpenAPI + endpoint index) (pull_request) Successful in 8s
Build ErsatzTV Image / Formatting (changed .cs conform to .editorconfig) (pull_request) Successful in 5s
Sixth cold review, scoped to round 7 and the rebase. It verified the rebase resolution independently (counting the guard-inventory table by hand rather than trusting the machine check), confirmed every one of round 7's re-measured claims true, found the tail sentinel sound, and ran the suite green at 1218. Two Lows, both real. THE FOLD JOINED WITH A SPACE. Round 7 folded backslash continuations before scanning, to close a `jq \` + `-e` split. It appended a space where bash appends nothing — and that is not cosmetic. `jq -\` + `e '.'` is `jq -e '.'` to the shell and `jq - e '.'` to a space-joining fold: two tokens, no flag, detector silent. Fixed by joining with nothing, which is a simplification toward real shell semantics rather than another layer of cleverness. BUT THE REVIEW'S THREE DEMONSTRATIONS WERE MIS-SPECIFIED, and checking that is what produced the useful part. All three used an INDENTED continuation, and bash does not strip the continuation line's leading whitespace: `echo -\` followed by an indented `e X` prints `- e X` — the token does not re-form — and `jq -\` + indented `e` exits 3, not as `-e`. Measured directly rather than argued. So those three were not evasions; the guard was right to stay silent on them. The reachable shape is a continuation whose NEXT LINE BEGINS AT COLUMN 0, and in this file that is ordinary rather than exotic: YAML strips the `run:` block's common indentation (10 spaces), so any line written at the block's base indent executes at column 0. My first attempt to construct it put the line at column 0 IN THE FILE, which simply broke the YAML — the mutant did not parse, which is not a measurement. The correct mutant parses, passes `bash -n`, forms a live `jq -e`, goes GREEN under the space-joining fold and RED under this one. So the review's conclusion was right and its mechanism was not, and the fold is now documented by the shape that actually reaches it. The fold is extracted to `_fold_continuations` and carries its own cases, including the indented split that must NOT be joined into a flag — the false-positive direction matters here too, since inventing a token bash never forms would redden the guard on innocent code. Also: "four spellings" appeared a second time in the test docstring, 55 lines below where round 7 corrected it (v1 catches `jq -er`; it missed three). That is the fourth time in this branch a retraction has stood at an adjacent site after being fixed at the first — the pattern being that correcting the sentence is not the same as sweeping the claim. Verification: 1223 passed, 2 skipped; ruff clean; decisions-validate OK; YAML + `bash -n` clean. M22 (revert the fold to space-joining) lets the reachable evasion through, so the separator is load-bearing and proved so.