Changes touching this path

• serve::held_tips takes the tips of a have over the ancestry the forge graph holds rather than over direct parents, so a have that skips versions no longer has a manifest read for each version it names: on the offer_cost fixture a have naming every other version of a 20-change line, its head included, had 10 manifests read and now has 1, pinned in the new a_gapped_have_has_the_manifests_of_its_tips_over_the_graph_read, and ADR 0075 says so. the record_deposit doc states what defines its writers, the one door to the deposit ledger of a position, which takes the remote, instead of naming callers, a list that had left out the runner deposit. judgement calls: bundle_walk takes have, wants and depth as one Ask and drops its clippy::too_many_arguments allow, the rideable closure called in place is the helper serve::rideable, the seed: line prints MiB, and the cargo_seed doc says nothing is overwritten only of what the destination held when the seed read it, since the seed takes none of the lane build locks. not taken: sharing the batch loop of a push deposit with the runner deposit, which differ in what they seal, how they bound a call and what they record. red under named mutations, each restored, over the 17 offer_cost tests: tips over direct parents (16 passed and 1 failed), the named versions counted among their own ancestors (13 and 4). cargo test green, 4827 passed over 144 test result lines with 14 ignored. owes a forge deploy for the fewer manifest reads (xukurtyx) 30c6668f · 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.