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…

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.