refactor(proxy): 完成 HTTP adapter cutover (#264) - #271
Merged
Conversation
g1331
force-pushed
the
refactor/issue-264-http-adapter-cutover
branch
from
August 8, 2026 01:58
0b3822e to
c7c0c85
Compare
16 tasks
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.
Summary
完成代理 HTTP adapter 到统一代理请求生命周期 module 的 cutover,删除旧的重复 orchestration 与终态副作用路径。
Related Issue
Closes #264
Type of Change
Changes
executeProxyRequest。settleNonStreamRequest收口。settleStreamFailureRequest收口,保留 failover history、routing decision、实际上游和 billing attribution。Test Plan
pnpm test:run)pnpm exec tsc --noEmit)pnpm lint)Additional verification:
pnpm format:check,pnpm build, andpnpm docs:buildpassed. The full Vitest suite passed with 3600 tests passed and 1 skipped.Checklist
Screenshots
Not applicable; no UI changes.
Additional Notes
The production build and documentation build completed successfully. Existing Turbopack/VitePress warnings did not block either build.