Several worktree operations now handle lock-state edge cases more carefully:
- Stale-lock self-heal failures are now logged:
[worktree] skipped the stale-lock self-heal for <path>: <reason> - When the worktree registry is unreadable, operations log
[worktree] left the lock on <path> — cannot read the worktree registry to verify ownership cleanupWorktreelogs when it keeps a worktree because the registry is unreadable, instead of silently skipping cleanupcleanupStaleAgentWorktreeslogs each kept worktree with the lock reason
Evidence
Worktree lock diagnostics (search for "cannot read the worktree registry to verify lock ownership")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.