Changes touching this path

• a land from a lane now refuses its sync over a primary with a pending path the adopt capture would refuse to record, where it read the primary as clean when that path matched landed main, ran loot adopt, whose capture refused, and reported relay=FAILED: Workspace::catch_up_blockers, which replaces landed_foreign_paths, also asks Readable::capture_refusals, the demotion refusal and the refusal to write over tip content this identity cannot open, read through demoted_paths and BaseRead::refuses_overwrite, which snapshot_assigning now refuses with too, forked from the pinned tip over the working change, and it still records nothing; a position with no pinned tip is not judged. the HoldsWork refusal now names its paths by cause, matching neither landed main nor the dock tip, over tip content this identity cannot open, or demoting the visibility the tip records, where it said the primary held a working change that is not empty, a primary not judged per path is said to have no pinned tip at or behind landed main, and the fix under it no longer asks for a primary holding nothing landed main does not. reproduced with an embargo that landed main lifts, which the capture refuses as a demotion before its sealed content gate, and one it moves earlier, which it refuses as sealed content. pinned: the_read_only_catch_up_judgment_names_what_the_capture_refuses_to_record in loot-cli, a_landed_path_the_adopts_capture_refuses_to_write_over_refuses_the_sync in loot-first, and the refusal wording in a_primary_holding_work_refuses_before_adopt_or_push. red under named mutations, each restored, failed and passed: the read asking no capture refusal, as before (1 and 1 in loot-cli, 1 and 3 in loot-first), is_empty ignoring the refusals (1 and 3 in loot-first), the demotion half dropped (1 and 1 in loot-cli), landed main as the fork base (1 and 1, and 1 and 3), the sealed cause unworded (2 and 2 in loot-first) and the old wording (2 and 2). cargo test green, 4940 passed over 145 test result lines with 15 ignored. CONTEXT.md, workflow.md, the land-change skill and the visibility census say so. owes no deploy (tyxoovwl) a36eb763 · 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.