- 24 An entry written in one command, prose on stdin Writing an entry was two steps: cairns new made a stub, then the prose went into it by editing the file.
- 23 Areas in one line each and files that fold Two complaints from use, both about friction rather than correctness: adding an area was a chore, and an entry with fifteen files put a wall of paths between its title and its first sentence.
- 22 A config section the binary had never heard of [[link]] from [[21]] worked here and did nothing on someone else's machine, with no error either way.
- 21 Links the generated nav could never know about The rail's navigation was whatever cairns had made: entries, the reference, the open questions, the About page, the feed.
- 20 One plus-minus sign crashed the scanner thread 'main' panicked at crates/cairns-core/src/entry.rs:490:32: start byte index 1 is not a char boundary; it is inside '±' (bytes 0..2 of string).
- 19 References, and a parser that reads them in pieces An entry could point at another only by writing out its filename:.
- 18 The tap is the repo A Homebrew tap does not need a repository of its own.
- 17 An entry that says nothing about what it does not know Hellbender's entry 60 asks whether check should refuse an entry with no **Still unknown:** line at all, rather than accepting a log that quietly stops collecting.
- 16 A field carried all the way through and shown nowhere files is in the spec as "paths the entry is about".
- 15 Two install instructions that were not true The README said:.
- 14 Hellbender's own docs tree crashed the renderer Enabling cairns on hellbender - the repo the format came from - took a cairns.toml and one init, which froze thirteen slugs and left the hand-written skill alone because it carries no marker.
- 13 Working blind, and the render loop I should have had first Four rounds of "still cramped", "so fucking tacky", "the page is too thin", before the accurate version of the complaint arrived: you're not even using a headless browser, you're throwing shit at a wall.
- 12 Three CSS edits, three wrong anchors, and half a stylesheet gone The layout work was a run of small fixes - one page width everywhere, a simpler entry list, one hover effect instead of three, a one-line footer, the contents list moved out of the flow.
- 11 The log's own links were dead on its own site The skill tells you to correct an earlier entry by linking to it:.
- 10 A question can be answered, not just a claim overturned Asked what happens when a later entry answers an earlier one's open question, and the answer was: nothing.
- 9 The viewer felt cheap, and the filters had never worked Three rounds of "still cramped" before the actual problem was named: it felt cheap.
- 8 Distribution, and a worklog a model can read Two things that both amount to the same question - who can get at this - and one correction to work done earlier in the day.
- 7 Migrate, and the backup that never fired migrate splits a single-file worklog on its ## headings, takes the number and title from each, demotes the sub-headings one level - the old format made the entry title an h2 and its sections h3, the new one makes the title the h1 - and writes one file per entry.
- 6 The log reads as a website, and the feed is not the whole log cairns build renders the payload: an entry page each with prev/next and clean URLs, an index with area chips and a search box, an open-questions page, an Atom feed, a search index, and the log.json all of it was built from.
- 5 The command was stricter than the format Asked whether an entry can sit in more than one area, the honest answer was yes - and then --area "decomp, engine" turned out to be rejected while --area decomp,engine worked.
- 4 The write path, and an init that nearly ate hellbender's skill new, init and the skill template close the write path.
- 3 The index generates, and hellbender's own index proves it cairns index regenerates WORKLOG.md, and rendering hellbender's 55 entries reproduces its committed index byte for byte apart from the documented area-spacing change.
- 2 What hellbender's own log said about the spec All 55 of hellbender's entries parse against the new strict front matter with no errors, and check found two real title-filename drifts the old tool could not see.
- 1 The format is the asset, so the spec is written down first The worklog format is extracted from hellbender as its own project, with the spec written before the tool so the format can outlive this implementation.