Changes touching this path

• a Lock now closes the workbench cache, where the Tickets view kept the flat runs of content keys it handed the core, with the folds they opened, after the keyring had zeroed its own: forgetInMemory, the path every end of an unlock takes, empties and closes each held SessionCache, a write to one after that keeps nothing so a read in flight puts nothing back, WorkbenchContext.cache is typed as one so a plain Map is not assignable to it, and the workbench takes a new one for the next unlock. a read of the Tickets list again after a write reuses keys only when the keyring that opened the list shown is the one of this session, and otherwise reads from nothing. each lock telling carries the time the lock began, and a tab whose reader unlocked by passphrase or words after it keeps that unlock, where the telling sent once the wipe settles relocked it; an unlock recalled from the vault is relocked by any telling, and every unlock by a bare lock message from an older build. the broadcast doc no longer says a told tab re-reads the vault, and a silent unlock that throws, as on an IndexedDB error, says why on the unlock card. pinned: no fixture key reachable from the cache once the unlock ends, a read in flight putting nothing back, a read again under another identity asking its own keyring for every key, and the lock rules. red under named mutations, each restored: forget not closing caches (2 failed and 1 passed), a closed cache still keeping writes (1 and 2), reuse under any keyring (1 and 2), a lock telling ignoring the unlock time (2 and 3), a silent unlock counted as asked (1 and 4), a message without a time read as time zero (1 and 4), a released cache still held (1 and 4), and the card reason left bare (1 and 4). cargo test green, 4919 passed over 144 test result lines with 15 ignored, and the site gate green at 1006 passed. CONTEXT.md and ADR 0096 say so. owes a site deploy (kqpqnmqx) 80ed4a15 · 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.