Skip to content

docs: retire superseded direct-NIM OpenCode hotfix - #1640

Merged
seonghobae merged 2 commits into
mainfrom
docs/retire-stale-nim-hotfix-current-main
Sep 1, 2026
Merged

docs: retire superseded direct-NIM OpenCode hotfix#1640
seonghobae merged 2 commits into
mainfrom
docs/retire-stale-nim-hotfix-current-main

Conversation

@seonghobae

@seonghobae seonghobae commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Current-main cleanup

Protected main@81b6f20d7f701bd2e50642ab107ab0f187ae6dc9 already has the gateway-only runtime state that old PR #1479 was trying to establish: opencode.jsonc enables only contextual-orchestrator, routes through contextual-orchestrator/orchestrator/free, and has no live nvidia-nim provider block. The old branch is 144 commits behind and no longer owns a safe current-main source delta.

One contradiction remains on protected main: docs/nvidia-nim-opencode-hotfix.md still instructs maintainers to configure a direct nvidia-nim provider, bind NVIDIA_API_KEY, and use a provider-specific admin-bypass hotfix window. That conflicts with the current gateway-only contract and the already-corrected docs/doctoring/hourly-nvidia-nim-autofix.md / ADR-0003 boundary.

This successor performs only the still-needed current-main cleanup:

  • delete the superseded hotfix document according to its own rollback section;
  • add a current doctoring record that binds the retirement to the exact protected-main configuration and clarifies that any queue-saturation bypass is a separately proven admission-recovery mechanism, never provider-specific permission.

No runtime code, workflow, credential, routing policy, security threshold, review identity, or branch-protection setting changes. Supersedes the remaining documentation responsibility of #1479 without transferring any predecessor checks/reviews.


Devin Review

@coderabbitai

coderabbitai Bot commented Sep 1, 2026

Copy link
Copy Markdown

Warning

Review limit reached

Next included review available in 45 minutes.

Check out review usage here.

View limit details

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.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: e79f978b-4c6d-4fdc-8e32-0e783a196731

📥 Commits

Reviewing files that changed from the base of the PR and between 81b6f20 and 43d1f1c.

📒 Files selected for processing (2)
  • docs/doctoring/nvidia-nim-opencode-hotfix-retirement.md
  • docs/nvidia-nim-opencode-hotfix.md

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.

Copy link
Copy Markdown
Contributor Author

QUEUE_SATURATION_CHICKEN_EGG verified on exact head 43d1f1c803a278aeeb2c3801a2ce69092154d35a.

  • The PR is mechanically mergeable and has zero review threads or submitted review objections.
  • The delta is documentation-only: delete the superseded direct-NIM hotfix and add the current gateway-only retirement record.
  • Protected main@81b6f20d7f701bd2e50642ab107ab0f187ae6dc9 independently proves the runtime state: opencode.jsonc enables only contextual-orchestrator and routes through contextual-orchestrator/orchestrator/free; docs/doctoring/hourly-nvidia-nim-autofix.md already documents the same corrected boundary.
  • All eight exact-head PR workflows returned by Actions (SBOM, CodeQL, SAST, OSV, Security Scan, Python Security, Secret Scan, Scorecard) are queued and none is failed.

The remaining admission blocker is therefore the verified central Actions backlog rather than source/security disagreement. Proceeding with the documented minimum-scope bypass pinned to this exact SHA. No predecessor review/check evidence is transferred.

@seonghobae
seonghobae merged commit 3a92259 into main Sep 1, 2026
14 of 30 checks passed
@seonghobae
seonghobae deleted the docs/retire-stale-nim-hotfix-current-main branch September 1, 2026 20:48

@devin-ai-integration devin-ai-integration 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.

Devin Review found 2 potential issues.

Devin Review

@@ -1,53 +0,0 @@
# NVIDIA NIM OpenCode model priority (hotfix)

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.

🔍 Baseline retains obsolete cleanup status

The direct-NIM audit still says the deleted document exists and cleanup was not attempted. Its reference and status are now stale.

Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.


## Verification

This record was created from protected `main@81b6f20d7f701bd2e50642ab107ab0f187ae6dc9`. At that revision, `opencode.jsonc` declares `enabled_providers: ["contextual-orchestrator"]`, uses `contextual-orchestrator/orchestrator/free`, and contains no live `nvidia-nim` provider block. The existing `docs/doctoring/hourly-nvidia-nim-autofix.md` already records the corrected gateway-only provider contract.

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.

📝 Info: Dormant provider block stays inactive

A nvidia-nim definition remains in root configuration, but enabled_providers excludes it. The record accurately describes active routing rather than configuration inventory.

Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

seonghobae added a commit that referenced this pull request Sep 1, 2026
Preserve protected main #1640 documentation cleanup while retaining only the seven intended solo-maintainer governance paths. Fresh pre-merge comparison showed the writer one commit behind and no content delta outside those seven paths. No force-push or history rewrite.
seonghobae added a commit that referenced this pull request Sep 1, 2026
Restore protected main #1640 documentation retirement byte-for-byte after ancestry integration exposed two predecessor documentation paths still present in the writer tree. Keep the final delta limited to the seven intended governance paths.
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.

1 participant