fix(automation): cover the full BandScope review queue

CHANGELOG.md

@@ -118,6 +118,11 @@ this file. The format follows Keep a Changelog, and versioned releases follow
 Semantic Versioning where the repository publishes a release.
 
 ## [Unreleased]
+- Raise the BandScope hourly review-repair scan bound to 200 so the
+  oldest-first scheduler covers the current open queue and does not hide newer
+  non-draft pull requests behind older drafts; the one-writer and retry bounds
+  remain unchanged.
+- Raise `contextual_orchestrator_review_sidecar.sh`'s
 - **Pin `opencode-review-dispatch.yml` off the starved floating `ubuntu-latest` image.**
   The 2026-09-01 floating-image fix (see that entry below) pinned `strix.yml`,
   `opencode-review.yml`, and `noema-review.yml` -- the three required-check

docs/doctoring/bandscope-hourly-review-caller.md

@@ -21,11 +21,14 @@ without crossing product ownership boundaries.
 The caller runs at minute 53 of every hour and invokes the sealed central
 `pr-review-fix-scheduler.yml` with protected base `develop`. Minute 53 avoids the
 established product-specific heartbeat minutes already present on protected
-central `main`. Each heartbeat scans at most 50 open pull requests and dispatches
-at most one writer. The two-hour same-head retry floor prevents a later heartbeat
-from duplicating a legitimate OpenCode, Strix, Noema, browser, Rust, or
-NVIDIA-backed investigation. The non-cancelling concurrency contract preserves
-root-cause analysis already in progress.
+central `main`. Each heartbeat scans at most 200 open pull requests and dispatches
+at most one writer. The scheduler enumerates oldest-first, so the 200-entry bound
+covers the current 136-open-PR queue while preventing older draft PRs from hiding
+newer non-draft work. If the queue approaches that bound, operators must raise it
+deliberately and recheck the bounded runtime. The two-hour same-head retry floor
+prevents a later heartbeat from duplicating a legitimate OpenCode, Strix, Noema,
+browser, Rust, or NVIDIA-backed investigation. The non-cancelling concurrency
+contract preserves root-cause analysis already in progress.
 
 A writer may edit only after it establishes the first causal boundary, compares
 bounded remediation candidates, proves remediation feasibility, verifies writer