Repository navigation
feat: add Atlas Cloud provider preset - #925
binyangzhu000-sudo wants to merge 5 commits into
Conversation
Signed-off-by: binyangzhu000-sudo <224954946+binyangzhu000-sudo@users.noreply.github.com>
|
@binyangzhu000-sudo is attempting to deploy a commit to the luokerenx4's Team Team on Vercel. A member of the Team first needs to authorize it. |
云端代理审阅(以 upstream
|
All three conflicts were the same both-sides-added-a-preset shape: upstream added an openrouter entry in the exact rows this branch adds atlas-cloud, in DEFAULT_MODEL_BY_PRESET and in the two matching spec expectations. Both entries are kept everywhere, openrouter first in upstream's position. Checked the auto-merged side too: the atlas-cloud entry in model-semantics.ts survived the merge intact. vitest src/ai-providers -> 42 passed; tsc --noEmit clean.
|
Synced with
Both entries are kept everywhere, I also checked the auto-merged side rather than assuming a clean merge is a correct one: the Verification on the merged branch:
No conflicts remain. |
This PR targets dev, but the previous sync on this branch merged upstream/master instead. That pulled master's 65 release commits in and put a version bump and a CI workflow edit into the diff, none of which belong to an Atlas Cloud preset. Merging dev this time absorbs all of it: the only conflicts were the two package.json versions, both resolved to dev's 0.93.1-beta, and the diff against dev is now the three src/ai-providers files this PR is actually about. Verified: vitest run — 800 files, 7039 passed, 4 skipped, zero failures; tsc --noEmit — zero errors.
|
Synced with This PR targets The preset itself is unchanged. I checked its shape against the other third-party presets in Verified:
|
Resolve the package.json / packages/cli/package.json version conflicts in favour of dev. The diff against dev remains the three src/ai-providers files for the Atlas Cloud preset. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: binyangzhu000-sudo <224954946+binyangzhu000-sudo@users.noreply.github.com>
|
Thanks for the review. Re-synced with the current
Verified locally: |
Summary
Verification
pnpm exec vitest run src/ai-providers/preset-catalog.spec.ts src/ai-providers/model-semantics.spec.ts src/workspaces/cli/shim.spec.ts services/uta/src/domain/trading/brokers/presets.spec.ts(80 passed)pnpm exec tsc --noEmitpnpm test: 3828 passed, 9 skipped; two unrelated tests timed out under the full parallel run and passed when rerun in the focused set; the catalog-contract failure found by the full run was fixed before the focused rerungit diff --check