pr-comment-looplisted

# PR comment loop ## Step 0 — when no reviewer is coming This loop processes findings; a repo no bot reviews produces none, and the failure is a PR handed over unreviewed. Config is not evidence: hosted reviewers are usually free for public repos only, and their config file grants nothing without the app also having access. Ask whether one has ever run there: ```bash # .user.type is the account's own kind — matching logins against "bot|ai" # counts a human called chair as a reviewer and misses a bot called sentry { gh api "repos/<owner>/<repo>/issues/<n>/comments" --paginate --jq '.[]|select(.user.type=="Bot")|.user.login' gh api "repos/<owner>/<repo>/pulls/<n>/reviews" --paginate --jq '.[]|select(.user.type=="Bot")|.user.login' } | sort -u ``` Empty means you are the review, so get one from a **fresh context** — the value is in not having authored the thing. Give it what it cannot discover (what is vendored, what is deliberate, what is already settled), point it at the PR and the checked-out branch, tell it to run the claims rather than read them, and require both an explicit "nothing to report" per category and a verdict. Its reply is not a GitHub comment, so step 2 will not find it: carry the returned findings as this round's list, and re-enter at step 3 to verify each against the source like any bot's. No review obtainable at all → say so and hand the PR back, rather than merging on your own approval. **The durable fix is repo-side:** an advisory workflow that re