Changes touching this path

• the relay's type-to-status rule stops being retyped at eleven handlers, but not by the From impls this ticket prescribed: NetError is deliberately mapped both ways here, being what the four wire decoders return and what the stores return, so a single From must pick one and the prescribed Internal would have flipped five decode sites from 400 to 500 and left a footgun where a later ? at a decode site silently became a 500 - a Refuse trait with named crossings or_malformed and or_internal is the same-sized change and behaviour-preserving by construction, handle_stow keeps its inverted mapping explicit and is now pinned as an exception rather than merely commented, and the forge turns out to be a bad model for a reason worth recording, since its stores already speak ForgeError so NetError arrives from one direction only and its unambiguous mapping is to 400, the opposite of what this ticket asked for; and the safety net this ticket claimed does not exist, because loot-relay-contract drives the stores directly and asserts no status anywhere, leaving the whole relay one status assertion above the auth layer, so five Malformed sites and three Internal ones now have live-HTTP coverage proved non-vacuous by flipping two mappings red first (#1653) 381c624c · 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.