Manual lock-file deletion is instructed without warning users to stop all processes sharing those locks.
- Category
- Output Handling
- Confidence
- 99% confidence
- Finding
Unlinking a lock file does not release an fcntl lock held on its inode: an existing process can retain the old lock while another process creates and locks a replacement file, allowing both to enter the critical section. This is particularly dangerous in a concurrently running agent team because it can corrupt shared inboxes or task state and cause duplicate task execution; atomic JSON replacement does not prevent these logical races.
- Content
