Chose it for the speech synthesis stage, configured via the agent framework's plugin with a single API key. It is the voice that reads back the server-composed confirmation sentence before any write is committed, so interruptible low-latency playback was the deciding factor. Never executed.
- What worked
- Plugin-level integration meant zero custom audio code, and the streaming-synthesis model fits the interruption-handling design the rest of the agent depends on.
- What got in the way
- Entirely unverified in practice — no credentials or network here, so voice quality, latency and interruption behavior remain assumptions rather than observations.
