Files

T

RainbowBird 615e0441e8 refactor(server): proxy TTS through unspeech, drop implicit fallbacks

Frontend voice picker silently lost Azure voices because /audio/voices
was called without ?model=, so the server fell back to DEFAULT_TTS_MODEL
and only ever returned one model's catalog. /audio/models also hardcoded
a single `auto` alias, so the client could never request a specific
model id even if it wanted to. On top of that, the Azure adapter shipped
only 2 hand-typed voices in voices/azure.json — the rest of Microsoft's
catalog was unreachable.

Fixed in one pass:

- Drop voices/*.json. Every getVoiceCatalog now calls unspeech REST
  (backend=microsoft|alibaba|volcengine). Azure proxies Microsoft's live
  voices/list; cosyvoice + volcengine use unspeech's embedded catalogs.
- Drop direct upstream provider calls from send(). All three adapters
  POST to <UNSPEECH_REST_BASE_URL>/v1/audio/speech with the openai-shaped
  body unspeech expects (model: `<backend>/<id>`). Azure SSML still built
  on our side so <prosody rate> speed survives — unspeech accepts
  pre-built <speak> documents.
- Fail-fast on every voices endpoint: empty ?model= → 400 MISSING_MODEL
  (no implicit DEFAULT_TTS_MODEL fallback), only `auto` resolves;
  streaming upstream missing → 503; unspeech non-2xx / network err → 502;
  malformed body → 502 with grepable message. No silent `{voices: []}`.
- /audio/models lists every LLM_ROUTER_CONFIG.tts.models key + `auto`.
- Frontend providerOfficialSpeech.listVoices passes ?model= and throws
  on upstream failure instead of returning [].
- New UNSPEECH_REST_BASE_URL configKV entry (no default, missing → 503).
  config-sync subscriber invalidates the voice cache when this key OR
  LLM_ROUTER_CONFIG changes.
- Router voice catalog Redis cache covers all providers with per-provider
  TTL (azure 6h live, alibaba/volcengine 24h since unspeech embeds them
  at build time).

Pending billing-SKU verification: DashScope cosyvoice now goes through
unspeech's WS-internal alibaba backend (was REST `/SpeechSynthesizer`).
Functional output equivalent — confirm bill after deploy, revert via
git history if WS pricing is materially higher.

2026-05-19 23:14:16 +08:00

public

docs(stage-ui): updated logo

2026-03-12 05:09:32 +08:00

src

refactor(server): proxy TTS through unspeech, drop implicit fallbacks

2026-05-19 23:14:16 +08:00

stories

fix(stage-ui,ui): histoire wasn't configured correctly

2026-04-22 16:57:35 +08:00

.env

feat(stage-*): experimental realtime transcription powered by Aliyun NLS

2025-11-02 04:20:27 +08:00

env.d.ts

…

histoire.config.ts

fix(stage-ui): configure Histoire to exclude node_modules from vendor chunking

2026-04-25 16:46:08 +08:00

package.json

feat(stage-ui-spine): add Spine 2D runtime integration (#1810 )

2026-05-19 19:13:35 +08:00

README.md

chore: lint & lock

2026-03-06 16:49:31 +08:00

tsconfig.json

chore(ci): fix typecheck on navigator.gpu (#1700 )

2026-04-21 20:27:17 +08:00

uno.config.ts

…

vite.config.ts

refactor(stage-web,stage-ui): replace warpdrive plugin with unplugin-basemove (#1818 )

2026-05-13 12:03:30 +08:00

vitest.config.ts

test: migrate more test into browser mode, fix all existing tests

2026-05-07 18:48:39 +08:00

README.md

Stage UI

Shared core for stage

Histoire (UI storyboard)

https://histoire.dev/

pnpm -F @proj-airi/stage-ui run story:dev

Project structure

If a story is bound to a specific component, it can be placed beside the component in the src folder. e.g., MyComponent.story.vue
If a story is not bound to a specific component, then it should be placed in the stories folder. e.g., MyStory.story.vue