Changes touching this path

• a land seeds the debug builds of registry dependencies as woyvmtwq seeded the release ones, from target/lane-seed under the primary, which the lands fill themselves: once a land from a lane that ran cargo test has published and freed the harbor, it copies the registry debug builds of that lane into target/lane-seed by the same rules, registry packages only by the Cargo.lock of the landed tree and again by that of the landing tree, copies under the cargo build locks, now taken shared on the source and exclusive on the destination, and nothing the destination holds already; the next land seeds its lane from there, where the debug builds of the primary predated the line-tables dev profile and matched no unit. measured in fresh copies of a lane, seven interleaved samples each of cargo test --locked --no-run --workspace at CARGO_BUILD_JOBS=4: a median of 162.7 s cold and 107.9 s seeded, 336 Compiling lines against 19, for a seed of 2.3 s over 387-391 units and 941-960 MiB, where the lane target/debug was 7.7 GiB; filling an empty seed directory took 2.6 s and a filled one copies nothing; after two hops every native link path under a target directory named the seeded copy, none the lane or the seed directory. the seed span on the timing line covers both profiles and the copy back closes a seed-refresh span. pinned in the new cargo_seed tests a_seed_directory_hands_the_next_lane_no_workspace_build (a lane into the seed directory and from there into a lane whose changed core is older than the seed, which rebuilds it and runs its own code) and a_destination_a_reader_holds_is_not_copied, and the orchestrator tests a_land_seeds_each_profile_from_its_source_and_copies_its_debug_builds_back and the_seed_directory_is_refreshed_after_the_harbor_is_freed. red under named mutations, each restored, over the 12 selected seed tests: path packages copied (4 failed and 8 passed), no destination lock (1 and 11), the destination locked shared (1 and 11), debug seeded from the target/debug of the primary (1 and 11), the copy back into the target of the primary (1 and 11), the copy back under the harbor (1 and 11). cargo test green, 4846 passed over 144 test result lines with 15 ignored. owes no deploy; lands use it once the release loot-first of the primary is rebuilt. it also carries comments on wwmonzor and rmwmkyvu and files qptwwkqx and uzkouqqx (lolzxwpk) f2cb7126 · 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.