Changes touching this path

• the silent unlock reads and files no standing self-grant: the device grant cache keeps each under the object it claims to open, in a store the vault database adds at version 4, and Keyring.keyFor and keysFor read and file the ones for the objects they are asked about, through the same sort and gates, keysFor in one read; the unlock files what is kept under no object, and moves each self-grant kept before under its object in writes of about 2 MiB, since one write of 60 MB held the store for 3.7 to 25 s in headless chrome. the live cache held 10,353 grants and 60,930,133 bytes, each self-grant carrying its object ciphertext, which reversed the verdict of qmlkwlkn, measured over small synthetic grants. over a fixture of that size and spread, up to 298,292 bytes, in headless chrome: the silent unlock 425 to 509 ms before and 68 to 74 after, and 1,224 to 1,303 and 80 to 84 at four times CPU throttling, while the keys of the 2,161 smallest grants went from 220 to 224 ms to 268 to 304, and from 931 to 993 to 1,182 to 1,387 throttled; the first unlock after the change files the old cache once, 440 to 515 ms, and its keys took 340 to 342 ms while the move ran. red under named mutations, each restored: the unlock filing every grant kept by object (5 failed and 13 passed), keyFor not reading them (5 and 13), keysFor not reading them (1 and 17), a grant read by object filed as verified (2 and 16), a read that lands after a lock filing (1 and 17), no move of grants kept before (2 and 16), a cache write without the vault check (1 and 17), the wipe leaving the new store (2 and 21), the count taken only from what is filed (6 and 12), a failed read not asked again (1 and 17), the move in one write (1 and 17), and the move going on past a write that did not land (1 and 17). cargo test green, 4888 passed over 144 test result lines with 15 ignored, and the site gate green at 970 passed. CONTEXT.md and ADR 0096 say so, and correct the qmlkwlkn verdict. a tab on an older build reloads once. owes a site deploy (vuvqoqyz) c89890f7 · 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.