fix(autofix): route coverage-evidence failures from Required OpenCode Review into bounded RCA

[seonghobae]

Problem

PR #2079 exact head 9dccfaa0776950498e557390a2fa8d6c34e0baf4 exposes a deadlock in the central repair scheduler.

Required OpenCode Review run 34757059796 reached coverage-evidence job 103723268900 and failed at Measure test and docstring evidence because touched-callable docstring coverage is 76.47% (13/17; required 80%). The model-pool review is intentionally skipped after this pre-review gate fails, so no current-head OpenCode CHANGES_REQUESTED review can exist.

At current protected .github/main 78393ea901efc0d57b35dd1e383e473425b7c1da, scripts/ci/pr_review_fix_scheduler.py has two individually sensible rules that combine into a repair deadlock:

1. needs_rca_repair() can dispatch from terminal failed checks without a prior OpenCode review.
2. current_head_failed_checks() drops any CheckRun whose workflow name is in RCA_IGNORED_WORKFLOW_NAMES, which includes OpenCode Review, Required OpenCode Review, and OpenCode PR Review.

Therefore a source-backed coverage-evidence failure emitted inside Required OpenCode Review is ignored by the failed-check path, while the alternative review-text path cannot exist because coverage failure prevented the model review from running.

Reproduction / RED

Create a PR-shaped fixture whose latest CheckRun is:

• workflow: Required OpenCode Review
• check/job name: coverage-evidence
• conclusion: FAILURE
• no OpenCode review submission

Current behavior: current_head_failed_checks(pr) == () and needs_rca_repair(pr) == (False, ()).

Required behavior: the scheduler must classify this as bounded RCA evidence and dispatch repair_mode=rca for the exact head.

Also keep the recursive control-plane guard: an opencode-review orchestration/status failure itself must remain ignored, as must metadata-only/queue-controller failures. Do not make all OpenCode workflow failures repairable.

Minimal causal repair

Prefer check-name-aware filtering over globally removing the workflow-name guard. Allow the source-backed pre-review gate(s) such as exact coverage-evidence to survive the workflow-name exclusion while retaining exclusions for orchestration/control-plane checks. Add regression coverage for:

• Required OpenCode Review + failed coverage-evidence => RCA dispatch without prior review;
• same workflow + failed opencode-review => no recursive RCA;
• successful/pending newer coverage-evidence attempt supersedes stale failure;
• exact-head/dedup/live-head protections remain unchanged.

No threshold lowering, synthetic status, manual/no-op rerun, provider fallback, or self-approval is an acceptable fix.

Concrete blocked owner case

#2079 needs only four behavior-neutral fixture-method docstrings (Response.__enter__, Response.__exit__, Response.read, Opener.open) to clear the observed coverage RED, but the central autonomous repair lane currently cannot reach that source repair from the failed pre-review gate. The PR has an exact-head review comment recording that causal repair.

[seonghobae]

Owner repair advanced on #2170. RED was strengthened in 67dfa048446c96d99e3db2ebacdc02d16ed6294e so a newer IN_PROGRESS Required OpenCode coverage-evidence attempt suppresses stale failure for both current_head_failed_checks() and needs_rca_repair(). Production repair 7cda25c8b903108051e0d1d78e49d2b692a94a4a now admits only coverage-evidence through the retained OpenCode-workflow exclusion; opencode-review remains excluded, so no recursive control-plane repair is enabled. Mechanical source delta from the strengthened RED is +5/-1 in scripts/ci/pr_review_fix_scheduler.py. #2170 is SOURCE_REPAIRED / ACCEPTANCE_PENDING with fresh hosted workflows generated; do not close this issue until exact-head checks/review are terminal GREEN and the repair lands normally.

[seonghobae]

Current owner repair is now #2170 exact d3f1d0264912e74b897fdf2a0a6085100de4e40a. Self-review found the first source allowlist too broad because it keyed on check name alone. RED d01316990c9410165736ef09f0ab9979241078e8 now proves OpenCode Review / coverage-evidence remains excluded; production repair admits only the exact tuple Required OpenCode Review / coverage-evidence while retaining opencode-review recursion exclusion. The strengthened RED→fix compare is one commit ahead / zero behind and only +4/-2 in scripts/ci/pr_review_fix_scheduler.py. Fresh exact-head hosted runs are queued, so keep this issue open until terminal acceptance and normal landing.