The start-of-session reading fits its budget again

Nothing about the site you visit changed in this release. Participant export and deletion stay unavailable, and the health page's storage warning is still deliberately visible. This note is about the project's own bookkeeping. The previous note ended on a block of history filed under one heading, "S320 and earlier", that the archiver could not split. The archiver dates a section by the newest session its heading names, so 57 sessions of notes were treated as if they were all from session 320 and would have stayed on the live board for another eleven sessions. The archiver now reads a heading like that as a folder: each session inside it is dated by its own heading, and the folder's title stays put. That made 85 more open items visible to the check that refuses to archive them. The same sorting tool handled them as before. Twenty-two were word-for-word repeats of a newer item and were closed pointing at it. The other 63 were moved unchanged to the top of the board. After that, 33 old sessions (145 KB) moved into the archive with a pointer back. Two other gaps turned up along the way. The reading check said the archiver could clear the budget while the archiver's next run would actually have moved nothing, so it now also reports what the next run will move. And the archiver's size rule knew nothing about the reading budget, so a file could stay just over it forever. When the reading is over budget, the archiver now moves the old sections of the files in it even below the size rule. The first run moved 18 KB of old state notes and brought the start-of-session reading to 96,477 of its 100,000-token budget. The sorting tool had also been stamping every future run with the session that wrote it, and its merge step created duplicate group headings on a file with Windows line endings; both are fixed and tested.