Changes touching this path

• a land run from a lane seeds the target/ of the lane with the release builds of registry dependencies that the primary target/ holds, before its pre-land gates: the new loot-first cargo_seed copies a unit only when the Cargo.lock of the position names its package as a registry package and not as a path package, under a shared lock on the cargo build locks of the source profile directory (skipping one a build holds), copies rather than hard-links (a same-name rebuild was measured writing fingerprint files and a proc-macro dll and pdb in place), renames each fingerprint into place last, overwrites nothing the lane holds and keeps file times, and prints a seed: line and a seed span; it never refuses, and is skipped under --skip-tests and in the primary. measured in fresh copies of a lane, twice each: the perf gate release build 70.67 and 70.07 s cold against 14.94 and 15.36 s seeded, the loot-wasm wasm32 release build 21.34 and 21.09 s against 7.43 and 7.36 s, for a seed of 5.06 and 5.11 s (1.43 GB). debug is not seeded: the primary debug builds predate the line-tables dev profile, and a seed of them took cargo test --no-run from 336 Compiling lines to 326 and saved no time, so a lane that never built Rust still pays that build. pinned in 7 cargo_seed tests, one the hunt experiment on a scratch workspace (two lanes over one seed each rebuild their own path crates, while a whole-target copy hands a third lane the primary binary), and a land_via order census; the rename census names the new rename, and was red until it did. red under named mutations, each restored, over the 7: path packages copied (4 passed and 3 failed), the fingerprint not copied (5 and 2), destination hashes not consulted (6 and 1), a held lock ignored (6 and 1); file times left unset stays green on Windows, whose copy keeps them; the seed moved after the pre-land gates (0 and 1 over the census). cargo test green, 4823 passed over 144 test result lines with 14 ignored. no deploy owed; lands seed once the primary loot-first is rebuilt; it also files lsoupnqm (woyvmtwq) e23e4b8b · 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.