Files
ersatztv/scripts
timothyandClaude Opus 5 66d62a2f58 docs(747): scope every re-probe claim to the configuration actually measured
Round 1 of independent review returned 21 findings. Nearly all were one mechanism:
a conclusion stated more broadly than the single configuration it rested on. Fixed
as a class rather than site by site.

Corrections of fact:
  * ci-image.yml's push trigger is `main` + `docker/ci/**` with deliberately NO
    `tags:` key - it was described as "main plus v* tags", which conflated it with
    docker-build.yml and contradicted ci.toolchain-image-publish-is-a-dispatch
  * push-supersession is not "no longer observable": a PR merge IS a push to main,
    so two merges landing close together still produce it. What is gone is the
    ability to reproduce it ON DEMAND
  * the scope-enum and reqRepoWriter items were established by reading Gitea source
    at the version tag, not by a scoped PAT - only the write:package 403 needs one.
    The invented reason contradicted that record's own Measured-vs-inferred block

Self-contradiction removed: "the gate does not fail open on absence" was stated
unqualified three lines below ARM A, which showed an absent context force-merging
with block_admin_merge_override:false. Now two claims - absence blocks an ORDINARY
merge; only the override field blocks a FORCED one.

Overclaims scoped to their evidence:
  * the 200-PR file-status pass is a large recency-biased SAMPLE, not a constructed
    case; `copied`/`modified` not appearing does not show they are never emitted.
    The prior pass that saw only changed/added was 30 PRs, not 2
  * the cancel-route re-probe covered the REST route and swagger only; the MCP
    cancel_run and web-UI/CSRF findings stay 1.25.4-dated. DELETE /actions/runs/{run}
    was read from swagger, not probed - no claim that it frees a runner slot
  * bypass-allowlist result holds for ONE configuration (empty list, override false);
    a non-empty list was untested, and it cannot distinguish "does not govern admins"
    from "empty list treated as unconfigured"
  * branches:[main] re-confirmed at the STATUS level; the run list was not enumerated
  * `skipped` sampled on two heads (#829, #828), not "every PR head"

Causal claims dropped where only an observation was made: `mergeable` reflecting
conflict-freedom, and the vocabulary delta being caused by sampling rather than by
the version change.

The push-supersession finding is mirrored into ci.verdict-write-retarget-fence, the
record that owns the claim, so a catalog reader does not re-open it next sweep.

Partially declined with evidence: the ~100-col rewrap. The baseline already carries
406/2486 such lines in ci-cd.md and 25/79 in main-direct-push-disabled, so the
premise does not hold; the one genuine outlier (a 432-col insertion) is wrapped.

Refs: #747
Decisions-Edit: yes
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-28 17:23:59 +02:00
..
2024-01-15 10:29:07 -06:00
2024-01-16 13:28:46 -06:00