Changes touching this path

• the read.pg plan pin no longer swallows the tail of the test it was inserted into: 674494c put its new it() for the tree read by manifest key in the middle of opens the metadata half with one boolean, published half unmoved, so the change, historyOfPath and publishedIndex assertions ran after the pin finally block and reported under the pin name. site/test/read.pg.test.ts closes the pin after its finally and moves those assertions back into the metadata-half test, which now reads as it did before 674494c plus the entryAt lines 674494c added. site/test/plan.ts states what planWithLoopsPricedOut needs of its db, every query on one connection inside one open transaction, instead of naming withOwner and withMember. read.pg keeps its one-client ReadDb rather than readDbFromUrl, which is a pool of up to 10 clients and so does not promise that the pin SET LOCAL and EXPLAIN share one transaction. red under named mutations, each restored, over the 16 read.pg tests: a moved change message assertion broken fails the metadata-half test under its own name (15 passed and 1 failed), where on the unfixed file the same mutation failed under the pin name (15 and 1), and OFFSET 0 dropped from treeAt fails the pin alone (15 and 1). the site live suites at 85 passed over 7 files against a throwaway Postgres 18 and the site gate green at 881 passed; site tests only, no Rust touched and no cargo test run. no deploy owed; it also files kzwowoww (kzwowoww) e50ebf01 · 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.