| Comment: | Landed: a strata that looks like one thing, because it is one thing. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
ca52fa73e4152ead529f414754f1cf75 |
| User & Date: | ai-local on 2026-08-27 00:04:13.531 |
| Other Links: | manifest | tags |
|
2026-08-27
| ||
| 10:08 | Landed: retarget replies read by the fold. check-in: 02bc605852 user: dmestas tags: trunk | |
| 02:48 | landing: read zit#144 retarget replies (carried from in-flight work) closed check-in: f61dfbb349 user: dmestas tags: retarget-reply | |
| 02:35 | landing.land: land a strata up to a rung, bottom-up closed check-in: 2478ddbc2b user: dmestas tags: stack-1 | |
| 00:04 | Landed: a strata that looks like one thing, because it is one thing. check-in: ca52fa73e4 user: ai-local tags: trunk | |
| 00:03 |
Landings: a strata is one row, and a map on the record
The open queue folds a stack under its base: a strata mark, the segment count, the landable end named, and the rungs in a details element with 1/N badges — no script. Settled views stay flat; a settled segment has left its chain. The record page draws the map: every rung bottom-up, this one marked, the landable one named, a rejected base as a broken rung. Above the bottom the accept control is disabled and says the segment below lands first. Proved with a real zit: two stacked landings count one decision; the top rung's accept is refused; accepting the base retargets the next onto trunk and it becomes the landable end, still one decision. closed check-in: 02f6aadcad user: dmestas tags: strata-ui | |
| 00:02 |
markup: fossil wiki resolves mentions and refs, like markdown does
An artifact with no N card IS fossil wiki — fossil's default, and what anything writing through the zit CLI produces. fossilInline resolved this dialect's own [target] links, but @mentions, [[wiki]] refs and bare hash refs are dialect-independent and were reaching only markdown bodies, so 62 of quarry's own 90 forum posts lost every mention in them. The two passes run after sanitizing, as they do in Render: resolveRefs mints the identity mark and the policy would strip it. It parses HTML and skips a/code/pre, so the anchors fossilInline just built and every block are left alone — both asserted.check-in: b00045e163 user: dmestas tags: trunk | |