Files
ersatztv/docs/decisions/records
timothy 8d071d04ff fix(748): the same field's TAIL still said to wait for a Gitea upgrade
Round 5, and the last mirror the concept-sweep finds. Round 4 corrected the
middle of `ci.gate-trigger-base-resolved`'s `rule:` and left its tail, so one
YAML line said both "five hold `code: read` since #748, under today's permissive
default" and, ~600 characters later, "the injected token stays write-capable
until Gitea >=1.26 with a Restricted default".

Doubly stale. The version half was already wrong independently of #748: the
instance went 1.25.4 -> 1.27.1 on 2026-08-05, so ">=1.26" has been satisfied for
three weeks, and `ci.actions-credential-scoping` has said so since that date. A
reader of that tail was told to wait for an upgrade that had already happened.

Replaced with the framing the rest of the corpus now uses: the Restricted
default is a separate OPEN lever whose effect on a declared `code: write` is
unmeasured, and it is not something to wait on a Gitea release for. Catalog
regenerated; verified the stale clause is absent from both the record and
`docs/decisions/README.md`, and the corrected one present in both.

Lesson this PR keeps re-teaching, recorded because it cost five rounds: a
"sweep" that greps the wording I just corrected finds only what I already fixed.
Rounds 3, 4 and 5 each found the next instance one structural level out — body
prose, then the `rule:` field the catalog mirrors, then the far end of that same
field. Sweep by SUBJECT, and treat a long generated-from field as needing its
own read end to end rather than a match count.

Decisions-Edit: yes
Refs: #748
2026-08-27 21:28:45 +02:00
..