Build ErsatzTV Image / CI toolchain image resolves (pull_request) Successful in 7s
Build ErsatzTV Image / Delimiter ban (release path) (pull_request) Successful in 24s
PR Gates / CI image pin matches docker/ci (pull_request) Failing after 10s
PR Gates / Docs update reminder (pull_request) Successful in 20s
PR Gates / Fix proofs (Proves trailers) (pull_request) Successful in 11s
PR Gates / decisions lifecycle (pull_request) Successful in 24s
Review verdict / Set review-verdict status (pull_request_target) Successful in 9s
review-verdict/h10 Review-verdict: MERGEABLE @ 548e058 (base: main)
PR Gates / Script lint and tests (ruff + pytest) (pull_request) Successful in 5m46s
Build ErsatzTV Image / Build & test (.NET) (pull_request) Successful in 9m4s
Build ErsatzTV Image / EF migration integrity (SQLite + MySql) (pull_request) Successful in 6m11s
Build ErsatzTV Image / Build & push image (amd64) (pull_request) Skipped
Build ErsatzTV Image / Functional E2E (curl + UI contracts) (pull_request) Successful in 6m1s
Build ErsatzTV Image / API docs in sync (OpenAPI + endpoint index) (pull_request) Successful in 9s
Build ErsatzTV Image / Formatting (changed .cs conform to .editorconfig) (pull_request) Successful in 6s
The last item from the review, taken rather than deferred: it was graded non-blocking (generically true, and wrong in the CONSERVATIVE direction — it overstates a credential's capability, so nobody is told something is safe that isn't), but it is the same body-vs-`rule:` split as rounds 4 and 5, in the record this PR is centred on, and it is one clause in a file already open. `ci.actions-credential-scoping`'s `rule:` said `actions/checkout` "persists a write-capable credential"; its body two paragraphs down, corrected in round 2, says that since #748 the one persisted credential is read-only by declaration. The rule now says the same, and the catalog carries it. Decisions-Edit: yes Refs: #748