Changes touching this path
- loot pull-grants now keeps the forge cursor only when every grant of the answer was handled, kept as standing custody or found never to apply, where each skip branch had to count its grant to hold it, so a grant no branch counts holds the cursor; a frame of this build format whose tag this build does not know, named by Frame::newer_tag over the Tag the decode dispatches on, holds it as a newer format does, where it passed as never applying; a grant expired by less than EXPIRY_GRACE_SECS, a day, longer than the widest time zone offset, is left pending in case this clock runs fast; and a failed unseal is named on stderr as a key not sealed to this identity, as the docs say. the ferry remedy matches every DeltaClass, its split test literal is joined, it says not to seal while loot status shows a deletion, and the seal-WIP refusal of a bare loot adopt or loot ferry counts the deletions the override would sign, read from two trees and only when it refuses. red under named mutations, each restored, failed and passed: the cursor moved regardless (5 and 8), a never branch not counting (4 and 9), an unknown tag passed (1 and 12), newer_tag at any major (1 and 0), no grace (1 and 12), an expiry always held (1 and 12), the old unseal wording (1 and 12), no deletion count (1 and 6), a count on every refusal (1 and 6), the old remedy ending (4 and 3), and a DeltaClass arm dropped fails to compile. cargo test green, 4923 passed over 145 test result lines with 15 ignored. CONTEXT.md and ADR 0057 say so. owes no deploy (uuqwrkyt)
5a473dfe · 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.