fix: correct log messages in KokoroTTSProvider from ElevenLabs to Kokoro

[giwaov]

Problem

The KokoroTTSProvider class in src/providers/kokoro_tts_provider.py has incorrect log messages that reference 'Eleven Labs TTS provider' instead of 'Kokoro TTS provider'. This is a copy-paste error from when the class was created based on the ElevenLabsTTSProvider.

Affected Code

Line 211 (start method):

logging.warning("Eleven Labs TTS provider is already running")

Line 222 (stop method):

logging.warning("Eleven Labs TTS provider is not running")

Impact

• Debugging confusion: When developers see 'Eleven Labs TTS provider is already running' in logs but are configuring Kokoro TTS, it creates confusion
• Incorrect diagnostics: Users may troubleshoot the wrong provider based on misleading log messages
• Code maintenance: Future developers may not realize which provider is actually being used

Solution

Changed the log messages to correctly reference 'Kokoro TTS provider':

# Before
logging.warning("Eleven Labs TTS provider is already running")
logging.warning("Eleven Labs TTS provider is not running")

# After
logging.warning("Kokoro TTS provider is already running")
logging.warning("Kokoro TTS provider is not running")

Testing

• Existing tests in tests/providers/test_kokoro_tts_provider.py continue to pass
• Tests verify 'already running' and 'is not running' patterns which are preserved
• No behavioral changes, only log message text corrections

[Copilot]

Pull request overview

This PR fixes misleading lifecycle warning log messages in KokoroTTSProvider so they correctly refer to Kokoro (not Eleven Labs), aligning runtime logs with the configured provider.

Changes:

• Update the start() “already running” warning to reference “Kokoro TTS provider”.
• Update the stop() “not running” warning to reference “Kokoro TTS provider”.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!