Skip to content

chore: sync main into coverage-runner fix branch - #702

Closed
seonghobae wants to merge 7 commits into
claude/contextualwisdomlab-audit-governance-qyxe67from
main
Closed

chore: sync main into coverage-runner fix branch#702
seonghobae wants to merge 7 commits into
claude/contextualwisdomlab-audit-governance-qyxe67from
main

Conversation

@seonghobae

@seonghobae seonghobae commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Mechanical synchronization probe for #651. GitHub reported the branches as non-mergeable, so this temporary PR is closed without changes.

cwl-noema-review Bot and others added 7 commits July 31, 2026 06:27
* fix(governance): let organization sweep finish

* fix(governance): activate scheduled queue sweep

* fix: authenticate private review metadata reads

* chore: refresh head for last-push approval

* fix(opencode): add paid Zen review fallback

* chore: trigger exact-head Zen review pipeline

---------

Co-authored-by: Seongho Bae <me@seonghobae.me>
Co-authored-by: opencode-agent[bot] <219766164+opencode-agent[bot]@users.noreply.github.com>
Co-authored-by: seonghobae <8172694+seonghobae@users.noreply.github.com>
* Prefer NVIDIA NIM models in OpenCode review pool

OpenCode skipped usable reviews on fast-mlsirm PR #290+. Add an
OpenAI-compatible nvidia-nim provider, prioritize Nemotron/Llama NIM
candidates in OPENCODE_MODEL_CANDIDATES, skip when NVIDIA_API_KEY is
unset, and document the temporary hotfix bypass (no permanent security
gate weaken).

* fix(opencode): wire nvidia-nim into isolated review workspace

Include the NIM provider in the generated isolated opencode.jsonc used by
the model pool (not only OPENCODE_MODEL_CANDIDATES), prefer NIM defaults,
fail fast if the generated config lacks NIM, and update quick-gate asserts.
Org secret is NVIDIA_NIM_API_KEY, not NVIDIA_API_KEY. Map it into the
process env that opencode.jsonc and the pool skip check expect so
nvidia-nim/* candidates are not skipped on every run.
Raise primary OPENCODE_RUN_TIMEOUT and dynamic timeout-cap defaults from
600s to 3600s so big-repo reviews are not killed by the short fallback.
Keep free-tier failover at 600s; workflow env (5400s) still overrides.
#683)

Large-repo free-tier failover was still capped at 600s while primary
paths already use ≥3600s. Align OPENCODE_FREE_RUN_TIMEOUT_SECONDS to
3600 in the dispatch workflow and pool default, update contract/quick
gate asserts, and document NVIDIA_NIM_API_KEY → NVIDIA_API_KEY mapping
for nvidia-nim/* candidates.
* feat(review): add NVIDIA NIM provider

* feat(review): route public scanners through NVIDIA NIM

* fix(review): preserve provider fallbacks

* fix(review): propagate Strix fallback model

* test: enforce Strix timeout invariants

* fix: break OpenCode scheduler check cycle

* fix(review): ignore scheduler self-check failures

* fix(review): reserve fallback budget after NIM

* fix(review): enforce scoped NIM credentials

* test(review): scope NIM secrets to review job

---------

Co-authored-by: opencode-agent[bot] <219766164+opencode-agent[bot]@users.noreply.github.com>
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

2 similar comments
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@coderabbitai

coderabbitai Bot commented Aug 3, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: ad2dcf98-4842-45b0-b349-a20177860c94

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

@seonghobae seonghobae closed this Aug 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants