feat(api): add speech profile and language-pair routing - #245
Open
jinyu918 wants to merge 6 commits into
Open
Conversation
Go coverage
Base branch: dev · Commit: f6525f5 · Test workflow run |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
torbys
approved these changes
Aug 13, 2026
Jerry-Yu-TeslaCoil
approved these changes
Aug 13, 2026
Jerry-Yu-TeslaCoil
left a comment
Contributor
There was a problem hiding this comment.
先前两条评审意见(生产默认严格校验会打掉非 en-US/zh-CN 目录对;ResolveSpeechRoute 未要求 TTS 双侧覆盖)在最新提交里都已处理:生产仍走 NewService(严格校验 opt-in),Resolve 路径已要求双侧 TTS。CI 全绿。
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
Implements Phase 1 of language-pair-based ASR/TTS provider routing.
speech_asr_profiles,speech_tts_profiles, andspeech_language_pair_routes.zh-CN <-> en-USanden-US <-> zh-CNresolve to the same route.NewServiceWithSpeechRouteValidatorand will be enabled in production after constructable provider profiles and routes are provisioned.legacy-defaultprofile pair and theen-US/zh-CNroute for compatibility.Validation
zh-CN <-> en-USresolve to the same active route.Scope
This PR establishes the API data model and validation boundary only. It does not build the realtime provider registry, prepare session bindings, consume language configuration events, or change media/provider protocol handling.
Related issue