chore: sync 11 low-risk upstream provider/reliability fixes from anomalyco/dev - #56
Merged
sepo-eng merged 11 commits intoAug 13, 2026
Merged
chore: sync 11 low-risk upstream provider/reliability fixes from anomalyco/dev#56sepo-eng merged 11 commits into
sepo-eng merged 11 commits into
Conversation
Copy link
Copy Markdown
Sorry, something went wrong.
(cherry picked from commit 3a90639)
(cherry picked from commit 561afb4)
(cherry picked from commit c789868)
(cherry picked from commit 8571a92)
Co-authored-by: skyzhao1223 <skyzhao1223@users.noreply.github.com> (cherry picked from commit ca3df21)
Co-authored-by: skyzhao1223 <skyzhao1223@users.noreply.github.com> (cherry picked from commit 959c8bd)
Co-authored-by: Aiden Cline <rekram1-node@users.noreply.github.com> (cherry picked from commit 502310f)
Co-authored-by: Aiden Cline <rekram1-node@users.noreply.github.com> (cherry picked from commit beeabe2)
Co-authored-by: Aiden Cline <rekram1-node@users.noreply.github.com> (cherry picked from commit 6fea419)
Co-authored-by: Aiden Cline <rekram1-node@users.noreply.github.com> (cherry picked from commit 91df883)
Copy link
Copy Markdown
|
Thanks for your contribution! This PR doesn't have a linked issue. All PRs must reference an existing issue. Please:
See CONTRIBUTING.md for details. |
Sorry, something went wrong.
Copy link
Copy Markdown
|
This PR doesn't fully meet our contributing guidelines and PR template. What needs to be fixed:
Please edit this PR description to address the above within 2 hours, or it will be automatically closed. If you believe this was flagged incorrectly, please let a maintainer know. |
Sorry, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue for this PR
Closes #
Type of change
What does this PR do?
Sean asked me to look at what's diverged upstream (anomalyco/opencode dev, 35 commits ahead of ours) and bring in what's actually applicable to this fork. I triaged all 35 by testing an isolated cherry-pick of each against our current dev, not just reading titles.
22 of the 35 are not applicable and are excluded here — they're anomalyco's own hosted-SaaS infrastructure we don't run: packages/console (their web console), packages/stats (Cloudflare R2 analytics), the zen.mdx/go.mdx docs (their hosted model-proxy product), script/beta.ts (their release channel), the pulumi CI auth fix (their deploy pipeline — we use k8s/converge), nix/hashes.json (they build with nix, we don't), .github/TEAM_MEMBERS (would misattribute team membership to us), and their own version-sync commits (we track our own fork version independently).
2 more need a hand-merge, not a cherry-pick, and are handled in separate PRs: a compaction-prompt-clarity fix that partially conflicts with our TKT-379 fix (their version reverts to hiding the compaction marker, which we deliberately don't do — measured regression if reverted), and a Muse-family model routing fix (Sean plans to actually serve Muse Glimmer, so this needs to land correctly, not just cherry-picked blind).
This PR is the remaining 11: clean, isolated, low-risk fixes that cherry-pick without conflict and apply equally to any opencode deployment, ours included:
Each commit carries its original author and message (git cherry-pick -x, so the upstream sha is in every commit's trailer for traceability). No commit here touches a file we've customized for this fork.
How did you verify your code works?
EXPECTATION: each cherry-pick applies without conflict against our current dev.
HOW EXERCISED: git cherry-pick -x <sha> for all 11, sequentially.
OBSERVED: all 11 applied clean, zero conflicts.
VERDICT: pass.
EXPECTATION: the touched packages' own tests (brought in with each fix) still pass on our fork.
HOW EXERCISED: bun test --cwd packages/opencode test/plugin/github-copilot-models.test.ts test/session/retry.test.ts test/session/system.test.ts test/provider/transform.test.ts test/provider/provider.test.ts and bun test --cwd packages/core test/provider-xai-responses.test.ts test/provider-mistral.test.ts test/provider-groq.test.ts.
OBSERVED: 577 pass, 0 fail (opencode); 9 pass, 0 fail (core).
VERDICT: pass.
EXPECTATION: the two doc-fix commits don't break the docs build.
HOW EXERCISED: bun run --cwd packages/web build.
OBSERVED: build completes clean.
VERDICT: pass.
EXPECTATION: nothing else broke.
HOW EXERCISED: repo's own pre-push hook — bun turbo typecheck across all 38 workspace packages.
OBSERVED: 32 successful, 32 total.
VERDICT: pass.
Screenshots / recordings
Not applicable — no UI-visible behavior change beyond the OC-2 theme color fix (a single hex value in a theme JSON file).
Checklist