catalog: promote chatterbox-fast to ready; vibevoice->down; resolve voxtral 8197 collision

- chatterbox-fast experimental -> ready: browser audition verified end-to-end
  (operator confirmed progressive playback "excellent" 2026-06-02).
- vibevoice ready -> down: no container running on irv-ml1 (connection refused);
  catalog status was stale.
- voxtral: NOT a stale typo — its stack genuinely claimed :8197, the port now held
  by the live chatterbox-fast. voxtral is down, so moved IT to :8201 (catalog
  endpoint + source_url, stacks/voxtral/.env.example + README, host .env) rather
  than disturb the live service. No live clash existed (voxtral down) but it was a
  latent deploy-time collision I introduced by placing chatterbox-fast on 8197.

No catalog_version bump (status changes + endpoint correction, additive). Validates
against the schema.
This commit is contained in:
vh
2026-06-02 09:10:57 -07:00
parent fa56718ba0
commit 099e1d7418
3 changed files with 14 additions and 11 deletions
+3 -1
View File
@@ -15,7 +15,9 @@ VOXTRAL_MODEL=mistralai/Voxtral-4B-TTS-2603
# ── network ──────────────────────────────────────────────────────────
# Host port (container listens on 8000 internally).
VOXTRAL_PORT=8197
# Was 8197 — moved to 8201 (2026-06-02): 8197 is taken by the live
# chatterbox-fast stack. Don't reuse 8197.
VOXTRAL_PORT=8201
VOXTRAL_BIND=0.0.0.0
# ── runtime / GPU ────────────────────────────────────────────────────