fix(scheduler): require independent exact-head approval - #1270
fix(scheduler): require independent exact-head approval#1270seonghobae wants to merge 4 commits into
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@opencode-agent Please review the exact current head |
|
@opencode-agent Please review exact head |
|
@opencode-agent review Review exact current head 6cb7144 against protected main@0c6b9a6459c9dbdf5e23fb01df7a32a8a14964b3. Walk through the scheduler approval, exact-head binding, stale-review handling, and failure evidence; publish a substantive Reviews API verdict on this SHA. |
|
Exact-head local verification for 6cb7144: full pytest passed (1410 passed, 1 skipped, 16 subtests); coverage.py statement and branch coverage both 100% across scripts/ci; interrogate public docstring gate passed for scripts/ci/pr_review_merge_scheduler.py; compileall and git diff --check passed. No source change was needed after review. Hosted Checks and an independent exact-head approval remain required. |
|
@opencode-agent review Exact head: 6cb7144. Review the complete changed diff and report substantive findings with file/line evidence. |
|
Current exact-head Strix RCA: the required Strix run reached the scan gate, emitted zero vulnerabilities, but produced no authoritative report artifact. The log records NVIDIA NIM provider exhaustion/rate limiting followed by the configured openai-direct fallback returning HTTP 404. This is typed provider/backend infrastructure failure and fail-closed behavior, not a source finding. Next action: rerun the same-head Strix evidence after provider availability is restored; do not merge until the exact-head security evidence is complete. |
Exact-head review follow-up\n\nCurrent exact head: 6cb7144\n\nThe Strix provider rerun is now executing for this head after the earlier provider/backend failure. Please review the full scheduler diff and publish a substantive exact-head verdict only after the current required Checks complete. No predecessor success or review evidence is being reused. |
Customer outcome
The organization merge scheduler refuses direct merge and auto-merge until
GitHub reports
reviewDecision: APPROVEDand a non-author, non-OpenCode formalapproval is bound to the exact live head. If stale authorization left
auto-merge armed, the scheduler disables it.
Root cause and minimal repair
PR #828 identified a real separation-of-duties gap but its old-base
implementation replayed stale files and split the mature scheduler into a
second core. This clean protected-main replacement reuses the existing
scheduler and adds only the shared authorization boundary, exact PR author
evidence, regressions, changelog, and APA 7 doctoring.
The independent-review helper considers only each eligible reviewer's latest
exact-head approval-affecting state. A later same-head change request or
dismissal therefore revokes that reviewer's earlier approval. Generic
github-actions[bot], missing identities, self-review, comment-only review,and predecessor-head approval remain fail closed. GitHub remains authoritative
for last-pusher, CODEOWNERS, required-review, and ruleset policy.
Exact local evidence
aa0c93e5d461daf64c160b91066f90bad57a532fcheck, and CodeGraph sync: PASS
Merge boundary
Do not transfer review or check evidence from #828 or the predecessor head.
This exact head requires fresh hosted checks, zero unresolved current-head
threads, and independent exact-head approval before protected merge. Project #1
remains
In Progressuntil that lifecycle completes.