tri tick: dirty work left after a released claim (a dead delegate) is never an anomaly #5895

tri tick (scripts/tri_loop/tick.py, t27#5787 / #5864) checks a dirty worktree only while a claim is HELD and stale. Once a tick releases its claim, a dirty worktree is never an anomaly, whoever left it.

Seen 2026-10-04 on cron 8782e5f8: tick 21 delegated two owner tasks to background agents in /tmp/trin-chat-zoom and /tmp/t27-run-steps, recorded held_by: "... live at tick 21 end", and released its claim. The session ended; both agents died with uncommitted work (last edits 10:39-10:41, no process in either directory). The next tick's card said ANOMALIES: 0. The loss was found by hand. held_by is free text with no clock, and tick.py does not read it.

Wanted: an anomaly orphaned-dirty when the claim is not held, a worktree is dirty, its newest dirty file is older than --stale-minutes, and no process has its cwd inside the worktree. Fresh writes or a live process mean the work is held: print it as a delegate line, not an anomaly. The fix line names the holder from held_by and the files, and never says add -A. Negative controls: a fresh write, and a live process standing in the tree.

Boundary

• scripts/tri_loop/tick.py