ci: schedule naruon hourly review repair - #1143
Conversation
|
Warning Review limit reached
Next review available in: 52 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 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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
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 |
|
Current-head review request for #1143. HEAD: 3a7a703 The exact HEAD now contains only the naruon hourly repair caller and its path-filtered contract/doctoring: minute 11, protected develop, one bounded dispatch, two-hour same-head retry, explicit review credentials, and no Copilot/NVIDIA secret forwarding. The unrelated agent-mention-router permission change was reverted because that responsibility is covered by #1162. Validate current Checks and active ruleset against this exact HEAD; do not reuse stale review state. |
|
Current-head revalidation for a749dff: 3 Naruon caller contract tests passed; actionlint for both changed workflows, compileall, and diff check passed. Required checks remain queued; no stale approval is being reused. |
|
@opencode-agent @cwl-noema-review Please review exact current head a749dff. |
|
@opencode-agent @cwl-noema-review Please independently review exact current head |
|
@opencode-agent @cwl-noema-review Please review this exact current PR head only: 5f2f1f4. Verify the pull-request comment reaction permission fix and the valid concurrency contract; review-only, no merge, dismissal, bypass, or auto-merge. |
|
Current-head repair evidence for
Review-only evidence; no merge bypass, dismissal, or auto-merge. |
|
Exact-head evidence for
|
a65b4d8 to
0bb567d
Compare
|
Exact current head |
|
@opencode-agent Please review exact current head |
|
@opencode-agent @cwl-noema-review Please independently review exact current head |
|
Current-head review evidence for 8f7a736: naruon minute-11 caller, develop target, one bounded dispatch, explicit OIDC/secrets, and path-filtered APA7 doctoring are present. Focused contract/regression tests: 15 passed; new caller and hourly workflow actionlint passed; compileall and diff check passed. The existing agent-mention router still emits the known local actionlint queue-key schema diagnostic; hosted quality remains the authority for that already-present queue contract. |
a843a57 to
c234d61
Compare
|
@opencode-agent Review exact current head c234d61 against main@2cce96f8. Rebased the Naruon minute-11 caller onto current main; it remains a thin read-only reusable-workflow caller for protected develop with explicit scheduler secrets, job-scoped OIDC, max 50 PRs/one dispatch/two-hour retry floor, and no NVIDIA/Copilot token. Verified: 5 focused caller/router tests, actionlint for the affected hourly workflows, compileall, interrogate, and git diff --check passed. The pre-existing agent-mention-router actionlint warning for nonstandard queue: max remains environment/schema-specific and is not claimed fixed. |
|
Current-head validation for exact commit |
|
Current-head validation for exact commit |
3a7a703 to
361f9eb
Compare
|
Rebased this PR onto current main; exact head is 361f9eb. The previously successful checks were tied to the pre-rebase head and are being revalidated. Please review this exact head only; merge remains gated on independent approval, terminal required Checks, and resolved threads. |
|
@opencode-agent review exact current head 361f9eb only after the rebase. Do not reuse predecessor approvals/findings; verify the naruon hourly caller, immutable source/credential boundaries, and current terminal Checks. |
OpenCode Review Overview
Pull request overviewOpenCode reviewed the current-head mergeability evidence and changed-file flow before approval, then found merge conflicts on the affected path. Findings1. HIGH Merge Conflict Guidance - Resolve the PR branch against the latest base branch
gh pr checkout 1143 --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:chore/add-naruon-hourly-review-repair
# rebase path only: git push --force-with-lease origin HEAD:chore/add-naruon-hourly-review-repair
Merge Conflict Evidence Mapflowchart 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: AGENTS.md"]
S2 --> I2["repository behavior"]
I2 --> Conflict["Merge conflict blocks this path"]
Conflict --> V2["required checks"]
Evidence --> S3["Docs: naruon-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_naruon_hourly_review_caller.py"]
S4 --> I4["regression suite"]
I4 --> Conflict["Merge conflict blocks this path"]
Conflict --> V4["targeted test run"]
Changed-File Evidence Mapflowchart 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: AGENTS.md"]
S2 --> I2["repository behavior"]
I2 --> Conflict["Merge conflict blocks this path"]
Conflict --> V2["required checks"]
Evidence --> S3["Docs: naruon-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_naruon_hourly_review_caller.py"]
S4 --> I4["regression suite"]
I4 --> Conflict["Merge conflict blocks this path"]
Conflict --> V4["targeted test run"]
Merge Conflict Guidance
gh pr checkout 1143 --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:chore/add-naruon-hourly-review-repair
# rebase path only: git push --force-with-lease origin HEAD:chore/add-naruon-hourly-review-repair |
![opencode-agent[bot]](https://avatars.githubusercontent.com/in/1549082?s=60&v=4){kind=small}
There was a problem hiding this comment.
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
DIRTYfor this pull request. - Root cause: Branch
chore/add-naruon-hourly-review-repaircannot be merged cleanly intomain; the changed-file flow below shows which review/runtime path is blocked by the conflict. - Fix: Merge or rebase the latest
mainintochore/add-naruon-hourly-review-repair, resolve conflict markers in the PR branch, rerun the focused checks, and push the same branch. - Repair commands:
gh pr checkout 1143 --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:chore/add-naruon-hourly-review-repair
# rebase path only: git push --force-with-lease origin HEAD:chore/add-naruon-hourly-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: AGENTS.md"]
S2 --> I2["repository behavior"]
I2 --> Conflict["Merge conflict blocks this path"]
Conflict --> V2["required checks"]
Evidence --> S3["Docs: naruon-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_naruon_hourly_review_caller.py"]
S4 --> I4["regression suite"]
I4 --> Conflict["Merge conflict blocks this path"]
Conflict --> V4["targeted test run"]
- Result: REQUEST_CHANGES
- Reason: mergeStateStatus is
DIRTY; mergeable isCONFLICTING. - Head SHA:
361f9eb34f3297a68d7ea1f327f98538aded9199 - Workflow run: 32408103281
- 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: AGENTS.md"]
S2 --> I2["repository behavior"]
I2 --> Conflict["Merge conflict blocks this path"]
Conflict --> V2["required checks"]
Evidence --> S3["Docs: naruon-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_naruon_hourly_review_caller.py"]
S4 --> I4["regression suite"]
I4 --> Conflict["Merge conflict blocks this path"]
Conflict --> V4["targeted test run"]
# Conflicts: # AGENTS.md
|
Merge-conflict repair pushed normally to current head
|
# Conflicts: # .github/workflows/hourly-nvidia-nim-review-repair.yml
Exact-head conflict repair
|
|
@opencode-agent @cwl-noema-review Fresh exact-head review request for central Naruon hourly caller PR #1143.
|
Dismissed as stale predecessor-head conflict evidence; current head c12457d was repaired and revalidated.
|
Exact-head audit update\n\nObserved hosted CI failure on the prior head: pip-audit lock refresh for PYSEC-2026-3721.\nRoot-cause fix: updated the hash-locked pip dependency to pip 26.2.1 with both package hashes.\n\nExact head: 9c2842a\nExact base: 6a79f07\nLocal verification: pip-audit clean and diff checks passed; the lock-only change has no additional local product test delta.\nGitHub mergeability: behind. Required checks and exact-head approval remain pending; decision remains WAIT_AND_REMEDIATE. |
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| pip==26.2.1 \ | ||
| --hash=sha256:71138adf1f4ca900cdb7d289c21b7494329f2332b6d85f0e1c42108c0384ed3e \ | ||
| --hash=sha256:f6ad667e89a1fe78046c8f13232b247200f5258d7828f3f7883d660878e0813f |
There was a problem hiding this comment.
🔍 Unrelated pip hash bump bundled in
requirements-pip-audit-ci-hashes.txt bumps pip 26.1.2 to 26.2.1, unrelated to scheduling the naruon caller. Confirm the lock was regenerated via the recorded uv pip compile command rather than hand-edited.
Was this helpful? React with 👍 or 👎 to provide feedback.
1 participant
Summary
ContextualWisdomLab/naruondevelopwith max 50 PRs, one dispatch, and a two-hour same-head retry floorVerification
python -m pytest -q tests/test_naruon_hourly_review_caller.py tests/test_pr_review_fix_hourly_contract.py tests/test_nonnest2_hourly_review_caller.py(26 passed)actionlint .github/workflows/naruon-hourly-review-repair.yml .github/workflows/hourly-nvidia-nim-review-repair.ymlpython -m compileall -q tests/test_naruon_hourly_review_caller.pygit diff --checkNo customer mailbox data or attachment bytes were uploaded.