docs: record code queue supervision cadence

docs/reference/code-queue-supervision.md

@@ -52,6 +52,10 @@ Use:
 
 Long-running tasks with fresh trace or heartbeat evidence should normally be left alone. Polling every few minutes is preferred over repeated interrupt/retry cycles.
 
+For broad CI/CD migration waves, use a fixed supervision cadence unless an incident demands faster action. A five-minute poll loop is the default: read `codex queues`, read terminal or suspect task summaries, then either accept, retry, split a blocker, or leave healthy tasks alone. The loop should keep the supervisor doing useful non-overlapping work, such as documentation or issue triage, but that side work must not take over a worker's assigned implementation.
+
+When a task leaves `running` or `judging`, treat the result as unread work until the final response and judge record have been inspected. Only then should the supervisor decide whether to refill the concurrency window.
+
 ## Intervention Rules
 
 Intervene only when there is a clear reason.