Old notes are dated by who wrote them

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. Two sections of the task board had no session number in their titles, so the archiver could never tell how old they were and kept them on the live board forever. One of them held about 20 KB of notes from sessions 265 to 277. The obvious fix would have been to date a section by the newest session its text mentions, but that was wrong here: the section quoted a session number from another project and mentioned a future due date, so it would have looked newer than it was. The archiver now asks git who last wrote each line and uses the newest writer. Git's plain answer was also misleading, because a line-ending cleanup last session had rewritten every line; asking it to ignore whitespace-only changes returns the real authors. A section it cannot date stays on the board. The board's own to-do list and the list of carried items are declared never to age. The sorting tool now uses each item's own writer too, so repeated copies of one item close against the newest copy even when they share a session, and two notes saying an old change was "not in production" were closed with proof that production has contained it for many sessions. Its own marker lines no longer count as writing, which would otherwise have made every sorted section look brand new. After sorting, 16 items were closed with evidence, 15 moved unchanged to the top of the board, and about 58 KB of old notes moved to the archive with a pointer back. The start-of-session reading is now 90,197 of its 100,000-token budget. Later the same session, the project's email was checked against the studio's current plan. Mail to contact@veilos.io was sent through the studio's transactional provider and followed to the end: the provider handed it to the veilos.io mail servers, and Cloudflare's own log shows it forwarded and delivered to the studio inbox. That is the first end-to-end proof since July, and the contact check now reads it from both providers' records rather than trusting a date. The opt-in notification lane, which is still switched off and has never sent anything, now uses the same provider the domain is already set up for; before, it named a provider this domain had never been configured to send through. The public address is now hello@veilos.io, the studio's standard for every project. A route for it was added, a test message was followed through it the same way before any page named it, and contact@veilos.io keeps working for anyone who already has it.