Files
ersatztv/scripts/tests
timothyandClaude Opus 5 21a3e5992a fix(869,893): re-establish the 1.25.4-dated CI claims on 1.27.1, and settle the page_statuses asymmetry from source
Finishes the claim sweep #747 deliberately left incomplete, and answers #893's
open question by reading the v1.27.1 source rather than inferring from a header.

Population derived with `git ls-files`, not from #869's item list: 17 files and
43 occurrences of `1.25.4`, materially wider than the four items the issue named.

Re-established on 1.27.1 (all previously 1.25.4-dated):

- creator attribution (the load-bearing one, since the H10 allow-list rests on
  it): four merged PR heads, exactly one `.creator.login` row per head and every
  other row `creator: null`, on BOTH the combined and list endpoints. The
  mechanism is in the serializer, so the two endpoints cannot disagree.
- scope enum: no `status` scope at v1.27.1; nine categories, zero occurrences.
- the `reqRepoWriter(unit.TypeCode)` gate on `POST /statuses/{sha}`: unchanged.
- the `write:package` 403: re-probed live with a read control (200) and a write
  control (201), in a throwaway repo, both artifacts deleted and confirmed gone.
- the cancel route: absence confirmed in the v1.27.1 router rather than resting
  on an observed 404, which cannot distinguish absence from a refusal.
- `pull_request` vs `pull_request_target` definition resolution: read off
  `notifier_helper.go`, which is stronger than the four 1.25.4 scratch PRs.

Corrected rather than re-dated:

- the `--depth=1` no-merge-base claim was filed against the wrong axis. It is a
  GIT property; a Gitea upgrade cannot change it. Re-probed on git 2.55.0.
- `enable_bypass_allowlist` postdating 1.25.4 was sourced from an issue body.
  Now checked in both trees. It holds; the neighbouring
  `block_admin_merge_override` does NOT share that history and is present at
  1.25.4 too, stated so the paragraph cannot invite the inference.

#893: `/statuses/{sha}` does NOT drop rows after pagination. `getCommitStatuses`
appends unconditionally and its only filter is a SQL WHERE evaluated in the same
query as the LIMIT/OFFSET, so an empty page really is the end. The asymmetry with
`count_pr_mutations` is therefore correct and is recorded with its reason. The
same two handlers also explain the per-endpoint terminator shapes (`[]` vs bare
`null`) that were previously an empirical table.

Claims that stay dated now carry a reason that was CHECKED this session rather
than inherited: all six workflow triggers re-enumerated, and the direct-push
half re-read live.

fixes #869
fixes #893

Decisions-Edit: yes
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Whe75djeAEuZpdNk6KU7No
2026-09-02 19:41:30 +02:00
..