A Status field mill cannot write stops the comment sweep and dispatch entirely

[slowernet]

poller.rb:32. @board.redrive raises first in tick, before anything else runs. Proven: comment fetches attempted = 0, every tick. So one misconfigured Status field silently stops mill reading comments at all — no answers, no dispatch.

Blocks a merge. Context: docs/notes/2026-08-20-plan-3a-review-triage.md, HIGH.

[slowernet]

Corroborated during the #11 review with a live demonstration: once any run row carries a desired_board_status the project cannot satisfy, redrive raises first in tick and the whole poller stops — no comment sweep, no dispatch, every tick. The #11 fix means the blocked run survives to be answered after the project is repaired, but nothing retries in the meantime. Worth noting the fix here should also make redrive isolate per-run failures rather than dying on the first.