Changes touching this path

• the dev profile carries line tables instead of full debuginfo: the workspace Cargo.toml gains [profile.dev] debug = line-tables-only, which test inherits, so the cargo test an implementer or a land runs keeps file and line in a backtrace and loses variable-level detail in a debugger, which CARGO_PROFILE_DEV_DEBUG=full brings back for one build; release and dist do not inherit dev and are unchanged. measured on the desktop with CARGO_BUILD_JOBS=4 and a target outside the lane, cargo test --no-run --workspace, three samples each alternating, medians: cold 326 s with full debuginfo and 157 s with line tables, a rebuild after touching loot-core 283 s and 62 s, and PDB bytes under target/debug 14.2 GB and 4.0 GB; the peak commit charge above its floor was 5.8 to 6.8 GB and 2.7 to 3.0 GB, with the machine at a median of 36 to 48 percent CPU per build, own build included, while another session ran. the LNK1171 note in docs/agents/workflow.md says line tables lower that peak and do not replace the cap. no test pins the profile and no test asserts on debuginfo. cargo test green, 4762 passed over 144 binaries with 13 ignored. no deploy owed; it also carries the live after-deploy numbers on nyvxmxqz and files ppwukxrx (kzzlsuqo) 02ce2dbf · 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.