- Shipped
- September 7, 2026 at 10:23 PM UTC
- Author
- Kamo
- Commit
- 9b9205f
THE CLAIM ROUTE DID NOT EXIST. The Java endpoint has accepted CLIENT claims since the catalogue's first ones shipped, but nothing in Next forwarded to it and nothing in the browser called it — so all six existing CLIENT achievements, TOP_CORNER included, were declared, rendered as locked cards and unearnable. That route is the first file here, and TOP_CORNER now claims from the goal it was always about. ONE OBSERVER PER CONCERN, NOT ONE CLAIM PER PAGE. Nine of the eggs are about where a member has been, six about the dock, three about who else is online. Each set is a single component that renders nothing, owns no element and reads no state anybody else can see — so the layout engine, which is load-bearing for the standing rule that a tool window never loses state, gains no achievement code at all. The remaining twenty-one are one import and one line at the place the thing actually happens. FIRE AND FORGET, DELIBERATELY. Nothing waits on a claim, branches on one, or shows an error for one. A member who has just found a secret is in the middle of doing something else. The local ledger is an optimisation against re-POSTing from scroll and route handlers, never a source of truth: clearing it costs one redundant round trip. Four eggs are narrower than they were specified, and each says so in its own doc rather than quietly reading as the thing it is not. Full-text search over document CONTENT does not exist in the manager, presence does not carry a route or a department, and chat heads bounce off the ceiling rather than leaving through it. ON_THE_SCENT is the biggest of these: it was meant to pay a member for TELLING a colleague, which needs an organization-wide "somebody found something" broadcast that does not exist and should not be invented quietly for a ten-point badge.