`gj-UdZddlmZddlZddlZddlmZmZmZddl m Z eje Z iZded<ej ZddZdd Zdd Zdd Zd Zdd ZdddddZddZddZddZy)u. Web Search Provider Registry ============================ Central map of registered web providers. Populated by plugins at import-time via :meth:`PluginContext.register_web_search_provider`; consumed by the ``web_search`` and ``web_extract`` tool wrappers in :mod:`tools.web_tools` to dispatch each call to the active backend. Active selection ---------------- The active provider is chosen by configuration with this precedence: 1. ``web.search_backend`` / ``web.extract_backend`` (per-capability override). 2. ``web.backend`` (shared fallback). 3. If exactly one capability-eligible provider is registered AND available, use it. 4. Legacy preference order — ``firecrawl`` → ``parallel`` → ``tavily`` → ``exa`` → ``searxng`` → ``brave-free`` → ``ddgs`` — filtered by availability. Matches the historic ``tools.web_tools._get_backend()`` candidate order so installs that never set a config key keep landing on the same provider they did before the plugin migration. 5. Otherwise ``None`` — the tool surfaces a helpful error pointing at ``hermes tools``. The capability filter (``supports_search`` / ``supports_extract``) is applied at every step so a search-only provider (``brave-free``) configured as ``web.extract_backend`` correctly falls through to an extract-capable backend. ) annotationsN)DictListOptional)WebSearchProviderzDict[str, WebSearchProvider] _providersct|ts!tdt|j|j }t|t r|js tdt5tj|}|t|<ddd+tjd|t|jytjd|t|jy#1swYaxYw)uRegister a web search/extract provider. Re-registration (same ``name``) overwrites the previous entry and logs a debug message — makes hot-reload scenarios (tests, dev loops) behave predictably. z>register_provider() expects a WebSearchProvider instance, got z-Web provider .name must be a non-empty stringNz(Web provider '%s' re-registered (was %r)z!Registered web provider '%s' (%s)) isinstancer TypeErrortype__name__namestrstrip ValueError_lockrgetloggerdebug)providerrexistings L/root/.hermes/venv/lib/python3.12/site-packages/agent/web_search_registry.pyregister_providerr0s h 1 2>**+ -   ==D dC  HII $>>$'# 4$ 6 $x.))  / $x.)) $$s /C..C7ct5ttj}dddt dS#1swYxYw)z0Return all registered providers, sorted by name.Nc|jSNr)ps rz list_providers..Rs qvv)key)rlistrvaluessorted)itemss rlist_providersr&Ns; *Z&&()* %- ..**s ;Act|tsyt5tj |j cdddS#1swYyxYw)z5Return the provider registered under *name*, or None.N)r rrrrrrs r get_providerr(Us9 dC  ,~~djjl+,,,s #AAcP ddlm}|}|}|D]%}t|tsy|j |}'t|t r |j r|j Sy#t$r0}tjddj||Yd}~yd}~wwxYw)zGResolve a dotted config key from ``config.yaml``. Returns None on miss.r) load_configNzCould not read config %s: %s.) hermes_cli.configr*r dictrrr Exceptionrrjoin)pathr*cfgcursegmentexcs r_read_config_keyr5bs J1m #Gc4('''"C # c3 CIIK99;   J 3SXXd^SII Js%A,AA,, B%5&B  B%) firecrawlparalleltavilyexasearxngz brave-freeddgsct5tt}ddddfd }dd}|rMj|}| ||r|S|tj d|ntj d|j Dcgc]}||r ||r|}}t|dk(r|dStD]+}|j|}|||s ||s)|cSy#1swYxYwcc}w) uResolve the active provider for a capability ("search" | "extract"). Resolution rules (in order): 1. **Explicit config wins, ignoring availability.** If ``web.{capability}_backend`` or ``web.backend`` names a registered provider that supports *capability*, return it even if its :meth:`is_available` returns False — the dispatcher will surface a precise "X_API_KEY is not set" error to the user instead of silently routing somewhere else. Matches legacy :func:`tools.web_tools._get_backend` behavior for configured names. 2. **Single-provider shortcut.** When only one registered provider supports *capability* AND ``is_available()`` reports True, return it. 3. **Legacy preference walk, filtered by availability.** Walk the :data:`_LEGACY_PREFERENCE` order (firecrawl → parallel → tavily → exa → searxng → brave-free → ddgs) looking for a provider whose ``supports_()`` is True AND whose ``is_available()`` is True. Matches the historic ``tools.web_tools._get_backend()`` candidate order so users with credentials but no explicit config key keep landing on the same provider as pre-migration. This is the path that fires when no config key is set — pick the highest-priority backend the user actually has credentials for. Returns None when no provider is configured AND no available provider matches the legacy preference; the dispatcher then returns a "set up a provider" error to the user. Nc~dk(rt|jSdk(rt|jSy)NsearchextractF)boolsupports_searchsupports_extract)r capabilitys r_capablez_resolve.._capables>  !))+, ,  "**,- -r c t|jS#t$r+}tj d|j |Yd}~yd}~wwxYw)zDWrap ``is_available()`` so a buggy provider doesn't kill resolution.z$provider %s.is_available() raised %sNF)r@ is_availabler.rrr)rr4s r_is_available_safez$_resolve.._is_available_safesA () )  LL? M s A!A  Az_backend`` → ``web.backend``). This is more reliable than the resolved backend the dispatcher fell back to, since a disabled provider fails the ``_is_backend_available`` gate and the dispatcher silently drops to the shared default. An explicit ``configured`` name still wins when given. Matching is by convention: bundled web plugins live under the ``web/`` key with the provider ``name`` differing only in hyphen/underscore (``brave-free`` provider ⇄ ``web/brave_free`` key, ``firecrawl`` ⇄ ``web/firecrawl``). We normalize both sides before comparing so every bundled provider is covered without hardcoding a per-vendor table. c^|jjjddS)N-_)rlowerreplace)ss r_normz'_disabled_web_plugin_for.._norms"wwy ((c22r )r>r?web_backendbackendNr)get_plugin_managerzweb/zdisabled via config/rHz%disabled-web-plugin lookup failed: %s)rXrrIr)r5hermes_cli.pluginsr]_pluginsr%r r startswithenablederrorsplitr.rr) rLrCrYwantr]pmr!loadedvendorr4s r_disabled_web_plugin_forris83 *(== Uzl($; < 2y1    DC9  !;;,,. KCc3's~~f/E~~||44YYsA&q)FV}$    C rQr5rPexplicits rget_active_search_providerros,  '78^rs@#''7   8 $,. (-  </,0Vr8^b8v34r