Summary

Fixes #17140 — TTS provider tools fail to read API keys from ~/.hermes/.env.

Problem

TTS provider tools (elevenlabs, minimax, mistral, xai, gemini) use os.getenv("X_API_KEY") directly, which does not read values stored in ~/.hermes/.env. The hermes config system uses get_env_value() from hermes_cli.config which reads .env directly, but the TTS tools bypass this, causing "API key not set" errors even when keys are correctly configured.

Solution

Replace all os.getenv() calls for API keys and base URLs in tools/tts_tool.py with _get_env_value() (aliased from hermes_cli.config.get_env_value), following the same pattern already used by hermes_cli/auth.py and hermes_cli/gateway.py.

Changes

Added _get_env_value import with fallback (lines 53-59):

try:
    from hermes_cli.config import get_env_value as _get_env_value
except Exception:
    def _get_env_value(key, default=None):
        return os.getenv(key, default)

Replaced all os.getenv() calls for env vars in tts_tool.py:

Safety

• Fallback to os.getenv() if hermes_cli.config is unavailable — no behavior change for existing installations
• get_env_value() checks os.environ first, then .env file — fully backward-compatible
• No new dependencies, no API surface changes

Testing

• Python syntax check passes (py_compile)
• Pattern matches existing usage in hermes_cli/auth.py (line 332) and hermes_cli/gateway.py (lines 2388+)

Closes #17140