Changes touching this path

• the History ledger walk carries no record of the versions it read on its rows: each row writes its depth as the scale of a zero, 0 then 0.0 then 0.00, and since a numeric compares by value a recursive UNION drops every later row of a version, so the walk keeps one row per version, at its least depth, and reads its parents once, where the zlulwtlw walk carried seen on every depth row and over 16 lanes of 2,100 changes stored 1,127,928 kB and took 9.8 s for a first page. measured as forge_owner on a throwaway Postgres 18, a first page in medians of 3, for the walk before zlulwtlw, the zlulwtlw walk and this one: this repo graph 259, 36 and 31 ms, the 1,400-deep line 33, 34 and 32 ms, 2 lanes 91, 373 and 87 ms, 4 lanes 187, 1,067 and 182 ms, 8 lanes 361, 3,055 and 338 ms, 16 lanes 735, 9,823 and 700 ms; the size query over this repo graph, the line, and 2 and 16 lanes went alike, 258, 36 and 29 ms, 32, 33 and 30 ms, 86, 381 and 84 ms, and 686, 9,463 and 654 ms. the answers compared equal to the walk before zlulwtlw row for row over this repo graph, the line, and 2 and 16 lanes at depth caps of 2000, 300 and 7, and over 21,000 random graphs with several heads, missing parents and depth caps: 143,645 rows and no difference, where a step of two places differed on 17,657 graphs and a value distinct per depth left 47,724 versions walked more than once. pinned in a new owner.pg test over 4 lanes of 150 changes: the answer, a walk capped at depth 5, and no CTE the page scans storing more than 256 bytes a version. red under named mutations, each restored, over the 4 selected live tests: the zlulwtlw walk back (1 failed and 3 passed, 1,642 kB against a bound of 150), the walk before it back (1 and 3), a value distinct per depth (1 and 3), and two places a step (2 and 2). cargo test green, 4842 passed over 144 test result lines with 15 ignored, the site gate green at 915 passed, and the site live suites 94 passed. CONTEXT.md says so. owes a site deploy and no forge migration (rmwmkyvu) 01378d5e · 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.