+ jHj- a0t$Rt^RIHt^RIt^RIt^RIt^RIt^RIH t H t H t H t ^RI Ht^RI Ht]P$!]4tR5RR/RR llltR tRsR ]R &R RltR6RRlltRtR6RR/RRllltRRltRRltRRltRRR3R R!] 3R"R#R$3R%R&]PB3/t"R']R(&R)R*lt#R+RR,R/R-R.llt$R/R0lt%R1R2lt&R3R4lt'R#)7zCross-adapter helpers shared by gateway/platforms/* and plugins/platforms/*. Kept dependency-light (stdlib + ``agent.secret_scope``) so every adapter can import it at module top level without cycles. ) annotationsN)AnyCallableIterableOptional)UnscopedSecretError) get_secretexternal_fallbackFc(V^8dQhRRRRRRRR/#)namestrdefaultrr boolreturn)formats">/home/ubuntu/.hermes/hermes-agent/gateway/platforms/_shared.py __annotate__rs)//C/#/D/]`/c\VR4pVf.V'd&\ 4f\ 4P V4pVeV#T# \d\P!T4pL\i;i)aScope-aware credential read with the default-profile startup fallback. An installed profile secret scope is authoritative: a scoped miss returns ``default`` (never borrow another profile's value from ``os.environ``). The DEFAULT profile constructs and sends *unscoped* under multiplexing, where a bare ``get_secret`` raises ``UnscopedSecretError``; there ``os.environ`` is that profile's own value, so fall back to it. ``external_fallback`` adds one rung for startup gates that run before any scope exists: an unscoped miss consults a one-shot build of the profile's own secret scope, so externally managed credentials (Bitwarden etc., only ``BWS_ACCESS_TOKEN`` in ``.env``) are visible to ``check_requirements``. N)_scoped_get_secret_UnscopedSecretErrorosgetenv_current_scope_unscoped_profile_secretsget)r rr vals&&$ rget_scoped_secretrse t, {(^-=-E')--d3/3.w. iios A!A+*A+c^RIHpV!4#)current_secret_scope)agent.secret_scoper#r"s rrr-s7  !!rOptional[dict]_UNSCOPED_PROFILE_SECRETScV^8dQhRR/#)r rdictr)rs"rrr5s % %4 %rc\f*^RIHp^RIHp\ V!V!444s\#\# \ d"\PRRR7/s\#i;i)z\Process-cached profile secret mapping (external resolvers are slow); failures degrade to {}.)build_profile_secret_scope)get_hermes_homezyCould not build the profile secret scope; externally managed credentials will not be visible to the startup gate (#95216)T)exc_info) r&r$r*hermes_constantsr+r( Exceptionloggerwarning)r*r+s rrr5sp!( + E 8(,-GHY-Z([ % %$ $$  + NN7AE  G)+ % $$  +s"8$A$#A$c$V^8dQhRRRRRR/#)r r r rrr)rs"rrrEs!00C0#0s0rcV'gV#\P!\4;_uu_4^RIHpHpV!4pVeHV!4'd;VP V4pVfTM\V4P4uuRRR4#RRR4\P!V4;'gTP4# +'giL>;i)uAllow/deny gate env read with per-profile isolation, always stripped. With a profile secret scope installed AND multiplexing active, a scoped miss returns ``default`` instead of falling through to ``os.environ``, which may hold ANOTHER profile's first-writer bridged value (the YAML→env bridges are first-writer-wins; allowlist leak, #72348). Single-profile deployments behave exactly like ``os.getenv``. r#is_multiplex_activeN) contextlibsuppressr.r$r#r5rr striprr)r rr#r5scopers&& rplatform_gate_envr:Es    Y ' 'P$&  !4!6!6))D/C!k7s3x~~/? ( ' ' IIdO & &w - - // ( 's B>/B>> C c\V\4'dLVP4R,R8Xd0\P!V4p\T\ 4'dT#V# \ dTu#i;i)a2Decode a JSON-encoded allowlist written by ``hermes config set``. String-typed defaults keep list literals verbatim on write (``allowed_chats`` is declared as ``""``), so the config can hold ``'["-100","-200"]'`` as a string. Malformed JSON passes through unchanged and keeps the legacy comma-split path. :NN[) isinstancer lstripjsonloads ValueErrorlist)rawloadeds& rdecode_json_list_literalrFYsd#s R 0C 7 ZZ_F fd # #M J  J sA$$ A43A4blank_is_unsetTc 0V^8dQhRRRRRRRRRR R R/#) r extrar%keyr envrrrGrrr)rs"rrrjs8>#'+7:rc"V'd2\VR4pVe"\V4P4'dV#T;'g/PV4pVe5V'd/\ V\4'dVP4'gV#V#)uThe ONE per-profile setting reader: explicit env ``env`` → the profile's YAML ``config.extra[key]`` → ``default``. The env rung is the owning profile's, read through ``get_scoped_secret``: a secondary multiplex profile sees its own ``.env`` and a miss falls to ITS YAML, never to the launch process's ``os.environ`` (which holds the default profile's bridged values); single-profile and default-profile installs read ``os.environ`` there, keeping the documented env-over-YAML contract (an explicit ``DISCORD_ALLOW_MENTION_EVERYONE=false`` beats ``everyone: true``, #108440; ``TELEGRAM_REACTIONS=true`` beats the stock ``reactions: false``, #109032). A blank env value is unset. An explicit ``False``/``0`` in YAML is a real value (``require_mention: false`` must not fall to ``default``). A blank YAML string is unset by default; readers whose YAML key means "clear it" (``allowed_channels: "" `` = no whitelist) pass ``blank_is_unset=False`` so only a missing/``None`` key falls through. N)rr r8rr>)rIrJrKrrG env_valuevalues&&&&$ rextra_or_secretrOjsn  %c40  S^%9%9%;%;  [[b  c "E }Juc,B,B5;;== LrcV^8dQhRR/#)r rrr)rs"rrrs   rcz^RIHpHp\V!4;'d V!4RJ4# \dR#i;i)a[True when running inside a multiplexed secondary profile's scope. Secondary-profile adapters are constructed/connected inside ``_profile_runtime_scope`` (secret scope installed + multiplex active). The DEFAULT profile under multiplexing runs unscoped and keeps the legacy ``os.environ`` precedence, so YAML->env bridges must skip only when True. r4NF)r$r#r5rr.r4s rprofile_scopedrRs<P')PP.B.DD.PQQ s+ + ::cV^8dQhRR/#)r rzCallable[[str, Any], None]r)rs"rrrs3rc.a\4oRV3RllpV#)uV``set_env(name, value)`` for ``apply_yaml_config_fn`` hooks: writes ``os.environ[name]`` only when the var is unset (explicit env wins over YAML) and NEVER while a multiplexed secondary profile's scope is active — the gateway loads every secondary's config inside ``_profile_runtime_scope``, so a write there would pin that profile's policy process-wide and the default profile's adapters would read it as their own (first-writer-wins poisoning, #80099). Hooks seed the same values into the returned ``extra`` so each profile's adapter reads its own. Lists are comma-joined; ``None`` is skipped. c$V^8dQhRRRRRR/#)r r r rNrrNoner)rs"rr%yaml_env_setter..__annotate__s&ffcf#f$frc<Ve%S'g\P!V4'dR#\V\4'dRP RV44M \ V4\P V&R#)N,c38"TFp\V4xK R#5iN)r ).0vs& r 3yaml_env_setter..set_env..s#:EqCFFEs)rrr>rCjoinr environ)r rNskips&&rset_env yaml_env_setter..set_envsL =DBIIdOO >HPT>U>U388#:E#::[^_d[e 4r)rR)rcrbs @ryaml_env_setterres   Dff Nrc V^8dQhRRRR/#)r messagerrr(r)rs"rrrs    rc0^RIHpV!\V44#)zStandalone-sender failure envelope with vendor exception text redacted (the same helper ``send_message`` uses), so a token or signed URL in an httpx/aiohttp error never reaches the model transcript.)_error)tools.send_message_sendersrir )rgris& r send_errorrks2 #g, rlowerc W9#r[rcfgrJs&&rrpsszrc4\V4P4#r[)r rlr]s&rrprpsSV\\^rr c*VPV4R9#)N)Nr1rrns&&rrprpsSWWS\;rcsvc(VPV4RJ#r[rtrns&&rrprpsSWWS\5rcV#r[rrrs&rrprpsrr@c W9#r[rrns&&rrprpscjrzCdict[str, tuple[Callable[[dict, str], bool], Callable[[Any], Any]]] _YAML_KINDSc$V^8dQhRRRRRR/#)r ror(speczIterable[tuple[str, str, str]]rz dict | Noner)rs"rrrs"  4 'E + rc\4p/pVFCwrEp\V,wrxV!W4'gK%W,W4&V!WX!W,44KE T;'gR#)aTable-driven ``apply_yaml_config_fn`` body: for each ``(yaml_key, ENV_VAR, kind)`` row seed the original YAML value into the returned ``extra`` and bridge it to env through ``yaml_env_setter`` (env wins; skipped under a secondary profile's scope). ``None`` when nothing matched. N)rery) ror{rcseededrJrKkindappliesencodes && rapply_yaml_bridgers^ GF$%d+ 3  (FK C) *  >>Trhome_env home_defaultc(V^8dQhRRRRRRRR/#) r r{z6Iterable[tuple[str, str, Callable[[str], Any] | None]]rz str | Nonerr rr(r)rs"rrrs,T",CFPTrc/pVF|wrEp\\VR4;'gR4P4pV'gK=\P!\ 4;_uu_4V'd V!V4MTW5&RRR4K~ V'dV\\VR4;'gR4P4;'gTpV'dRVR\V R2R4/VR&V# +'giK;i)uTable-driven ``env_enablement_fn`` body: for each ``(ENV_VAR, extra_key, conv)`` row read the profile-scoped value, skip it when blank or when ``conv`` raises ``ValueError``, else seed ``conv(value)`` (``None`` conv keeps the stripped string). ``home_env`` seeds ``home_channel`` as ``{"chat_id", "name"}`` from ```` (else ``home_default``) with ``_NAME`` naming it — the core hook lifts that dict into a ``HomeChannel``. The name falls back to the literal ``"Home"``, the same rule the built-in platforms use. r1Nchat_idr _NAMEHome home_channel)r rr8r6r7rB) r{rrseedrKrJconvrDhomes &$$ rseed_extra_from_envrsD$#C,22399;    , ,%)S sDI- ,  $Xr288b9??AQQ\ $-tV=NRZQ[[`Oaci=j#kD K - , ,s $C$$ C5 c V^8dQhRRRR/#)r namesr rCallable[[Any], bool]r)rs"rrrs  S %: rcaRV3RllpV#)z``is_connected`` for platforms whose only configuration is env: True when every ``names`` var is non-blank. Resolves ``hermes_cli.gateway.get_env_value`` at call time (scope-aware, .env-backed) so setup-status tests that patch it see the same value.c V^8dQhRRRR/#r configrrrr)rs"rr&env_is_connected..__annotate__sVVSVTVrc<a^RIHo\;QJdV3RlS4F 'dK R# R#!V3RlS44#)r!Nc3v<"TF.pSPV4;'gRP4xK0 R#5i)r1N) get_env_valuer8)r\r gateway_mods& rr^9env_is_connected..is_connected..s0UutK--d399r@@BBus99FT)hermes_cli.gatewaygatewayall)rrrs&@r is_connected&env_is_connected..is_connecteds/0sUuUssUsUsUuUUUrr)rrsj renv_is_connectedrs VV rc V^8dQhRRRR/#)r keysr rrr)rs"rrrs#*?rcaRV3RllpV#)z``PlatformEntry.config_connected_fn``: connected when the merged PlatformConfig carries a token/api_key or every ``extra`` key (no env fallback; that is ``is_connected``'s job).c V^8dQhRRRR/#rr)rs"rr,config_connected_extra..__annotate__s^^^^rc<a\SP;'g SP4;'g;\;QJdV3RlS4F 'dK R# R#!V3RlS44#)c3Z<"TF pSPPV4xK" R#5ir[)rIr)r\krs& rr^Cconfig_connected_extra..config_connected..s&:]X\ST6<<;K;KA;N;NX\s(+FT)rtokenapi_keyr)rrsfrconfig_connected0config_connected_extra..config_connectedsKFLL22FNN3]]ss:]X\:]ss]s]s:]X\:]7]]rr)rrsj rconfig_connected_extrars^^ rc$V^8dQhRRRRRR/#)r rNrrintrr)rs"rrrs!sSSrcV\V4# \\\3dTu#i;i)zU``int(value)`` or ``default`` when unparseable (incl. non-finite YAML like ``.inf``).)r TypeErrorrB OverflowError)rNrs&&r coerce_portrs,5z z= 1s ((r[)r1)(__conditional_annotations____doc__ __future__rr6r@loggingrtypingrrrrr$rrrr getLogger__name__r/rrr&__annotations__rr:rFrOrRrerkr dumpsryrrrrr)rs@rrs #  44K?   8 $/SX//." -1>0 % 0(".24 &&  )+C D ;S A 5{ C ($** 5 T P &/3IK2 r