Artifact d55c02ac24c8f3ba0a76c3d6e427c7942289e62a68ceef12e94ccf2516f3ef03:
- File
internal/api/register.go
-
2026-08-26 12:56:35
— part of check-in
[1305bb9374]
on branch landings-batch
— A landing's CI verdict: the branch tip's tag, nothing new minted
The ticket asked to decide the shape — forum reply or tag — before wiring the display. Neither is needed: a verdict is already a tag on a check-in, quarry already folds and reads them, and a landing proposes a branch whose tip is a check-in.
Better on its own terms too. The verdict stays attached to what was actually tested rather than to a discussion record, keeps the zit#127 invariant with no new vocabulary, and a retargeted or reopened landing inherits the right answer without anyone copying it across.
Read at render, never stored, so it cannot go stale against the branch it describes. No run leaves it empty, which reads as 'nothing has run' rather than as bad news. (user: dmestas, size: 269565) [annotate] [blame] [check-ins using]
- 2026-08-26 12:58:43 — part of check-in [db0ed60824] on branch trunk — Accepted. Ordering by the DAG, one current landing per branch, and a verdict that was already an artifact. (user: dmestas, size: 269565) [annotate] [blame] [check-ins using]
-
2026-08-26 12:56:35
— part of check-in
[1305bb9374]
on branch landings-batch
— A landing's CI verdict: the branch tip's tag, nothing new minted