Changes touching this path

• the tracker files three follow-ups and one live reading: swvnulnx records three timing tests that refused the kwxvxtqm land under load and passed alone, vmkxlwlx the loot burn guidance the v0.4.26 Known Issues pass narrowed on the page, proyvqqx a ferry after a mirror rewrite that ingests the burned bytes readable and then exits 1, and a comment on kwxvxtqm carries the live numbers after forge v0.4.25-deploy.14, the replacement run and the site deploy. tickets only, no code f9d87e72 · 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.