Changes touching this path

• loot new --no-snapshot runs the publish gate over the working change it signs, where it judged the disk: a path an ungated capture such as the implicit capture of loot migrate sealed published under a rule, and the disk then lost, was signed published with no --allow-publish and exit 0 through the 0.4.25 binary. under --no-snapshot the publish gate now judges the paths among the #2387 rows whose seal carries the @world marker, read in the same pass as those rows (Workspace::signed_rows, renamed from signed_provenance) through the refusing marker read, and decides them as it decides the disk (publish_gate_over); the capturing path is unchanged. the preflight of loot new under bare --no-snapshot now reads the same rows through Workspace::signing_gates, which the finalize seam calls too, where it judged the disk and could refuse a file on disk the signed change does not hold, which a user saw first, or pass a secret the change holds that the seam then refused; with -m it judges the disk that -m records, as before. ADR 0038 closes the publish gate its #2387 amendment left open and CONTEXT.md says so, and a #2219 summary test that signed a recorded publication without consent now passes --allow-publish and drops the consent it passed for a file the change does not hold. pinned through the binary, red first: the reproduction signed and the preflight refused a file the change does not hold, while the capturing pin passed (1 passed and 2 failed); the lockout arm #2387 left unpinned is pinned over the same fixture. red under named mutations, each restored, over the four pins: the publish gate over the disk under --no-snapshot (2 passed and 2 failed), the preflight over the disk under --no-snapshot (3 and 1), every readable recorded row taken as a publication (1 and 3), the recorded change judged on a capture (3 and 1), and the seal gate over the disk under --no-snapshot (3 and 1). no format, wire or migration byte moves, so this owes no deploy. cargo test green, 4659 passed over 142 binaries with 13 ignored (#2462) 87c3841e · 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.