docs(747): re-probe the Gitea CI claims on 1.27.1, and measure the two that were source-attested only

The instance moved 1.25.4 -> 1.27.1 during #743, which left a set of deliberately
version-pinned CI claims dated rather than wrong. The population was re-derived from
`git ls-files` instead of from the issue's own 9-key list, which found ~21 claim sites
across workflows, scripts, tests, docs and records.

Re-confirmed unchanged on 1.27.1:
  * an `if:`-skipped job still reports commit-status `skipped`, a distinct state
  * `compare/{base}...{head}` still serves no `files`
  * no agent-side cancel route (POST 404, and live swagger has no cancel path at all)
  * `review-verdict.yml`'s `branches: [main]` still suppresses the run off a non-main base

Re-derived from a constructed corpus rather than a sample, because two arbitrary PRs
showed only two of the values: the PR file-status vocabulary is changed/added/renamed/
deleted over 200 PRs. All four were already in the closed allow-list, so that set is now
evidenced rather than partly presumed.

Newly measured, replacing source-attestation. All three arms ran on throwaway
scratch-base protection rules, so `main`'s rule was never touched (its updated_at is
unchanged at 2026-08-05):
  * `block_admin_merge_override: false` lets an admin force_merge past an ABSENT
    required context (HTTP 200); flipping only that field to `true` refuses the
    identical call (HTTP 405) - the negative control that makes it attributable
  * an absent required context BLOCKS, so the merge gate does not fail open when
    review-verdict.yml never runs
  * `enable_bypass_allowlist` is NOT a better-targeted substitute: enabled with an
    empty username list, the admin force_merge still succeeded
  * trap: the PR API reports `mergeable: true` while that same merge is refused,
    because the field reflects conflict-freedom and ignores branch protection

Left explicitly dated rather than silently refreshed, each with its reason:
push-supersession auto-cancel is no longer observable on this repo (no workflow
triggers on a non-main push, and main refuses direct pushes), and the scope-enum /
reqRepoWriter / write:package-403 items need a scoped PAT rather than a read-only probe.

review-verdict.yml carries three more 1.25.4-dated comments and is deliberately
untouched here: #763 is in-progress on that file and its paging work overlaps them.

Refs: #747
Decisions-Edit: yes
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-08-28 17:14:40 +02:00
co-authored by Claude Opus 5
parent b16ec15d6c
commit 566a320cf2
13 changed files with 87 additions and 26 deletions
+2 -1
View File
@@ -13,7 +13,8 @@
# Why this is the merge-gate-safe half of #416: the two REQUIRED contexts (`Build & test (.NET)`,
# `EF migration integrity (SQLite + MySql)`) are gated by SKIPPING STEPS inside a job that always
# runs and always reports `success` — never by an `if:`-skipped job. On Gitea 1.25.4 an
# `if:`-skipped job reports commit-status state `skipped` (verified, PR #418), and how branch
# `if:`-skipped job reports commit-status state `skipped` (verified, PR #418; re-confirmed on
# 1.27.1, 2026-08-28, ersatztv#747), and how branch
# protection treats a `skipped` REQUIRED context is not something we rely on. Non-required jobs may
# skip freely (production already proves a `skipped` non-required context — e.g. `build` on every
# PR — does not block merge).
+6 -2
View File
@@ -41,7 +41,8 @@
# This NARROWS the window, it does not erase it. The base is re-read after the paging round trips
# alongside the head, so a retarget that is still in effect at that point fails closed; a retarget
# that opens and closes strictly between the files call and the re-read is not observable from here.
# Pinning the diff to two shas would close it, and Gitea 1.25.4 cannot serve that: `compare/{base}...
# Pinning the diff to two shas would close it, and Gitea cannot serve that (measured on 1.25.4,
# re-confirmed on 1.27.1 2026-08-28 ersatztv#747): `compare/{base}...
# {head}` returns `total_commits`/`commits` and NO `files`, and a `--depth=1` fetch of the two shas
# has no merge base, so a three-dot diff is impossible while a two-dot one over-reports every commit
# `main` gained since the branch point (both measured, #698). The remainder is covered one level up
@@ -190,7 +191,10 @@ while [ "$page" -le "$MAX_PAGES" ]; do
# "renamed rows MUST carry previous_filename" requirement entirely. (An earlier version of this
# comment claimed the source path would be "dropped", which is not the mechanism; a maintainer
# who tested that claim would find it false and might conclude the check is redundant.)
# `modified` is accepted alongside `changed` deliberately: live Gitea 1.25.4 emits `changed`, but a
# `modified` is accepted alongside `changed` deliberately. Live Gitea emits `changed`; the full
# emitted vocabulary was re-derived on 1.27.1 (2026-08-28, ersatztv#747) over the file rows of the
# 200 most recently updated PRs — exactly `changed`, `added`, `renamed`, `deleted`, all four already
# in the list below. `modified` is retained because a
# closed allow-list built from the wrong vocabulary is a worse failure than the hole it closes — it
# would gate every genuine docs-only PR on any version that spells it differently. The property is
# "reject values we do not recognise", not "enumerate one version exactly".
@@ -476,9 +476,11 @@ def test_a_rename_disguised_by_an_unknown_status_is_rejected(hook, status):
def test_gitea_real_status_values_are_accepted(hook):
"""Positive control for the closed set. The real Gitea 1.25.4 value for an edit is `changed`,
NOT `modified` — a closed allow-list built from the wrong vocabulary would reject every real
docs-only PR, which is a far worse failure than the hole it closes."""
"""Positive control for the closed set. The real Gitea value for an edit is `changed`, NOT
`modified` — a closed allow-list built from the wrong vocabulary would reject every real
docs-only PR, which is a far worse failure than the hole it closes. Measured on 1.25.4 and
re-derived on 1.27.1 (2026-08-28, ersatztv#747) across a 200-PR corpus, which emits exactly
`changed`, `added`, `renamed`, `deleted`."""
hook.set_pages(
[
{"filename": "docs/a.md", "status": "changed"},