Changes touching this path

• loot pull-grants keeps the cursor it asked from when the ack of the grants it filed fails, where it moved past them, so the forge kept them un-acked while this store never fetched them again, and stderr now says the next pull fetches them again to ack them. which grants hold the cursor is read off the refusal type: an envelope or frame of a newer version than this build reads, a quarantine write that failed, and an apply refusal that never_applies does not name hold it, while an envelope or frame that does not read, a frame that is not a sealed grant, an expired grant and a key not sealed to this identity are named on stderr as grants that can never apply here and no longer hold it, where one such grant in the first answer kept every pull a whole pull. a failed unseal carries the unauthorized code. the wvyrkooo pin of a grant left pending used a key not sealed here, so it now pins that such a grant is passed, and the hold is pinned by a failed quarantine that the next pull quarantines and by a newer frame and envelope. the forge cursor carries no instance identity and the forge has none to give it, so CONTEXT.md, ADR 0057 and grant_cursors say that any forge whose deposit orders start again below a kept cursor, restored or a new instance behind the same URL, misses the same way until .loot/grant-cursors is deleted. red under named mutations, each restored, each 1 failed and 0 passed: the failed ack ignored, the old ack wording, an expired grant held, a key not sealed here held, the unseal left a backend error, a bad envelope held, an unreadable frame held, a failed quarantine passed, a newer frame passed, and a newer envelope passed. cargo test green, 4919 passed over 144 test result lines with 15 ignored. owes no forge deploy (lxmysqxp) 71d7905c · 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.