the spike-crdt 50k-file scale test leaves a plain cargo test: scale_and_transfer_50k is #[ignore]d with a reason naming this ticket and still runs under cargo test -p spike-crdt -- --ignored (1 passed in 21.79 s). nothing depends on the spike crates beyond workspace membership, and ADR 0002, CONTEXT.md and docs/bakeoff cite the bake-off numbers and a reproduce command rather than requiring the test on each land, so each now names the flag that runs it; no census pins the ignored count. the spike-dag twin stays in the gate, because it drives DagRepo, the engine loot ships, through a 50k-file bundle and apply in about 2 s, and a comment beside it says so. measured in this lane on a debug build, the spike_crdt binary went from 22.26, 22.55 and 22.73 s (6 passed) to 2.14, 2.15 and 2.15 s (5 passed, 1 ignored), and the workspace cargo test from 239 s to 215 s wall, so a land workspace-tests span should drop by about 20 s per pass. with the ignore disabled the full run read 4800 passed with 13 ignored and spike_crdt 6 passed at 23.30 s, restored to 5 passed and 1 ignored. cargo test green, 4799 passed over 144 test result lines with 14 ignored. no deploy owed (lxryvmqp) db5980c3 · 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.