Changes touching this path

• the per-dock load stops materializing the change graph twice, because reachable_from now owns its pool and moves each reachable node out of it instead of deep-copying a complete path manifest per change and dropping the original, and it moves them in a second pass over the ids the shared topo walk emits so that walk keeps yielding borrows and the graph file byte order stays the one #1585 pinned (#1547) ea3859e4 · 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.