Changes touching this path

• loot maroon refuses while a working change is in progress, where it signed a change built on every head, the working change among them: the re-seal took its tree from current_tree and its parents from heads, so the content of that change travelled under the maroon signature past the finalize gates loot new runs, a .env reached a peer holding no grant with exit 0, and the peer held the signed maroon over a parent no bundle ships. the check sits in maroon_inner, which forward and hard maroon share, before anything is sealed or recorded, and it covers a working change that holds no edit, such as one describe named over a clean tree, and one the implicit capture of the maroon has just recorded; the refusal names loot new as the route. building on the finalized tip was rejected, since the working change would stay a sibling head pointing the path at the old object. ADR 0010 gains a #2467 amendment, and CONTEXT.md, the help line and the maroon-identity skill say what maroon signs. a #1485 test whose maroon arm signed over a described working change now finalizes first and takes --no-snapshot, the spelling on which no upstream read promotes the key, and it stays red with the maroon flush deleted (0 passed and 1 failed); a relay purge test signs its anchor. pinned through the binary, red first: the peer read the .env and held two heads (2 passed and 3 failed over the maroon smoke pins). red under named mutations, each restored: no guard (11 passed and 1 failed over the engine maroon tests, 2 and 3 over the smoke pins), refusing only a working change that holds an edit (4 and 1 over the smoke pins), the hard arm unguarded (11 and 1 in the engine), and the refusal after the change is recorded (11 and 1 in the engine). no format, wire or migration byte moves, so this owes no deploy. cargo test green, 4671 passed over 142 binaries with 13 ignored (#2467) d03ee3f9 · 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.