߲j[UdZddlZddlmZmZddlmZddedeedefdZdded eedefd Z d e deefd Z d Z e e e dZ eeeefed<deedeefdZy)z>Endpoint identity for auxiliary custom-provider health checks.N)AnyOptional)normalize_route_base_urlproviderbase_urlreturncxddlm}ddlm}||}t t ||}|}|r|d|fS||fS)uProvider-wide key, or endpoint-specific key for an explicit custom endpoint — prefixed with the active profile home: a 402 on profile A's account must not hide the provider from profile B's (differently funded) account in the same multiplexed process.r_normalize_chain_label)hermes_home_keyzcustom-endpoint)agent.auxiliary_clientr hermes_constantsr r_custom_health_base_url)rrr r labelendpointhome_keys ;/home/ubuntu/.hermes/hermes-agent/agent/auxiliary_health.py_unhealthy_cache_keyrsI>0 "8 ,E'(?((STH H*H44 U?explicit_base_urlcddlm}t|xsdj}ddlm}||}|dk(r |xs|S|j dr|r|St jt5ddl m }m }||r|xs|cdddS||}|r9|xs,t|jd xsdjcdddS dddy#1swYyxYw) zQReturn the concrete custom endpoint used to scope health and failed-route checks.r)_current_custom_base_urlr z local/customzcustom:)_get_named_custom_provider_resolves_to_customNr) r rstrstripr startswith contextlibsuppress ImportErrorhermes_cli.runtime_providerrrget) rrrexplicitr rrrentrys rrrs?$*+113H= "8 ,E 5355  "x   [ )H_ u %979HH+84 Gs599Z#8#>B?EEG HH  H H s0C"9C""C+excc:ddlm}tfd|DdS)a+Why a fallback candidate cannot serve this walk (``_FALLBACK_REASONS`` label), or None. The same capacity classes that admitted the primary failure into the chain (payment/quota, rate limit, connection, route-incompatible model, malformed response) mean "this lane is out for now, try the next configured one"; anything else (a 400 request-shape error, a ValueError) is the caller's bug and must still propagate. Auth errors are excluded on purpose: they have their own refresh-then-quarantine path in the candidate helpers (#106367).r)_FALLBACK_REASONSc3FK|]\}}|dk7s |s|yw)z auth errorN).0 predicaterr&s r z8fallback_candidate_unavailable_reason..5s&e#9eE\r<sD > 3 (3- 3 chsmWZ, y Xc] &+/'9?!H94Xe_ 457hsm77r