probe(751): POSITIVE — does the fixed classify step execute? #752

2026-08-06T20:26:59+02:00

timothy commented

2026-08-06 20:26:59 +02:00

Throwaway probe for ersatztv#751. Base carries the #751 fix, a probe-named context (probe751/h10, never the real one — a status forged on a scratch head is inherited by any later PR with the same head sha, #663) and a self-admitting branches: filter. EXPECT: the classify step runs, and this docs-only head is granted the docs-only exemption. Closed and deleted after reading the log.

Throwaway probe for ersatztv#751. Base carries the #751 fix, a probe-named context (`probe751/h10`, never the real one — a status forged on a scratch head is inherited by any later PR with the same head sha, #663) and a self-admitting `branches:` filter. EXPECT: the classify step runs, and this docs-only head is granted the docs-only exemption. Closed and deleted after reading the log.

timothy referenced this issue from a commit

2026-08-06 20:53:24 +02:00

fix(751): the fence never trusted its count — a page past the end is `null`, not `[]`

timothy force-pushed probe751/head-pos from 16516b52db to f47b5d2407

2026-08-06 20:53:25 +02:00

Compare

timothy referenced this pull request

2026-08-06 20:56:09 +02:00

review-verdict.yml's classify/post step never executes — job goes green, review-verdict/h10 is never posted automatically #751

timothy force-pushed probe751/head-pos from f47b5d2407 to 3108200da3

2026-08-06 21:36:25 +02:00

Compare

timothy force-pushed probe751/head-pos from 3108200da3 to c0b526b204

2026-08-06 22:16:04 +02:00

Compare

timothy force-pushed probe751/head-pos from c0b526b204 to 17c73e3485

2026-08-10 18:54:41 +02:00

Compare

timothy referenced this issue from a commit

2026-08-10 19:43:17 +02:00

fix(751): the fence never trusted its count — a page past the end is `null`, not `[]`

timothy added 1 commit 2026-08-10 19:43:21 +02:00

probe(751): round-6 head (pos)

PR Gates / CI image pin matches docker/ci (pull_request) Successful in 14s

Details

PR Gates / decisions lifecycle (pull_request) Successful in 15s

Details

PR Gates / Docs update reminder (pull_request) Successful in 12s

Details

probe751/h10 Exempt: docs-only change (no code, no protected path)

Details

Review verdict / Set review-verdict status (pull_request_target) Successful in 17s

Details

Build ErsatzTV Image / Build & test (.NET) (pull_request) Successful in 12s

Details

Build ErsatzTV Image / EF migration integrity (SQLite + MySql) (pull_request) Successful in 10s

Details

Build ErsatzTV Image / Build & push image (amd64) (pull_request) Skipped

Details

Build ErsatzTV Image / Functional E2E (curl + UI contracts) (pull_request) Successful in 10s

Details

Build ErsatzTV Image / API docs in sync (OpenAPI + endpoint index) (pull_request) Successful in 10s

Details

Build ErsatzTV Image / Formatting (changed .cs conform to .editorconfig) (pull_request) Successful in 8s

Details

PR Gates / Script tests (pytest) (pull_request) Failing after 2m1s

Details

6bae7d651b

timothy force-pushed probe751/head-pos from 17c73e3485 to 6bae7d651b

2026-08-10 19:43:21 +02:00

Compare

timothy referenced this pull request

2026-08-10 21:09:35 +02:00

fix(751): a stray expression delimiter in a COMMENT killed the verdict gate — plus the two nil-slice twins and a dead-code guard it hid #764

timothy commented

2026-08-10 21:10:12 +02:00

Probe complete — closing. Final evidence is recorded on #751 and in PR #764.

This pair verified the #751 fix on the live instance across six rounds, the last against e133c11fd, whose executable content is byte-identical to the merged head (only comments changed after it). Positive: the classify step runs, the fence reports trusted=yes, and the docs-only exemption is posted. Negative control: the defect reintroduced, the step dropped, and the new guard fails the job with the probe context absent — which is what established that a later step still runs after the runner drops an earlier one, the premise the guard stands on.

The probe context was probe751/h10 throughout, never the real one: a status forged on a scratch head is inherited by any later PR carrying the same head sha (#663).

Probe complete — closing. Final evidence is recorded on #751 and in PR #764. This pair verified the #751 fix on the live instance across six rounds, the last against `e133c11fd`, whose executable content is byte-identical to the merged head (only comments changed after it). Positive: the classify step runs, the fence reports `trusted=yes`, and the docs-only exemption is posted. Negative control: the defect reintroduced, the step dropped, and the new guard fails the job with the probe context absent — which is what established that a later step still runs after the runner drops an earlier one, the premise the guard stands on. The probe context was `probe751/h10` throughout, never the real one: a status forged on a scratch head is inherited by any later PR carrying the same head sha (#663).

timothy closed this pull request

2026-08-10 21:10:13 +02:00

timothy referenced this issue from a commit

2026-08-28 18:25:36 +02:00

docs(747): bind each re-probe claim to the exact arm that produced it

Pull request closed

This pull request cannot be reopened because the branch was deleted.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: timothy/ersatztv#752