Release Notes 2026-09-04 (the register lap)
The second release of September 4: every "is this you?" reaches the actual claim door, the work register becomes the single numbered list of open work, and three plans are written for the month ahead.
TL;DR: Verified in production: the claim door now reaches every listing that offers it, the work register organizes all open work by owner and priority, and the claim drive, statement surface and September 22 hardware day each have a written plan.
Status as of 2026-09-04: see body.
Relations
Verified in production on 2026-09-04 at 10:34 UTC (ten commits; UAT 11 of 11 smoke checks, then promoted and verified live, with negative controls answering 404).
Every "is this you?" now reaches the actual claim door
Four listing surfaces offered a person control over their own entry, and not one of them reached the page that offers it. Three linked to a generic contact page that reads no intent, and one to an anchor. Meanwhile the real claim door, with the form, the free-and-forever promise, the 72-hour removal SLA and the published count of removals honoured, sat unlinked from the listings it exists for.
Every listing now links to it, carrying the listing's own name and record, so the form opens already filled in rather than asking somebody to retype what we are showing them. A guard test asserts the link target across all four surfaces, because this was the same shape as a defect we have had before: each half worked, nothing tested the join, and the promise was the part that broke.
The work register
All open work is now one numbered list, organized by who it waits on, published in the repository and updated as part of every release. Founder decisions, external waits, and the engineering queue each carry stable identifiers, so work can be tracked by number rather than by memory.
Three plans for the month
The claim drive to the first hundred claimed listings, shaped by the rule that we never solicit off the data we hold. The statement surface, a bank statement over the consent receipts rather than a log viewer, whose shipping test is whether a reader can answer "did anything happen this month I did not expect?" in thirty seconds. And the September 22 runbook for Apple hardware day, which separates the part-number flip from the start of measurement so neither blocks the other.
A correction we published on ourselves
An earlier note in this session reported a ninety-minute build hang. That was a misreading: the build had queued for forty-one minutes and then run for fifty-five, and it succeeded. A change made on that false premise was withdrawn, and the real measurement is now recorded where the next reader will find it.