Changes touching this path

• the forge records its wide events (ADR 0101): every request under server::scoped and lane is one JSON line on standard output in the shape the site error shipper reads, named on its answer in x-loot-event, which CORS now exposes; a signed caller is named by a key reference, a BLAKE3 derivation of the signing key set where the envelope verifies and cleared per request, never the key; a 4xx is an ok event with a refused note and only a 5xx is an error, its kind the ForgeError variant off the derived Debug, its message scrubbed, its frame the endpoint; errors, slow and signed requests are kept and 5 percent of the rest, and every request is counted into an exact per-minute line; each burn delete job run that did or failed anything is a forge.job event. pinned in wide.rs, 9 tests, a_verified_caller_is_named_on_its_event_by_a_key_ref and every_answer_names_its_wide_event_and_a_page_may_read_it; red under named mutations, each restored, failed and passed: the caller not recorded (1 and 8), no event header (1 and 0), the header not exposed (1 and 0), a refusal as an error (1 and 8), quotes kept (2 and 7), the key itself as its reference (1 and 8), a signed request sampled like the rest (1 and 8), begin keeping the caller (2 and 7). owes a release and a forge deploy, and files mwvpnyss for its deploy half (kwlnqtmy) 9a3350b1 · dbf3dbe6…

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.