A watch saved before the no-checks clock may have seen its head's checks
pending, so its clock now starts at the next push instead of inferring
none were ever seen. Azure DevOps reports no checks because it cannot read
pipelines, so the notice is limited to GitHub; other hosts keep their
existing check, conflict, and comment semantics.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>