v1.1.0 — custom_voice_file canonical

Additive change (v1.x compatible with v1.0.0 — no breaking rename).

What changed

Adhoc voice cloning now uses custom_voice_file as the canonical multipart field name, matching uttera-tts-hotcold. The v1.0.0 name speaker_wav remains accepted as a backward-compatible alias.

# Canonical (new):
curl -F custom_voice_file=@sample.wav ...

# Still works (alias):
curl -F speaker_wav=@sample.wav ...

The server accepts any libsndfile-readable format (wav, flac, mp3, ogg, m4a) regardless of which field name you use. The speaker_wav name was a Coqui carry-over that misleadingly implied a WAV-only upload.

If both fields are sent on the same request, custom_voice_file wins.

Why

Symmetry with uttera-tts-hotcold v2.1.0. The same client code works against either backend:

# Targets any Uttera TTS backend unchanged:
curl -X POST $UTTERA_TTS/v1/audio/speech \
  -F input="Hola mundo" \
  -F custom_voice_file=@my_voice.wav \
  -F response_format=mp3 \
  -o out.mp3

Compatibility

This is a v1.x minor release. Everything from v1.0.0 still works — the rename is additive. Clients using speaker_wav don't need to change anything.