docs(frank-tts): the harness sends a voice only in voice_id

The section this PR adds claimed speech.voice was the forwarded voice key. It is not: the openai-speech transport builds {model, input, response_format, voice?} and sets voice only when the CALL passed voice_id, tts.localVoice is the local Kokoro backend key, and speech.voice is the TUI speak-aloud voice whose enum is Kokoro-only. A restarted session proved it the honest way - the tts device arrived at 7772 with no voice key and got "unknown voice None; available voices: narrator1, narrator2, narrator3" - so the fresh-process success earlier that day was the run that was told to pass voice_id, not evidence of a setting.

The law now reads: voice comes from voice_id alone, so a voice-less call is the harness default shape (the endpoint grew DEFAULT_VOICE in its own PR to answer it), and speech.voice must stay a Kokoro name - a pack name there breaks the vocalizer and does nothing for synthesis. config.yml reverted to am_fenrir on the operator box, and the worklog entry that recorded narrator1 as wiring carries the correction.

serverAppConfigs-docs/Dankclaw/Frank TTS.md

@@ -154,17 +154,24 @@ The operator harness reaches this endpoint through
 `baseUrl: http://192.168.0.143:7772/v1`, `auth: none`, and the runner api
 `openai-speech` on the **model** row (naming a runner api at *provider* level
 fails the whole file's validation and disables every custom provider, which is
-how the fleet's chat endpoints disappear) — plus `config.yml`:
-`modelRoles.speech: frank-tts (dankclaw)/frank-tts` and `speech.voice:
-narrator1`. Three laws, read out of the harness bundle and measured the day of
-the flip:
+how the fleet's chat endpoints disappear) — plus `config.yml`
+`modelRoles.speech: frank-tts (dankclaw)/frank-tts`. Four laws, read out of the
+harness bundle and measured the day of the flip:
 
-- **The forwarded voice key is `speech.voice`, not `tts.localVoice`.** The
-  latter belongs to the local Kokoro backend and still carries `bm_george`; it
-  is what answered when the role pointed at `local/kokoro`. `speech.voice`
-  becomes the request's `voice`, and this endpoint treats an unknown name as an
-  error rather than a default — so a Kokoro-style revert has to move **both**
-  keys together.
+- **The only voice the harness can send is the `voice_id` argument of the call.**
+  The transport builds `{model, input, response_format, voice?}` and adds `voice`
+  **only** when the caller passed `voice_id`; no setting feeds it.
+  `tts.localVoice` is the *local Kokoro backend's* voice (it is what answered
+  `voice=kokoro/bm_george, backend=local` in the control test), and
+  `speech.voice` is the TUI's **speak-aloud** voice — its enum is Kokoro's list,
+  and it never reaches an HTTP request. So a harness call arrives voice-less by
+  default, which is exactly why the endpoint grew `DEFAULT_VOICE`: the declared
+  pack answers a voice-less request and the journal marks that line `(default)`,
+  while an **unknown** name still 400s with the list that exists.
+- **`speech.voice` must stay a Kokoro name.** Setting it to a pack name does not
+  select a pack; it hands the vocalizer a value outside its enum. (The first
+  draft of this section said the opposite and was reverted the same day, after a
+  fresh session's call came back `unknown voice None`.)
 - **There is no silent fallback.** An explicitly configured `modelRoles.speech`
   yields exactly one candidate, so a dead 7772 fails the speech device with
   *"No available speech model matches the speech role"* instead of quietly