Changes touching this path

• a land from a lane no longer refuses its sync over a primary whose uncaptured edits are only landed main content: primary_state counted any pending path as work, so a primary that a git pull had moved to the landed commit came out relay=REFUSED although the loot adopt it guards fast-forwards over that content. it now asks Workspace::landed_foreign_paths, the per-path judgment the catch-up makes with ff_foreign_paths, read off the disk without a capture as two delta-seam verdicts against landed main and the dock tip over one walk, and a pending path matching either is not work; a path matching neither, or a dock not at or behind landed main, still refuses, and the read records nothing. the Unlanded check and the ticket-only allowance are unchanged. pinned: a_primary_whose_disk_holds_landed_main_uncaptured_syncs, whose verdict reads relay=pushed, a_landed_path_beside_one_matching_neither_still_refuses, a dock-ahead arm on the unlanded pin, and the_read_only_catch_up_judgment_names_what_the_adopt_refuses_over_and_records_nothing in loot-cli. red under named mutations, each restored, over the three loot-first pins: the old any-dirt refusal (1 failed and 2 passed), every dirty primary read as landed (1 and 2), an unjudged dock read as landed (1 and 2), the ancestor precondition dropped (1 and 2), the anchor side dropped (1 and 2, and the loot-cli pin 1 failed), the landed side dropped (1 and 2, and 1 failed), and a judgment that captures (2 and 1, and 1 failed). cargo test green, 4881 passed over 144 test result lines with 15 ignored. CONTEXT.md, workflow.md and the land-change skill say so, and the verb tier width is 424 methods. owes no deploy; lands use it once the release binaries of the primary are rebuilt. it also files tnlrmsmo, ntzsvkkv, nqzrszwo and oxuypvlz (qktqvvzr) b9bc7fd7 · 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.