* refactor(plugins): remove the Sep 2026 decomposition compat layer on schedule The PLUGIN-COMPAT layer (2776813df3+d63e380324+0a5164cebe) kept pre-#102117 import paths alive for external plugins until 2026-09-14. That window closed two weeks ago; since then the loader has already been skipping plugins that use the old paths. This removes the layer itself: - 328 appended `PLUGIN-COMPAT` blocks (lazy `__getattr__` pointer tables, re-exported third-party names, restored dead definitions) and the three re-export stub modules (gateway/startup_watchdog, hermes_cli/observability/relay_runtime, tools/environments/modal_utils) - COMPAT_MANIFEST.md, compat_manifest.json, scripts/check_compat_pointers.py and its lint step - the reporting surfaces: CLI banner notice, `hermes plugins compat`, the `hermes doctor` section, the post-update notice, the Desktop one-time dialog, the loader's pre-import skip and the `plugins.allow_deprecated_imports` escape hatch An external plugin that still imports an old path now fails to load with its ImportError as the reason in `hermes plugins list`, the same path as any broken plugin. hermes_cli/plugin_compat.py stays as three inert stubs (compat_report, removal_in_effect, summary_lines): an already-running pre-removal `hermes update` lazy-imports them after the checkout swap (tests/compat/old_updater_surface.json). In-tree fallout, both already dead: hermes_cli/setup.py::_check_espeak_ng (no callers; its `shutil` came from a compat block) and gateway/config.py::SessionResetPolicy ("retained solely for the scheduled plugin-compat window"). Two test_run_agent patches targeted the removed `run_agent.handle_function_call` pointer; they now patch `model_tools.handle_function_call`, the seam production reads, like every sibling test in that file. * chore: retrigger CI (zero-job startup_failure phantom) * test: drop resolution allowlist rows for the two deleted which() sites hermes_cli/setup.py::_check_espeak_ng (dead) and tools/skillevaluator_scan.py::scanner_available (a restored definition inside a PLUGIN-COMPAT block) no longer exist; the stale-row gate requires their allowlist entries go with them.
46 lines
1.7 KiB
Python
46 lines
1.7 KiB
Python
"""TTS Provider Registry.
|
|
|
|
Registered plugin TTS providers, populated at import-time via
|
|
:meth:`PluginContext.register_tts_provider` and consulted by :mod:`tools.tts_tool`
|
|
only when ``tts.provider`` is neither a built-in nor a command-type provider.
|
|
Built-ins always win: a colliding plugin name is rejected here with a warning
|
|
(re-checked at dispatch). Command-providers-win-over-plugins is enforced by the
|
|
dispatcher (a name in the user's config.yaml is more specific than a plugin).
|
|
"""
|
|
|
|
from __future__ import annotations
|
|
|
|
import logging
|
|
|
|
from agent.provider_registry import ProviderRegistry, lower_key
|
|
from agent.tts_provider import TTSProvider
|
|
|
|
logger = logging.getLogger(__name__)
|
|
|
|
|
|
# Names reserved for native built-in TTS handlers. **Kept in sync with
|
|
# ``BUILTIN_TTS_PROVIDERS`` in :mod:`tools.tts_tool`** (``TestBuiltinSync`` in
|
|
# ``tests/agent/test_tts_registry.py`` fails on drift); importing it directly
|
|
# would be a circular import.
|
|
_BUILTIN_NAMES = frozenset({
|
|
"edge", "elevenlabs", "openai", "minimax", "xai", "mistral", "gemini", "neutts", "kittentts",
|
|
"piper", "deepinfra",
|
|
})
|
|
|
|
|
|
def _warn_builtin_collision(key: str) -> None:
|
|
logger.warning(
|
|
"TTS provider '%s' shadows a built-in name; registration ignored. "
|
|
"Built-in TTS providers (%s) always win — pick a different name.",
|
|
key, ", ".join(sorted(_BUILTIN_NAMES)),
|
|
)
|
|
|
|
|
|
# Case-insensitive, whitespace-tolerant keys mirror how
|
|
# ``tools.tts_tool._get_provider`` normalizes the configured ``tts.provider``.
|
|
_registry: ProviderRegistry[TTSProvider] = ProviderRegistry(
|
|
label="TTS", provider_cls=TTSProvider, logger=logger, normalize=lower_key,
|
|
builtin_names=_BUILTIN_NAMES, on_builtin_collision=_warn_builtin_collision,
|
|
)
|
|
_registry.export(globals())
|