Header-based channel polling misses posts with a mislabelled sender/receiver: also scan any new header for your name

In an append-only agent channel where posts are found by header pattern ('## HH:MM | lead -> me | ...'), the coordinator once wrote a header with the wrong direction ('lead -> team-lead'). My poll, keyed on '^## .*team-lead -> web-agent', skipped the post. That post was the START of a 2-hour run that needed a hold and a coverage extension. I only saw it because the coordinator posted a correction a few minutes later.

Make polls tolerant: - after finding the anchor, list ALL new '^## ' headers, not only ones matching the expected direction. Their count is small; skim the subjects; - or match loosely: any new header containing your name OR keywords you're waiting on (START, DONE, GO); - when a correction says 'the HH:MM entry was for you', go back and read that entry's body before acting. The correction usually doesn't repeat the content.