probe(756): DO NOT MERGE — does a failing continue-on-error step skip the if:-less guard? #766

Closed
timothy wants to merge 3 commits from probe756/coe-invariant into main
3 Commits
Author SHA1 Message Date
timothy 1d34a73ff0 probe(756): DO NOT MERGE - does a failing continue-on-error step skip the if:-less guard?
PR Gates / CI image pin matches docker/ci (pull_request) Successful in 16s
PR Gates / Docs update reminder (pull_request) Successful in 18s
PR Gates / decisions lifecycle (pull_request) Failing after 17s
review-verdict/h10 Awaiting review verdict for 1d34a73
Review verdict / Set review-verdict status (pull_request_target) Successful in 8s
PR Gates / Script tests (pytest) (pull_request) Successful in 2m7s
Build ErsatzTV Image / Build & test (.NET) (pull_request) Successful in 9m29s
Build ErsatzTV Image / EF migration integrity (SQLite + MySql) (pull_request) Successful in 6m51s
Build ErsatzTV Image / Build & push image (amd64) (pull_request) Skipped
Build ErsatzTV Image / Functional E2E (curl + UI contracts) (pull_request) Successful in 6m36s
Build ErsatzTV Image / API docs in sync (OpenAPI + endpoint index) (pull_request) Successful in 10s
Build ErsatzTV Image / Formatting (changed .cs conform to .editorconfig) (pull_request) Successful in 8s
2026-08-10 22:16:19 +02:00
timothy 7e769c1b1f docs(756): record the per-step marker contract and its build-lane measurement
Adds ci.required-job-step-execution-markers, updates
ci.workflow-run-body-no-expressions (whose rule: named #756 as the open
residual and whose scope paragraph was tracking REQUIRED contexts rather
than one file), and documents the guard in docs/ci-cd.md.

Decisions-Edit: yes
Refs #756
2026-08-10 22:08:29 +02:00
timothy 2c6b0a39de fix(756): per-step execution markers on docker-build.yml's two REQUIRED jobs
A run: body the runner declines to interpolate is DROPPED and the job still
concludes success (#751). In review-verdict.yml that is fail-CLOSED; in
docker-build.yml's `test` and `migrations` — the other two required contexts on
main — it is fail-OPEN: the required check goes green having done no work.

Every consequential run: step now records that it began, and a trailing guard
fails the job when the expected set is incomplete. Per STEP, not per job as
proposed: a job-start marker only proves step 1 ran, and the dangerous drop is
`Test` or the migration replay.

Refs #756
2026-08-10 22:02:54 +02:00