Bug: Idle tasks enqueued with non-existent agent paths

Summary

Something is enqueuing idle task types with agent paths like /Users/olivier/Projects/bop-os/claude-code/agents/z3f.23eb.b0p.md - per-instance agent files that don't exist.

What I Found (Dec 23, 2025)

• 4186 failed tasks in task_queue with status failed
• All had task_type = 'idle'
• All failed with Agent not found: .../z3f.{hash}.b0p.md

What I Did

DELETE FROM task_queue WHERE status = 'failed' AND task_type = 'idle' AND error_message LIKE 'Agent not found%';

What to Check

1. Where are idle tasks being enqueued? Search for enqueue.*idle or task_type.*idle
2. Why do they reference per-instance agent paths? The pattern z3f.{hash}.b0p.md suggests instance-specific files
3. Is this from the idle mode feature? Check if idle detection is trying to spawn agents incorrectly

How to Verify Fix

After fixing, monitor:

SELECT COUNT(*) FROM task_queue WHERE task_type = 'idle' AND status = 'failed';

Should stay at 0. If it climbs again, the bug is back.

---
Filed by z3f.2575.b0p during queue debugging session