| Comment: | merge wiki-read: the wiki made readable |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
200d8889cf157f62e5fa4376a0a0b25a |
| User & Date: | dmestas on 2026-08-23 00:34:54.672 |
| Other Links: | manifest | tags |
|
2026-08-23
| ||
| 00:42 |
file: link the check-in a symbolic version resolved to
/file/trunk/... printed "trunk" as a check-in link, which 404s. The ref now goes to zit for resolution — never the index's branch table, which answers with a branch literally named trunk and is a stale lie on any repository that renamed its default (tk). Only a symbolic ref pays for the lookup. closed check-in: d62d6dfbfb user: dmestas tags: file-version | |
| 00:41 |
timeline nodes take the mark's shape; a leaf stops claiming a line above it
Node measured in the rail's own weight — line, ring gap and centre dot all 2.5 — so it reads as the logo instead of a squashed version. The upward line on tips was mine: hadAbove read a rail alloc had just pointed at this commit, so every tip drew a line to nothing. check-in: f312b5951d user: dmestas tags: trunk | |
| 00:34 | merge wiki-read: the wiki made readable check-in: 200d8889cf user: dmestas tags: trunk | |
| 00:34 |
wiki: track the contents-highlight asset
go:embed reads from disk, so the build was green locally while the file was untracked — a fresh checkout would have failed to compile. closed check-in: 5d5aa3902e user: dmestas tags: wiki-read | |
| 00:28 |
timeline: branch colours cannot collide on a page
The hue was a raw hash mod 360, so two names could land a few degrees apart — ticket-list and fossil-caps rendered as one magenta. Hues now come from nine slots at least 30 degrees apart, with the mainline's blue and the accent's orange left out; a branch keeps its hashed slot unless another branch in view wants it, and assignment is by name so it never depends on commit order. check-in: a754d20b3c user: dmestas tags: trunk | |