Skip to content

feat(automation): run Keyverse hourly NVIDIA NIM review repair - #1074

Open
seonghobae wants to merge 4 commits into
mainfrom
feat/keyverse-hourly-nvidia-nim-review-repair
Open

feat(automation): run Keyverse hourly NVIDIA NIM review repair#1074
seonghobae wants to merge 4 commits into
mainfrom
feat/keyverse-hourly-nvidia-nim-review-repair

Conversation

@seonghobae

@seonghobae seonghobae commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Buyer-perceivable gap

Hourly NVIDIA NIM review repair never scanned ContextualWisdomLab/keyverse. Live IdP pull requests such as ContextualWisdomLab/keyverse#83, #100, and #101 target protected main and stalled while Clearfolio, DiskSage, and fast-mlsirm received heartbeats.

Change

  • Thin scheduled caller at minute 29, base_branch: main, one dispatch, two-hour same-head retry.
  • Job-scoped id-token: write so the reusable scheduler can mint the OpenCode App fallback from GitHub OIDC.
  • Maps only PR_REVIEW_MERGE_TOKEN and OPENCODE_APPROVE_TOKEN. Never NVIDIA_NIM_API_KEY on the caller. Never COPILOT_GITHUB_TOKEN.
  • Independent pull_request / push / compileall path contracts.
  • Local 2× pytest + coverage + interrogate at 100% on this head.

Do not self-approve. Merge remains subject to two-approval + last-pusher ruleset. GitHub review/Checks wait is not a blocker.

Refs ContextualWisdomLab/keyverse#83, ContextualWisdomLab/keyverse#100, and ContextualWisdomLab/keyverse#101.


Open in Devin Review

@cursor

cursor Bot commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@coderabbitai

coderabbitai Bot commented Aug 17, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 38 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: dbb206c3-43fa-4f35-bc9a-a92f687eb1ff

📥 Commits

Reviewing files that changed from the base of the PR and between 55a8b57 and 298b6b8.

📒 Files selected for processing (5)
  • .github/workflows/hourly-nvidia-nim-review-repair.yml
  • .github/workflows/keyverse-hourly-review-repair.yml
  • ARCHITECTURE.md
  • docs/doctoring/keyverse-hourly-review-caller.md
  • tests/test_keyverse_hourly_review_caller.py

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.

❤️ Share

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

@seonghobae
seonghobae enabled auto-merge (squash) August 17, 2026 02:15
@seonghobae
seonghobae force-pushed the feat/keyverse-hourly-nvidia-nim-review-repair branch from 42cc5df to 6afb5ca Compare August 19, 2026 09:58
@seonghobae seonghobae moved this from Todo to In Progress in naruon Platform Roadmap Aug 19, 2026
@seonghobae

Copy link
Copy Markdown
Contributor Author

Rebased onto current main 9e9f59f3; resolved shared hourly-contract conflicts while preserving Keyverse paths. Caller tests passed (6 passed); actionlint passed on both changed workflows; diff check passed. Project #1 is In Progress.

@seonghobae
seonghobae force-pushed the feat/keyverse-hourly-nvidia-nim-review-repair branch from ec2eddf to f5a4195 Compare August 19, 2026 14:55
@seonghobae

Copy link
Copy Markdown
Contributor Author

Current-head maintenance: rebased the Keyverse hourly caller onto main bbedc1a. Exact head: f5a4195. Caller contract tests: 34 passed; actionlint and git diff --check passed. Protected hosted checks remain; no bypass used.

@opencode-agent
opencode-agent Bot disabled auto-merge August 19, 2026 20:48

@opencode-agent opencode-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

OpenCode reviewed the current-head mergeability evidence and changed-file flow before approval, then found merge conflicts on the affected path.

Findings

1. HIGH Merge Conflict Guidance - Resolve the PR branch against the latest base branch

  • Problem: GitHub reports mergeStateStatus DIRTY for this pull request.
  • Root cause: Branch feat/keyverse-hourly-nvidia-nim-review-repair cannot be merged cleanly into main; the changed-file flow below shows which review/runtime path is blocked by the conflict.
  • Fix: Merge or rebase the latest main into feat/keyverse-hourly-nvidia-nim-review-repair, resolve conflict markers in the PR branch, rerun the focused checks, and push the same branch.
  • Repair commands:
gh pr checkout 1074 --repo ContextualWisdomLab/.github
git fetch origin main
git merge --no-ff origin/main  # or: git rebase origin/main
git status --short
# resolve files, then git add <resolved-files>
# merge path: git commit
# rebase path: git rebase --continue
git push origin HEAD:feat/keyverse-hourly-nvidia-nim-review-repair
# rebase path only: git push --force-with-lease origin HEAD:feat/keyverse-hourly-nvidia-nim-review-repair
  • Regression test: Keep OpenCode approval gated on mergeability so model-output failures cannot approve a conflicted PR.

Merge Conflict Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Workflow (2 files)"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V1["actionlint plus required checks"]
  Evidence --> S2["Changed file (2 files)"]
  S2 --> I2["repository behavior"]
  I2 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V2["required checks"]
  Evidence --> S3["Docs: keyverse-hourly-review-caller.md"]
  S3 --> I3["operator or user guidance"]
  I3 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V3["docs review"]
  Evidence --> S4["Test: test_keyverse_hourly_review_caller.py"]
  S4 --> I4["regression suite"]
  I4 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V4["targeted test run"]
Loading
  • Result: REQUEST_CHANGES
  • Reason: mergeStateStatus is DIRTY; mergeable is CONFLICTING.
  • Head SHA: f5a4195e2a12e6953bc9b6ec823e2e36ce8d9489
  • Workflow run: 32293312756
  • Workflow attempt: 1

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Workflow (2 files)"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V1["actionlint plus required checks"]
  Evidence --> S2["Changed file (2 files)"]
  S2 --> I2["repository behavior"]
  I2 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V2["required checks"]
  Evidence --> S3["Docs: keyverse-hourly-review-caller.md"]
  S3 --> I3["operator or user guidance"]
  I3 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V3["docs review"]
  Evidence --> S4["Test: test_keyverse_hourly_review_caller.py"]
  S4 --> I4["regression suite"]
  I4 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V4["targeted test run"]
Loading

@opencode-agent

Copy link
Copy Markdown
Contributor

OpenCode Review Overview

  • Head SHA: f5a4195e2a12e6953bc9b6ec823e2e36ce8d9489
  • Workflow run: 32293312756
  • Workflow attempt: 1
  • Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode reviewed the current-head mergeability evidence and changed-file flow before approval, then found merge conflicts on the affected path.

Findings

1. HIGH Merge Conflict Guidance - Resolve the PR branch against the latest base branch

  • Problem: GitHub reports mergeStateStatus DIRTY for this pull request.
  • Root cause: Branch feat/keyverse-hourly-nvidia-nim-review-repair cannot be merged cleanly into main; the changed-file flow below shows which review/runtime path is blocked by the conflict.
  • Fix: Merge or rebase the latest main into feat/keyverse-hourly-nvidia-nim-review-repair, resolve conflict markers in the PR branch, rerun the focused checks, and push the same branch.
  • Repair commands:
gh pr checkout 1074 --repo ContextualWisdomLab/.github
git fetch origin main
git merge --no-ff origin/main  # or: git rebase origin/main
git status --short
# resolve files, then git add <resolved-files>
# merge path: git commit
# rebase path: git rebase --continue
git push origin HEAD:feat/keyverse-hourly-nvidia-nim-review-repair
# rebase path only: git push --force-with-lease origin HEAD:feat/keyverse-hourly-nvidia-nim-review-repair
  • Regression test: Keep OpenCode approval gated on mergeability so model-output failures cannot approve a conflicted PR.

Merge Conflict Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Workflow (2 files)"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V1["actionlint plus required checks"]
  Evidence --> S2["Changed file (2 files)"]
  S2 --> I2["repository behavior"]
  I2 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V2["required checks"]
  Evidence --> S3["Docs: keyverse-hourly-review-caller.md"]
  S3 --> I3["operator or user guidance"]
  I3 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V3["docs review"]
  Evidence --> S4["Test: test_keyverse_hourly_review_caller.py"]
  S4 --> I4["regression suite"]
  I4 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V4["targeted test run"]
Loading
  • Result: REQUEST_CHANGES
  • Reason: mergeStateStatus is DIRTY; mergeable is CONFLICTING.
  • Head SHA: f5a4195e2a12e6953bc9b6ec823e2e36ce8d9489
  • Workflow run: 32293312756
  • Workflow attempt: 1

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Workflow (2 files)"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V1["actionlint plus required checks"]
  Evidence --> S2["Changed file (2 files)"]
  S2 --> I2["repository behavior"]
  I2 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V2["required checks"]
  Evidence --> S3["Docs: keyverse-hourly-review-caller.md"]
  S3 --> I3["operator or user guidance"]
  I3 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V3["docs review"]
  Evidence --> S4["Test: test_keyverse_hourly_review_caller.py"]
  S4 --> I4["regression suite"]
  I4 --> Conflict["Merge conflict blocks this path"]
  Conflict --> V4["targeted test run"]
Loading

Merge Conflict Guidance

  • Current merge state: DIRTY
  • Base branch: main
  • Head branch: feat/keyverse-hourly-nvidia-nim-review-repair
  • Fix direction: merge or rebase origin/main into feat/keyverse-hourly-nvidia-nim-review-repair, resolve conflict markers in the changed files, rerun the focused checks, then push the same branch.
  • Repair commands:
gh pr checkout 1074 --repo ContextualWisdomLab/.github
git fetch origin main
git merge --no-ff origin/main  # or: git rebase origin/main
git status --short
# resolve files, then git add <resolved-files>
# merge path: git commit
# rebase path: git rebase --continue
git push origin HEAD:feat/keyverse-hourly-nvidia-nim-review-repair
# rebase path only: git push --force-with-lease origin HEAD:feat/keyverse-hourly-nvidia-nim-review-repair

@seonghobae
seonghobae force-pushed the feat/keyverse-hourly-nvidia-nim-review-repair branch from f5a4195 to 16112a2 Compare August 20, 2026 01:23
@seonghobae

Copy link
Copy Markdown
Contributor Author

Rebased onto current origin/main c47bee5 and preserved the existing hourly caller path set.

Current HEAD: 16112a2

Validation on this HEAD:

  • pytest -q tests/test_keyverse_hourly_review_caller.py: 6 passed
  • actionlint: caller and hourly dispatcher passed
  • compileall and git diff --check passed

@OpenCode review this exact HEAD after the rebase.

@seonghobae
seonghobae force-pushed the feat/keyverse-hourly-nvidia-nim-review-repair branch from 16112a2 to 4e88010 Compare August 20, 2026 04:44
@seonghobae

Copy link
Copy Markdown
Contributor Author

@opencode-agent review the exact current head $head_oid against protected base 2cce96f. Rebased this hourly caller onto current main; contract tests, changed-workflow actionlint, and diff --check were run on the exact rebased source. The caller keeps explicit target identity, bounded dispatch/retry, OIDC/approved secret scope, and no COPILOT token forwarding. Treat predecessor reviews/checks as historical and do not approve from queued or status-only evidence.

Copy link
Copy Markdown
Contributor Author

@opencode-agent Review the current exact head of the Keyverse hourly review-repair caller. Verify the thin caller targets ContextualWisdomLab/keyverse protected main, delegates to the product-neutral central scheduler, applies the one-dispatch and same-head retry bounds, keeps non-cancelling concurrency, grants only read contents plus job-scoped OIDC, maps only established scheduler credentials, and does not expose provider, merge, release, or protection authority. Reacquire exact-head checks and formal review without altering the branch.

@seonghobae
seonghobae enabled auto-merge (squash) August 20, 2026 06:19
@opencode-agent
opencode-agent Bot disabled auto-merge August 20, 2026 07:00
@seonghobae
seonghobae dismissed opencode-agent[bot]’s stale review August 20, 2026 09:41

Dismiss stale review: review commit f5a4195 is not current PR head 4e88010; current-head review is required.

Add a thin minute-29 caller for ContextualWisdomLab/keyverse on protected
main. The caller maps only established scheduler credentials, grants
job-scoped OIDC, and leaves NVIDIA_NIM_API_KEY on the reusable worker.
@opencode-agent
opencode-agent Bot force-pushed the feat/keyverse-hourly-nvidia-nim-review-repair branch from 4e88010 to 507ae5e Compare August 20, 2026 10:55
@seonghobae

Copy link
Copy Markdown
Contributor Author

@opencode-agent Please review the exact current PR head 3bb0af9. Re-check changed-file scope, current mergeability, unresolved threads, and all required checks. Do not approve a stale head.

devin-ai-integration[bot]

This comment was marked as resolved.

Copy link
Copy Markdown
Contributor Author

Exact-head review renewal

  • current head: 298b6b8eef50ab4f096b9e5778403fad2f908e20
  • RCA fixed: the Keyverse section had split the preceding nonnest2 paragraph in ARCHITECTURE.md, and CLAUDE.md contained a duplicated/incomplete product-caller bullet
  • fix: restored the complete nonnest2 contract, kept one actionable scheduler-boundary bullet, and added regressions for both documentation invariants
  • local exact-head evidence: 24 focused caller tests passed, actionlint passed for the caller and shared quality workflow, compileall passed, and git diff --check passed
  • hosted Checks for this new head are newly queued; no qualifying independent approval is present

The two review threads are addressed; merge remains subject to fresh terminal protected Checks and independent approval.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

1 participant