Changes touching this path

• the serve::fetch_latency tests whose pin is what a walk reads, refuses and reports run their walks and fetches under fetch_latency::UNSPENDABLE, an hour, in place of the serving 15 s WALK_BUDGET, which the hit and miss test walk ran past at up to 31.7 s on loaded pre-land runs where it passes alone in 1.45 s: the hit and miss test, a_refused_get_fails_the_walk_and_stops_it, a_refused_walk_still_reports_the_reads_it_made, a_walk_that_fails_in_a_step_names_that_step_before_its_error_span and the_walk_gives_the_first_failure_recorded, with fetch_all gone and its callers on fetch_all_within. WALK_BUDGET is unchanged and the pins on it stay, among them the budget module and the cold fetch width arithmetic. with WALK_BUDGET cut to 1 ms and UNSPENDABLE set back to it, 5 of the 8 fetch_latency tests failed on the spent budget, and with the fix only the cold fetch fit failed (1 failed and 7 passed); red under named mutations, each restored: hits and misses swapped (2 failed and 6 passed), every read a miss (1 and 7), the blobs span lapped before the gets (1 and 7). twelve loot-forge lib suites run at once beside a loot-core cargo test each passed 677; cargo test green, 5017 passed over 145 test result lines with 15 ignored (wvyoprtz) 493d3d0f · 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.