Offer Whisper's Translate to English only on models trained for it (canTranslate)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docs/Decisions.md

@@ -1224,3 +1224,20 @@ whole-file output is equally bad, which is exactly what the absolute bar
 exists to catch.
 **Consequence:** full `bun test` ≈ 19 min on CPU (en_alien ≈ 20 min of it
 on a cold run); the fast suite excludes this file.
+
+## D-WS4a — Whisper's "Translate to English" only on models trained for it (`canTranslate`)
+**Status:** Accepted (2026-10-29) · spec 001 Goal 4a
+`WhisperModel` gains `canTranslate: boolean` (`src/lib/models.ts`): **true** for multilingual
+tiny / base / small / medium, **false** for every `.en` model (no task token) and for
+`whisper-large-v3-turbo` — OpenAI's model card says turbo was fine-tuned on transcription data only
+and is not trained for translation, so its "translate" output is unreliable. Any future turbo-based
+fine-tune defaults to false until tested. `TranscriptionOptions` renders the Task control only where
+true (language stays). **Stale task:** the `task` state is kept, but `taskForModel(modelId, task)`
+maps "translate" to "transcribe" for a model that can't translate; App applies it on model switch
+(picker and the server-engine auto-switch to turbo) and again when building every file / live run's
+options, so a leftover "translate" can never reach the worker or the server. **Not changed:** the
+server's `parseLanguageAndTask` (D-032) still accepts "translate" for any model — the browser never
+sends it for turbo now, and a direct API caller asking faster-whisper to translate with turbo gets
+what faster-whisper does; rejecting it server-side would be a behaviour change for API users with no
+UI benefit. Speech in another language than English can still end up in English (or Danish) through
+text translation of the finished transcript (D-WS4b), for every model.