Changes touching this path

• a repo stops going unopenable by every verb at once somewhere past 2100 changes, because the open's topo pass and the two loads shaped like it now share one explicit-stack walk instead of spending a call frame per ancestor, and that walk is pinned to emit exactly what the recursion emitted so the derived heads and the graph file's byte order cannot move (#1585) a463423e · 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.