Commit Graph
3 Commits
Author SHA1 Message Date
Thore CimbalandClaude Opus 5 84e87238f6 fix(pruefungen): acknowledge the reworded wiki finding, record what the run taught
The first CI run after the acknowledgement list went in was still red, so the
"all three green" line in #0104 was premature and is corrected rather than left
standing.

Two things it showed. Disabling the wiki mirror changed the finding's wording from
"Mirror wiki: counterpart unreadable" to "wiki: no active push mirror", and since
acknowledgements match on substrings, the entry no longer applied. Added. That is
the cost of a list readable without special knowledge: fix or move a cause and the
acknowledgement has to follow, otherwise it goes red - correctly.

The second finding, management mirror divergence, is deliberately NOT acknowledged.
It appears on any run starting minutes after a push because the mirror lags, and
acknowledging it is tempting - but that same message is the only signal if a mirror
ever really stops (#0028). It stays sharp; a run right after a push is briefly red.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-18 12:00:00 +00:00
Thore CimbalandClaude Opus 5 9915b979a6 chore(issues): record #0104's mirror address
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-18 12:00:00 +00:00
Thore CimbalandClaude Opus 5 0c4cb05a0e docs(issues): #0104 - every scheduled check is permanently red
Decision sorb. AGENTS.md makes a red pipeline the alarm, with no second channel by
design. That only works while green is the normal state, and right now none of the
three scheduled checks reach it: canonize_rotation was red for nine days,
gruppenpruefung is red daily on 20 findings of which 17 are deliberately deferred,
and stillstandspruefung aborts daily for a missing GITEA_TOKEN. The management
pipeline has failed every day since at least 2026-08-12.

canonize_rotation is the proof rather than the anecdote: it failed for nine days on
a conflict touching both TURN secrets and the client image tag, and nobody noticed,
because one more red cross among red crosses is invisible. It surfaced only because
someone looked for an unrelated reason.

The issue asks how "known and deferred" gets distinguished from "new" without the
deferred work blocking the channel, and recommends acknowledging #0053's findings
with an expiry date while fixing #0031 outright. Acceptance requires showing a
freshly introduced finding still turns the pipeline red - demonstrated, not assumed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-18 12:00:00 +00:00