Changes touching this path

• a land from a lane now refuses its sync over a primary where the adopt capture would refuse the whole position before it records a path, where it read as clean a primary whose pending paths match landed main and whose .loot was copied from another machine, ran loot adopt, whose capture refused, and reported relay=FAILED: Workspace::catch_up_blockers asks refuse_before_capture first, before it reads the tree, and returns its refusal as CatchUpBlockers::position_refusal, which is_empty counts, and the sync refusal prints it in its own words. a primary whose custody is locked already refused, since its open refuses the read as it refuses the adopt, and is now pinned. pinned: the_read_only_catch_up_judgment_returns_the_captures_refusal_of_the_position in loot-cli, a_primary_whose_loot_was_copied_from_another_machine_refuses_the_sync and a_primary_whose_custody_is_locked_refuses_the_sync in loot-first. red under named mutations, each restored, failed and passed: the read asking no position refusal, as before (1 and 0 in loot-cli, 1 and 2 in loot-first), the tree read before the ask (1 and 0), is_empty ignoring the refusal (1 and 2), the refusal printed as its code (1 and 2), an unreadable primary read as clean (1 and 2, the adopt ran), and the read failure unworded (1 and 2). cargo test green, 4949 passed over 144 test result lines with 15 ignored. CONTEXT.md, workflow.md and the land-change skill say so. owes no deploy (uxyruuuz) 8e9ec69a · 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.