fc-ttsreader: route Whisper alignment at openai-compatible backend

The fc-speech-align container on BLUEJAY-WS (port 9200) is the speaches
build of faster-whisper-server, which exposes the OpenAI-compatible
/v1/audio/transcriptions contract — not the FlowerCore /align contract.

FasterWhisperAlignmentClient (FlowerCore.Common a1b3bfc) supports both
shapes; tell it explicitly to talk OpenAI-compatible here so requests land
on the right endpoint and verbose_json gets adapted into the FC alignment
response. Also pin the Model id to one speaches recognizes.

Switch back to fc-align once a native /align backend is deployed (or wire
a tiny FastAPI shim in front of speaches if we want a stable contract).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

apps/fc-ttsreader/fc-ttsreader.yaml

@@ -174,8 +174,17 @@ spec:
               value: "120"
             - name: Speech__Alignment__Enabled
               value: "true"
+            - name: Speech__Alignment__Backend
+              # speaches container on BLUEJAY-WS speaks the OpenAI-compatible
+              # /v1/audio/transcriptions contract; FasterWhisperAlignmentClient
+              # adapts the verbose_json response into the FlowerCore shape.
+              # Switch to "fc-align" once a native /align backend is deployed.
+              value: "openai-compatible"
             - name: Speech__Alignment__BaseUrl
               value: "http://10.0.56.20:9200"
+            - name: Speech__Alignment__Model
+              # Tag understood by speaches (faster-whisper-server).
+              value: "Systran/faster-whisper-base.en"
             - name: Speech__Alignment__TimeoutSeconds
               value: "120"
             - name: TtsReader__Ollama__BaseUrl