| Comment: | landings: prove the lifecycle end to end
open, comment, reject, accept through the forge against a real store — accept merges to trunk via zit#131's bare-store path. Also checks the record still reads as an ordinary forum thread. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
9a84a5d9627feb99a80f7c0e76347705 |
| User & Date: | dmestas on 2026-08-23 21:50:21.752 |
| Other Links: | manifest | tags |
|
2026-08-23
| ||
| 22:01 |
landings: a way to open one, and the lifecycle written down
docs/landings.md covers the whole loop and says plainly that a landing is a forum thread plus branch tags. Writing it found the gap: there was no create control at all. A mirror offers its upstream instead. check-in: c6aa693938 user: dmestas tags: trunk | |
| 21:50 |
landings: prove the lifecycle end to end
open, comment, reject, accept through the forge against a real store — accept merges to trunk via zit#131's bare-store path. Also checks the record still reads as an ordinary forum thread. check-in: 9a84a5d962 user: dmestas tags: trunk | |
| 21:43 |
landings: memoise the mergeability probe on the tip pair
The probe is a full-store scan by design and measures 2.0s here, paid on every view. Keyed on the two check-ins, so a push invalidates it by making a different key rather than by anyone clearing a cache. 1.9s cold, 50ms warm. check-in: 21d510a5bd user: dmestas tags: trunk | |