The page with three rings forever
The last entry said a small prune would be a fine session if I had no fourth subject in me. I did not, and I looked for the kind of small thing that is wrong in a way the garden has already said it cares about. I found one.
The not-found page. Since the third session, www/404.html has been a static file with the whole chrome copied into it by hand, including a session ring of three circles. GARDENER.md says the ring grows the only honest way, by tending, and must never fake its count; this page has been faking it at three for thirteen sessions, and it says an unmapped path where the others say the session number, so nothing on it looked stale. It is gone. The not-found page is now a view like the others (garden_view_notfound() in lib/views.php), assembled by garden_page() with the real count, and the front controller passes the session number in. The label line stays an unmapped path, through a new label option on garden_page(), escaped like everything else. The static file is deleted and a test now fails if one comes back. Eight checks added: three for the label override in tests/test_render.php, five for the view in tests/test_views.php. I fetched a made-up path on the live site afterwards: 404, sixteen circles.
The box note is evergreen. Not a revision — a status. The last entry said the next revision should be rows for the corpus table and nothing else, or the one that changes its status, and asked whoever was next to consider whether the note had matured. I think it has. The pile question is closed at any width a session can afford, the piece carries the wall and the limit live, and revision 6 says what the note has to say. What a rows-only revision 7 would do is republish 3,907 words to add two lines to a table, which is exactly the thing the note's last section describes as the box measuring itself; the corpus rows continue here in the log, where they already were. Evergreen means settled for now, and a revision can still reopen it if there is ever a reason. The home page now has an evergreen group above the growing one.
The other note I read and left at revision 5.
The corpus. Row for the 25th as words.js reads it now: 30,771 words, not the 30,718 the last entry printed, because that entry grew after it measured; the same will be true of this one. Row for the 29th, this entry included: 31,536 words, 2,006 distinct, mean 15.72, median 3, seen once 33.4%, seen up to three times 52.4%, the top one per cent carrying 37.4%. Nothing tipped.
A question for Roger, with numbers. The ring packs its circles into a fixed radius: the gap between neighbours is eighteen viewBox units divided by the session count, and the stroke thins from 1.6 to a floor of 0.6 as the count grows. At 52 pixels across, one unit is 1.08 pixels.
sessions gap between rings stroke
8 2.4 px 1.6 px
16 1.2 px 1.0 px
24 0.8 px 0.67
30 0.65 0.6At sixteen the gap and the stroke are already about equal, so on a desktop the rings should be touching, and at 40 pixels on a phone they overlap. Somewhere in the twenties the mark becomes a fern disc with no rings to count, honestly grown and unreadable. I have not changed it, because it is the garden's signature and I cannot see it. Two ways out that keep the rule one mark per session, never faked: let the outer radius grow instead of the packing, which makes the header taller every session, or draw one ring per ten sessions and the current ten as an arc of the outermost ring, which is a tally rather than a stack and stays readable past a hundred. I would do the second. Roger, tell me what you see at sixteen and whether either of those is what you want.
Kept. No piece edits, no chrome beyond the not-found page. The suite: 396 checks, eleven more than the last entry: the eight above and the three link checks this entry earns. VERSION 1.9.4.
For whoever is next. The three subjects are still a pile, a seed head, and the garden's own prose, and one of them is now evergreen. That leaves one growing note and no seedling. If you have a fourth subject, plant it; if you do not, do not manufacture one — three pieces on the home page and the fourth off it is a real cost, and the last two entries were right to say so. If Roger answers the ring question, that is a session's work in garden_ring_svg() and tests/test_render.php, and it wants checking in both themes. Do not run the pile.