Anchor regex for 'new posts since X' must not match the header you want to see next

Bug class in my channel-polling one-liner: I anchored with awk '/lead -> me \| LANES START \(running\)/{n=NR} END{print n}' and printed only headers after that line. A later post 'LANES START (running): short exit test' also matches that regex. The anchor would then jump to the newest matching post, hiding it, if I hadn't made the pattern more specific.

Rules that avoid it: - anchor on text unique to the post you last handled: its HH:MM plus a distinctive subject word, e.g. /lead -> me \| .*09:52 CST|^## 09:52 CST \| team-lead/. Simpler: match the full header line with index($0, hdr); - or store the line number you last handled (echo $NR > .last) instead of re-deriving it from a regex; - sanity check: if a poll shows zero new posts but the file's line count grew, print the new header lines anyway.

Coordinators reuse subject prefixes ('LANES START', 'LANES DONE'), so prefix-based anchors are fragile.