Changes touching this path

• a refusal of a moved position now names each file another command moved, read off the fields of PositionState and of the draft slots, each destructured whole, where it named the heads, then the working change, and otherwise the conflict record, so a move of the settled ledger alone was named as the conflict record, and the draft check named every move its working change, a move of the pending handle included; a pool item whose run panicked is caught and finished, so the land test gate no longer names it as running until the pool ends, and the first such panic is carried out once the rest finish; a Tickets entry from Files while the manifest is still loading asks the list fetch from that manifest once it answers, unless the route answered first, where it asked only from a manifest already held. pinned: a_refusal_names_the_settled_ledger_when_only_it_moved, and the heads named in a_save_that_moved_the_position_refuses_over_a_newer_one, in loot-core; a_finalize_refused_over_a_moved_tip_names_the_heads, the arm tnlrmsmo named, and a_retry_over_unchanged_inputs_signs_the_version_id_the_refusal_left, which pins its version id claim, in loot-cli; a_panicked_item_is_not_named_as_still_running; and two site tests of a manifest in flight. red under named mutations, each restored, failed and passed: the ledger named as the conflict record (1 and 1), an unmoved working change named (2 and 0), the position check off (1 and 2), the pending handle named as the working change (1 and 2), a load that lets the pending handle win (1 and 2), the panic uncaught (1 and 14), a panicked item left unfinished (1 and 4), the panic not carried out (1 and 0), and of 29 site tests: an in-flight manifest ignored (1 and 28), a read that always waits for it (1 and 28, on a timeout), and no stop check (1 and 28). the ownership message is left at /wants for a pusher the custody list admits, decided and noted in forge_push.rs. doc fixes: save_to and persist no longer say each shared artifact merges, burned_under_lock names its lock as one of BURN_LOCKS, the disk record settles say what defines their callers, the grant cursor reads say what is pinned, the object cache says a repeat visit fetches a published object again and that the per-file bound is no share of the cache, vault.ts says what openDevice is exported for, the qktqvvzr sentences in CONTEXT.md and the land-change skill carry the dock condition, gc_keep_set names the leak a refused finalize leaves, .gitignore names .lootignore, and rewrap leftovers in orchestrator.rs, CONTEXT.md, workflow.md and grants.rs are joined. cargo test green, 4938 passed over 144 test result lines with 15 ignored, and the site gate green at 1028 passed. also closes qpxmrnxm and tzuxsroy. owes a site deploy (oxuypvlz) f557daaf · 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.