Tracked under #6.
Scope
Params::set_translate(true) is wrapped today (1-line passthrough), but the wrapper ships no test coverage of the full translate-task flow (token-id remapping, prompt seeding, language-id handling under translate).
Symbols
Params::set_translate (already exposed).- Token-id ranges affected by translate vs transcribe (
token_translate / token_transcribe).
- Prompt seeding behaviour when
translate = true.
Why deferred
No caller has exercised the translate path against this wrapper. The setter exists, but there's no regression coverage to catch a future upstream change that breaks translate output (e.g., language-id semantics, prompt-token order).
Acceptance
- An integration test that runs translate on a small audio fixture and checks the output is English even when the input audio is non-English.
- A unit test pinning
set_translate(true) + set_language("zh") interaction (translate task with explicit source language).
- Documentation pass on
Params::set_translate to spell out the behaviour.
If you're using the translate task in production, drop a comment.
Tracked under #6.
Scope
Params::set_translate(true)is wrapped today (1-line passthrough), but the wrapper ships no test coverage of the full translate-task flow (token-id remapping, prompt seeding, language-id handling under translate).Symbols
Params::set_translate(already exposed).token_translate/token_transcribe).translate = true.Why deferred
No caller has exercised the translate path against this wrapper. The setter exists, but there's no regression coverage to catch a future upstream change that breaks translate output (e.g., language-id semantics, prompt-token order).
Acceptance
set_translate(true)+set_language("zh")interaction (translate task with explicit source language).Params::set_translateto spell out the behaviour.If you're using the translate task in production, drop a comment.