the agent runtime lock is ignored at any depth: .lootignore named .claude/scheduled_tasks.lock at the root only, and a session run from tools/ left tools/.claude/scheduled_tasks.lock, which loot read as live local work, so the land of kzknpprm came out relay=REFUSED over it and loot adopt refused until the file was moved aside. .lootignore adds **/.claude/scheduled_tasks.lock and keeps the root rule, since a **/ rule there matches only with a directory in front of the name; .gitignore names it at any depth as well. checked by hand with the release loot: the lock under .claude/, tools/.claude/ and a/b/.claude/ lists nowhere in loot status, and with the **/ rule alone the root copy listed. config only, no code; owes no deploy (swwzursm) 143e590f · 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.