Recurring bot quota/trial notices (Codex usage limits, Qodo trial, CodeRabbit review-limit) still block approval — add info_status_patterns; fix stale maintainer-resolve refusal message #1932

Summary

With #1918 (PR #1920) live, a clean SonarCloud pass no longer blocks approval. But the other recurring operational notices from registered review bots still do. They repeat on every push while a bot is out of quota, and nothing can clear them without dev-lead:

• chatgpt-codex-connector: "You have reached your Codex usage limits for code reviews…". There were four of these on PR feat: implement issue #1903 — Register cubic (cubic-dev-ai) as an advisory reviewer — add it to the reviewer council and let dev-lead act on its findings #1907 alone.
• Similar quota and trial notices from Qodo ("Qodo reviews are paused because your trial has ended") and CodeRabbit ("Review limit reached…"), per dev-lead's own unmarked acknowledgement comments block the approval they exist to unblock — 5 self-inflicted gate blockers on one PR #1919's evidence.

scripts/maintainer-resolve-comment.sh deliberately refuses these, because its bot path is restricted to sources with an info_status_pattern and only sonarqubecloud has one. So a maintainer has to hide each notice by hand in the GitHub UI. On PR #1907 (2026-09-25) I did exactly that for four Codex notices, posting a maintainer-resolve-marked reply first.

Acceptance criteria

1. Add info_status_pattern rows for the exact, anchored text of each registered bot's quota, rate-limit or trial notice, where that notice carries no code finding. Start with Codex's usage-limit notice, then Qodo's trial-ended notice and CodeRabbit's review-limit notice. Use fixtures from real comments. Coordinate with cubic refusal detection: tighten to the real trial-ended notice and classify refusals in formal reviews (after trial ends ~2026-09-29) #1930 (cubic).
2. Each pattern matches only the notice, never a genuine review from the same bot, with tests for both.
3. Fix the refusal message in maintainer-resolve-comment.sh. It still says the path accepts "a REGISTERED REVIEWER BOT's comment", but after the feat: implement issue #1918 — Approval gate can never clear bot status comments — SonarCloud re-posts 'Quality Gate passed' on every push and #1911's resolve script is self-scoped, so the #1894 queue is still deadlocked #1920 hardening it accepts only registered info-status bots. A registered finding bot such as Codex is refused while the message implies it is eligible.
4. Remember the rollout: the gate runs inside pr-review, so a pr-review/v1-next cut (and ring promotion) is needed before this takes effect.