Changes touching this path

• a failure inside an unlock now ends it through forgetInMemory, which publishes locked, so the unlock card is usable where it sat disabled on unlocking, and a silent unlock throws the failure for the card to say, as for an engine that does not load, with the vault record kept; a vault holding a key the account holds retired asks for a key as one it does not hold does, where it unlocked as that key, and forgetInMemory forgets the keyring an unlock built before publishing it. also fixes yvonuouo: a lock telling carries an id, weighed at the time the tab first heard it by performance.now, where a time from Date.now could step backward and leave an unlock standing; an unlock takes its generation when asked for and stops at its next step once an end moves it, removing a seed it stored meanwhile, and a relocked unlock removes the seed it stored when still the one stored; forgetInMemory closes every workbench cache made since the last end, one no workbench shows included, so such a cache stays in memory until the unlock ends. red under named mutations, each restored, failed and passed of 24: no end on a failure (5 and 19), the silent catch swallowing every failure (2 and 22), a retired key not filtered (1 and 23), a wrong identity thrown (2 and 22), the built keyring not forgotten (2 and 22), a cache not kept from construction (2 and 22), the wall clock (2 and 22), no check once the engine loads (2 and 22), a seed stored as the lock was heard kept (1 and 23), a relock keeping its seed (1 and 23), and no check once the keyring is restored (1 and 23). cargo test green, 4919 passed over 144 test result lines with 15 ignored, and the site gate green at 1016 passed. CONTEXT.md and ADR 0096 say so. owes a site deploy (knqurkks) 8e9e4b6f · dbf3dbe6…
• the seal-WIP refusal of a bare loot adopt or loot ferry now counts deletions as loot status classes its rows, so the source of a recorded move is not one, where it counted every path gone from the tree and sent the reader to restore a move source, which turns the move into a copy; a workbench releases its SessionCache when it unmounts, which closes it then unless a write the unload guard counts as unsettled still reaches it, and then once none does or at the Lock, where each mount of one long unlock kept its cache to the Lock; a retired key is refused by the guard each unlock runs and by the passphrase save, where 24 words for one unlocked and stored the seed; an unlock ended by a lock whose seed removal fails says both, and the record is named for removal, in localStorage and in the tab, so a silent unlock that sees the name removes it before it recalls anything, or throws. also Tag::of matches the Tag discriminants, a debug_assert stops a settled count above the answer, the wire.rs body time claim names the readers it is true of, the unknown-tag hold is documented as unbounded by choice, Response::bytes takes the body without a copy when nothing else holds it, and a read into no room is not the end of a body. red under named mutations, each restored, failed and passed: a move source counted (1 and 1), no deletion counted (2 and 0), an empty read taken as the end (1 and 11), a branch counting twice (1 and 0, on the assert), and of 41 site tests: release never closing (1 and 40), release closing what a write reaches (1 and 40), a settled write not closing it (1 and 40), the guard not telling the cache (1 and 40), a closed cache kept in the set (2 and 39), a retired key let through (3 and 38), the removal failure replacing the end (1 and 40), the recall ignoring a noted record (2 and 39), no note before the removal (2 and 39), any record removed while one is noted (1 and 40). cargo test green, 4934 passed over 145 test result lines with 15 ignored, and the site gate green at 1026 passed. CONTEXT.md and ADR 0096 say so. owes a site deploy (ylopkxsk) 771ec092 · dbf3dbe6…diff

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.