Changes touching this path
- ADR 0097 records the grilling on #2182: a proposal's participants learn what happened through a pull first, a cross-repo list of my proposals and their activity on loot propose and the private shell plus one ambient line after verbs that already reach the forge, measured against a locally kept last-seen marker; and then through an opt-in email, off by default per account, with separate per-event toggles, an own-actions toggle and a per-repo watch for owners and members. the forge stores no address: Clerk already holds one for every account the proposal door admits, and a sender worker outside the forge looks it up at send time and holds the only Clerk and mail credentials. an email never says more than the world can read, naming and quoting a metadata-public repo and sending a nameless nudge for a private one, enforced by the sender reading excerpts only through the anonymous views. the forge writes a text-free outbox row in the same transaction as each act; delivery is coalesced per proposal under an hourly ceiling with one-click unsubscribe, through a transactional provider on a sending subdomain, Postmark behind a swappable interface. the grant inbox was ruled out as the channel because it is a pull, and browser push is rejected for now. CONTEXT.md gains Proposal notification. graduates as #2405, #2406, #2407, #2408 and #2409. docs only, no code moves (#2182)
8af4b498 · dbf3dbe6… - ADR 0099 records the move of loot from millerbyte.com to loot.build (map #2412): the site and one-liner at the apex with www redirecting, artifacts at dl.loot.build, the forge at forge.loot.build, security@loot.build through Cloudflare Email Routing with no catch-all, the relay not recreated, and the production Clerk instance on loot.build; and a hard cutover, the operator decision, in which the new names serve beside the old, a release carries them, every clone re-points its forge remote, and the old names are removed with no alias or redirect kept. it states what that breaks for anything made before it, read from the code: an opted-in old binary POSTs telemetry to the old name silently, so the old names must end NXDOMAIN rather than answered by the millerbyte.com wildcard, which would hand those reports to Vercel; old --help links; installers and manifests pinned to dl.millerbyte.com; the crates.io placeholders published with the old homepage, which only a new publish by the operator fixes; and it records the measured costs of the move (a 19.2 s first unlock on the new origin, no forge change because a signed request does not bind the host). ADRs 0037, 0041, 0045, 0049, 0061, 0064, 0066, 0067, 0074 and 0097, whose decisions name a loot host, each gain an amendment pointing here, and a banner where they had none; their bodies keep the names they were written with (#2414)
bf2242c5 · dbf3dbe6…diff
Renames are not followed. loot's tree maps a path to an address, so a rename is a delete and an add. This list is the history of the name, not of the bytes.