test(voice): cover tts fallback

This commit is contained in:
William Valentin
2026-02-25 11:21:49 -08:00
parent e3e98058b0
commit eec54ace9d
5 changed files with 84 additions and 1 deletions
+1
View File
@@ -145,6 +145,7 @@ Gateway streaming UX signals:
- Routing applies reaction rules with deterministic priority/cooldown (and recursion guard) before intent routing.
- Companion nodes re-register `node.*` capabilities after reconnect; runtime clients can auto-reconnect and surface connection events.
- Canvas artifacts are persisted by the gateway so session UI surfaces can recover after daemon restarts.
- TTS synthesis failures degrade to text-only replies without dropping the response.
Key files:
@@ -18,6 +18,7 @@ If you only want the protocol surface, see `docs/api/PROTOCOL.md`.
- Reaction matching is deterministic (priority + cooldown + recursion guard) before intent/agent routing.
- Companion `node.*` registration is per WebSocket connection; reconnects must re-register capabilities before invoking node RPC methods.
- Canvas artifacts are persisted per session under the gateway data directory for UI recovery across restarts.
- TTS output is best-effort; synthesis failures fall back to text-only responses.
## Component Map