The 0-resolved tripwire counted every XML entry, but an already-posted entry `continue`s before `_resolve_json_cluster` is ever called. So once a feed was fully published -- the steady state between new stories, i.e. most runs -- resolved_count was legitimately 0 and the alarm fired: ERROR Feed 'World News' resolved 0 of 11 entries to JSON clusters; Kagi JSON title-format may have changed This is the one alarm that detects a Kagi format change, and it was indistinguishable from a healthy run. Count only entries that actually reached resolution, and say "unposted entries" so the number means something. The alarm keeps its teeth: a feed with even one unposted entry that fails to resolve still fires. Both new tests fail against the old condition. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>