| Comment: | index: fold landing records into a queryable surface
A landing (zit#127) is a reading of forum_post, not a new artifact kind, so the table is derived and recomputed whenever any post in its thread folds -- which is what makes a reply indexed before its root converge on the same row. Backfilled once at open for indexes whose posts predate the table. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
3c6bee847a9c9be354237117cbc3ffe6 |
| User & Date: | dmestas on 2026-08-23 13:42:55.095 |
| Other Links: | manifest | tags |
|
2026-08-23
| ||
| 19:17 |
landings: the decision surface
A list of what awaits a decision and a page per record: proposal, diff against target computed at view time, discussion, and the controls. accept rides `i` because it merges; everything else is a forum cap. Transitions render as events — zit stores them as replies, which is encoding the interface exists to hide. check-in: 7d2a820f65 user: dmestas tags: trunk | |
| 13:50 | merge struct-links: wanted and unlinked reachable from the filter row check-in: c9c04092a9 user: dmestas tags: trunk | |
| 13:42 |
index: fold landing records into a queryable surface
A landing (zit#127) is a reading of forum_post, not a new artifact kind, so the table is derived and recomputed whenever any post in its thread folds -- which is what makes a reply indexed before its root converge on the same row. Backfilled once at open for indexes whose posts predate the table. check-in: 3c6bee847a user: dmestas tags: trunk | |
| 12:31 |
timeline: the mainline claims rail 0 only when it is free
A merge whose two parents are both on trunk puts two chains in front of one column. Claiming rail 0 anyway stopped drawing the line that was already travelling there — the gap — and overwrote the commit it was heading to. Test asserts every head resumes its predecessor's tail. check-in: 6f34d948a0 user: dmestas tags: trunk | |