docs(lobe-chat): voice surface fully safe — ballad/verse aliased by tts-dev

tts-dev aliased the last two unaliased OpenAI voice names (ballad->emmie,
verse->donut, tts-stack c55bc3c). Verified: the full modern OpenAI voice set
returns 200, only a genuinely-unknown string 404s. A stock Lobe picker can
no longer produce a 404 or trip the router cooldown, so the voice string no
longer needs pinning; still pin mp3 for response size.
This commit is contained in:
2026-08-16 16:54:32 -07:00
parent 25fa18efb8
commit 933253d42e
+7 -4
View File
@@ -67,10 +67,13 @@ Authoritative list (13): `computer`, `computer-soft`, `computer-urgent`, `donut`
`emmie`, `glados`, `miranda`, `sindra`, `sindra-excited`, `sindra-sad`,
`sindra-soft`, `sindra-sultry`, `sindra-whisper`.
**The only live grenades are `ballad` and `verse`** — newer OpenAI additions never
aliased, both confirmed 404. If Lobe exposes the full modern OpenAI voice list those
are the two to avoid; tts-dev has offered to alias them (one-line change on his side)
and infra-ops has taken him up on it.
**Voice surface is now fully safe (tts-dev, 2026-08-16, tts-stack `c55bc3c`).**
`ballad`→emmie and `verse`→donut were the last two unaliased OpenAI names; they are
now aliased and live. Verified: the entire modern OpenAI voice set returns 200, and
only a genuinely-unknown string (`wharrgarbl`) 404s. **A stock Lobe voice picker
cannot produce a 404 from any voice it would plausibly offer, so it cannot trip the
router cooldown.** The env-vs-UI voice question is therefore moot for safety — pin
`mp3` for size, but the voice string itself no longer needs pinning.
### The real constraint is SIZE, not length