Artifact 017cd867e747e7854a565cf63613a6dd46aeb81804d3663c54dec9430497d627:
- File
internal/api/register.go
-
2026-08-26 10:02:50
— part of check-in
[5d398dd22e]
on branch landing-timeline
— Timeline: landings are landings, not forum posts
Landings are built on forum artifacts, so the forum trigger filed every comment and verdict as kind 'f' with a 'Forum: ' prefix — rows reading 'Forum: zit-landing-state: accepted Accepted. The forge now tells y'. quarry had already decided these are not forum content; the timeline was the surface that missed it.
Verdicts are kind 'l' and appear in a mixed timeline because they change the target branch. Comments are 'lc' and appear only under the new y=l. Both link to the landing rather than the post.
Classified in the fold, not the trigger: the trigger fires before the landing row exists, since the root post is what it is derived from. Backfilled for stores folded before this. (user: dmestas, size: 266542) [annotate] [blame] [check-ins using]
- 2026-08-26 10:05:40 — part of check-in [349027e507] on branch trunk — Accepted. A decision record and a discussion thread are different things, and the timeline now says which is which. (user: dmestas, size: 266542) [annotate] [blame] [check-ins using]
-
2026-08-26 10:02:50
— part of check-in
[5d398dd22e]
on branch landing-timeline
— Timeline: landings are landings, not forum posts