3 Commits

Include renames

Author	SHA1	Message	Date
viettranx	613b6e38d7	feat(tts): provider capabilities schema + Gemini TTS + dynamic param forms ... Baseline groundwork for TTS expansion plan. Introduces a capabilities system that the follow-up plan (phase-01..04) builds on. Backend: - `audio.ParamSchema` / `ProviderCapabilities` types + per-provider capabilities.go for edge, elevenlabs, minimax, openai, gemini. - Gemini TTS provider (client, models, voices, wav encoder, multi-speaker via SpeakerVoice, audio-tag aware prompts). - TTSOptions gains `Params map[string]any` (read-only) + `Speakers`. - `VoiceListProvider` interface decouples HTTP voice handler from provider-specific impls. - `nested_keys.go` resolves dot-separated param paths for nested provider bodies (voice_settings.stability etc.). - Characterization + defaults-invariant tests per provider lock nil-params byte-equivalence before new params land. - `/v1/tts/capabilities` HTTP endpoint + integration coverage. - Dual-read tests (PG + SQLite) for tts_config. Frontend (web + desktop): - `DynamicParamForm` with depends-on evaluation, split into fields/logic modules. Slider primitive added. - `AudioTagPicker` + `MultiSpeakerEditor` for Gemini. - `voice-picker` refactored toward portal UX; combobox tightened. - tts-capabilities API client + typed hooks. - i18n catalogs (en/vi/zh) expanded; parity tests guard key drift. - TTS page reorganised (voice-model-section removed; playground + credentials + provider-setup split cleanly). Docs: codebase-summary, project-changelog, tts-provider-capabilities.	2026-04-20 00:05:19 +07:00
Junghwanandviettranx	f729b2d618	Prevent TTS test-connection from bypassing provider URL guards (#937) ... The repo already validates provider base URLs during provider CRUD, but TTS test-connection built ephemeral providers from user-supplied api_base without reusing that protection. This change applies the same validation at test time and adds regression coverage for blocked loopback targets. Constraint: Must preserve current local-provider SSRF policy semantics from provider validation Rejected: Restrict test-connection to admins only | larger behavior change than needed for the bug Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep TTS test-connection URL validation aligned with validateProviderURL behavior for provider CRUD Tested: go test ./internal/http -run 'TestTestConnection_(MissingProvider|UnsupportedProvider|MissingAPIKey|BelowOperator|BlockedAPIBase)$' -count=1 -v Tested: go build ./... Tested: go build -tags sqliteonly ./... Not-tested: Full repo race test suite Co-authored-by: viettranx <viettranx@gmail.com>	2026-04-17 20:15:44 +07:00
viettranx	34172d2767	feat(tts): add test-connection endpoint, hot-reload support, and Telegram voice messages ... - Add POST /v1/tts/test-connection for testing TTS credentials before saving - Add UpdateManager() with RWMutex for thread-safe HTTP handler hot-reload - Add sendVoice() for Telegram voice bubble support via audio_as_voice metadata - Wire ttsHandler into gateway deps for config reload propagation	2026-04-16 17:22:56 +07:00