+ jHja0t$Rt^RIHt^RIt^RIt^RIt^RIHt^RI H t ^RI H t H t ^RIHtHtHtHtHtHtHt]P,!]4tRR/tR R ltR R ltR R/RRlltRR/RRlltRR/RRlltRRltRR/RRllt RR/RRllt!RR/RRllt"]!RR 7!R!R"44t#]#!R#R$]R%RvRwRxRyR#RvRzR&7 ]#!R'R(]R)R'R*7]#!R+R,] R-R{R|R.R/7]#!R0R1R2R3R0R4R57]#!R6R7]!R8R6R97]#!R:R;]"R73t$R?]%R@&RARBlt&RCRDlt'RERFlt(RGRHlt)RIRJlt*R~RKRLllt+RMRNlt,]-!4t.RO]%RP&/t/RQ]%RR&RSRTlt0RURVlt1RWt2RXt3RYRZlt4R[R\lt5R]R^lt6R_R`lt7RRRaR/RbRcllt8RdR/ReRfllt9RgRhlt:RiRjlt;Rk]RpRqlt?RkR/RrRsllt@RtRultAR#)a]Move a home onto the catalog plugin of a feature that left core. A feature (gateway platform, toolset, bundled plugin) that moves from core into a standalone catalog plugin keeps its names, config keys and env vars, so migrating is only "install the plugin". Each row of :data:`LEFT_CORE` names the catalog plugin and a read-only predicate "does this home use it". The contract is the one memory providers established (``memory_provider_migration``, whose helpers this reuses; memory is not a row because its plugin name comes from ``memory.provider``, not a table): * ``hermes update`` installs the plugin for every profile home sharing the venv that uses the feature. * Agent start and gateway start retry once per process for the active home (Desktop users update through the app and never run ``hermes update``), honouring ``security.allow_lazy_installs``. * After a failed attempt (catalog miss or unreachable, failed install) starts skip the row for an hour, doubling with each further failure up to a week, so an offline machine pays the network round trip once, not on every ``hermes chat``, and a home whose install cannot succeed stops failing every hour; ``hermes update`` always retries. * A home gets the plugin automatically at most once (``_left_core_installed`` in its config.yaml): ``hermes plugins remove`` afterwards is the user's choice and sticks. Installs go through the normal catalog install path at the reviewed pin (kill list, dependency constraints, enable). Unattended dependency consent covers only these rows: the feature shipped in core, so its users already accepted its dependencies. Agent/gateway start always installs with it (nothing can answer a prompt there); ``hermes update`` in a terminal still asks. Every outcome reaches the user (terminal, Desktop, chat); a gateway-start outcome waits for the home's first agent to deliver it. ) annotationsN) dataclass)Path)CallableOptional)_failed_recently _home_consent _home_label_install_command _interactive _note_failure_unattended_consentzterminal.singularity_imageTERMINAL_SINGULARITY_IMAGEc V^8dQhRRRR/#)homerreturndict)formats"C/home/ubuntu/.hermes/hermes-agent/hermes_cli/left_core_migration.py __annotate__r2s22t22c^RIpVPVR, PRR74p\ T\ 4'dT#/# \d/u#i;i)N config.yaml utf-8-sigencoding)utilsfast_safe_load read_text Exception isinstancer)rrdatas& r _read_configr%2s\##TM%9$D$Dk$D$Z[dD))41r1  s(A AAc$V^8dQhRRRRRR/#)rrrnamestrrboolr)rs"rrr;s&dddSdTdrcf^RIHp^RIHpVP V4p\ V\ 4'dTM/pVPV4p\ V\ 4'dTM/pVPWUPR4V\V04R7PV4p\ V\ 4'gR#VPV4pVP;'gDRV9;'d7\\VP ;'gR4P#44# \d/pLi;i)aPlatform *name* is on in *home*'s config files as the gateway loader reads them: legacy ``gateway.json`` base layer, then config.yaml's ``gateway.platforms`` / ``platforms`` / ``gateway.`` blocks merged in the loader's order (managed overlay and ``${VAR}`` applied), so the last explicit ``enabled`` wins. A stored token with no ``enabled`` anywhere counts too. Env credentials are the caller's to check. Read-only; works before the platform's plugin loads. config_loader)PlatformConfiggateway)alsoFenabled)r.r,gateway.configr-load_legacy_gateway_jsonr#rread_yaml_layersr"merge_platform_sectionsget frozenset from_dictr0r)r(tokenstrip)rr'r,r-gw_datayaml_cfgblockplatforms&& rplatform_configured_onr?;s &-44T:G#GT22gG 11$7&h55x2H  1 1,,y)7D69J 2 LLOCPTI eT " "''.H    c c  6 b b4HNNDXDXVX@Y@_@_@a;bc sD D0/D0 own_platformr1c(V^8dQhRRRRRRRR/#) rconfigrnameszfrozenset[str]r@r(rr)r)rs"rrrRs/ h hD h h# hW[ hrcnaVPR4p\V\4'd-VP4UUu.uFwrEWB8wgK VNK uppM.pVP VPR44\ ;QJdV3RlV4F 'gK R# R#!V3RlV44#uuppi)aA toolset in *names* is selected in ``platform_toolsets`` or the top-level ``toolsets`` list. *own_platform*'s row is skipped: it scopes that platform's own sessions, which only exist once the platform is on (:func:`platform_configured_on`). The installers copy cli-config.yaml.example into config.yaml, and it carried ``homeassistant: [hermes-homeassistant]`` until Home Assistant left core, so that row alone is not use.platform_toolsetstoolsetsc3<"TFWp\V\4;'d;\;QJdV3RlV4F 'gK RM RM!V3RlV44xKY R#5i)c3@<"TFp\V4S9xK R#5iNr().0itemrCs& r ,_toolset_listed...\s,PCDSY%-?CsTFN)r#listany)rKselrCs& rrM"_toolset_listed..\sAg\fUXz#t$PP,PC,P,PC,P)PP\fsA" A"A" A"TF)r6r#ritemsappendrP)rBrCr@rowsr>rQ selectionss&f$ r_toolset_listedrWRs ::) *DXbcgimXnXn4::<T<-(8;S##<TtvJfjj,- 3g\fg33g3g3g\fg ggUs B1 B1 process_envFc$V^8dQhRRRRRR/#rrrrXr)rr)rs"rrr_s&pptpTpdprc^RIHpV!VR, 4PR4;'gRP4'dR#V'd2^RIHpV!RR4;'gRP4'dR#\ VR4'dR#\\V4\RR04RR 7# \ dLCi;i) aWhat made core run Home Assistant for *home*: ``HASS_TOKEN`` in its ``.env`` (it enabled both the gateway platform and the tools), the platform on in its gateway config (:func:`platform_configured_on`), or the ``homeassistant`` / ``hermes-homeassistant`` toolset selected for another platform or in the top-level ``toolsets`` list. *process_env* (the active home at startup only) also counts a ``HASS_TOKEN`` the process received from its environment (systemd unit, Docker, shell export).) load_env_filez.env HASS_TOKENr1T) get_secret homeassistantzhermes-homeassistant)r@) agent.secret_scoper\r6r:r^r"r?rWr%r7)rrXr\r^s&$ rhomeassistant_in_usera_s 1dVm$((6<<"CCEE  5<,2299;;<dO44 TI8N&OP_n pp    sB4$B44 CCc$V^8dQhRRRRRR/#rZr)rs"rrrus& G G Gt G Grc^RIpVPVR, PRR74p\ V\ 4'dVPR4MRp\ V\ 4'dVPR4MRp\ V\ 4'd1VPR4'gVPR4'dR #\\V4\R044# \\3d/pLi;i) a What made core's Spotify tools usable for *home*: a login stored in its ``auth.json`` (``providers.spotify``, written by ``hermes auth spotify``) or the ``spotify`` toolset selected for a platform. The tools were opt-in and login-gated, so a client id alone is not use.Nz auth.jsonrr providersspotify access_token refresh_tokenT) jsonloadsr!OSError ValueErrorr#rr6rWr%r7)rrXrhstorerdstates&$ rspotify_in_usernus D;.99;9OP+5UD*A*A +&tI(29d(C(CIMM) $E%EIIn$=$=?A[A[ <-y)/E FF Z s(C%%C;:C;c$V^8dQhRRRRRR/#)rrrpluginr(rr)r)rs"rrrs!884888rc^aaa^RIHp\V3Rl\44oVP V4P R4o\S\4'dSM/oRTT3R llpT!R 4;'dT!R 4'*# \ d\PRTRR7R#i;i) z*plugin*'s bundled copy was on for *home*: its key or name in ``plugins.enabled`` and neither in ``plugins.disabled`` (which wins, as in the loader), read with the managed overlay applied like the loader's config, so an administrator's pinned list counts.r+c3L<"TFqPS8XgKVxK R#5irI)rp)rKfrps& rrM+_bundled_plugin_selected..s>i88v+=11is$ $plugins#left-core: unreadable config for %sTexc_infoFc V^8dQhRRRR/#)rkeyr(rr)r)rs"rr._bundled_plugin_selected..__annotate__snnCnDnrc<SPV4p\V\4;'d;\;QJdV3RlV4F 'gK R# R#!V3RlV44#)c3l<"TF)p\V4SPSP39xK+ R#5irI)r( plugin_keyrp)rKnfeatures& rrM;_bundled_plugin_selected..listed..s,.mglbcs1v':L:Lgnn9]/]gls14TF)r6r#rOrP)rzrCrrus& rlisted(_bundled_plugin_selected..listedsK C %&mm33.mgl.m33m3m3.mgl.m+mmrr0disabled) r.r,next LEFT_COREr4r6r"loggerdebugr#r)rrpr,rrrus&f @@r_bundled_plugin_selectedrs&>i>>G006::9E$GT22gGnn )  7 7VJ%7!77  :D4 Ps B#B,+B,c$V^8dQhRRRRRR/#rZr)rs"rrrs!66$666rc\VR4#)zWhat made core trace to Langfuse for *home*: the bundled ``observability/langfuse`` selected (:func:`_bundled_plugin_selected`). The plugin was opt-in, so keys in ``.env`` alone are not use.langfuse)rrrXs&$rlangfuse_in_users $D* 55rc$V^8dQhRRRRRR/#rZr)rs"rrrs!//T/4/D/rc^RIHpVPV4PR4p\V\4'dTM/p\VPR4;'gVPR4;'gR 4P4pV'g-^R I H pV!V4PR R 4P4pV'gWV'dO^R I HpHpV!V4V!V!448Xd/\ P"PR R 4P4pVP%4R 8H# \d\ P RTRR7RpEL2i;i)a/What made core run its Singularity backend for *home*: ``terminal.backend`` (or the legacy ``terminal.env_type``) set to ``singularity`` in its config (managed overlay applied, as the bridge reads it), else ``TERMINAL_ENV=singularity`` from its dotenv layers as ``load_hermes_dotenv`` resolves them (the home's ``.env``, then the administrator-managed ``.env`` with override, ``${VAR}`` references expanded: :func:`~hermes_cli.env_loader.resolve_home_dotenv`). config.yaml wins over both, as in the bridge. *process_env* (startup) also counts a ``TERMINAL_ENV`` the process received from its environment (systemd unit, Docker, shell export), for the launch home only: ``TERMINAL_*`` is process-global (``get_secret`` never scopes it), so for any other served home it is the launch profile's backend, not this one's.r+terminalrvTrwNbackendenv_typer1)resolve_home_dotenv TERMINAL_ENV)get_routing_process_hermes_homehermes_home_key singularity)r.r,r4r6r"rrr#rr(r:hermes_cli.env_loaderrhermes_constantsrrosenvironlower)rrXr,r configuredrrrs&$ rsingularity_in_users& 11$7;;JG&h55x2HX\\),NN Z0HNNBOUUWJ =(.22>2FLLN +U 4 O4S4U$V V;AACJ     ..  :D4 Ps D22%EEc$V^8dQhRRRRRR/#rZr)rs"rrrs!11t1T1d1rc0VR, P4#)a*home* registered a ``hermes import-agent`` source for ``--sync`` (its ``import-sync.json``, which scheduled syncs read). A one-shot import leaves no other trace, and installing the plugin for every home would add a command nobody asked for; the old spelling names the install.zimport-sync.json)is_filers&$ragent_imports_in_users % % . . 00rT)frozenc]tRt^t$R]R&R]R&R]R&R]R&RtR]R&RtR]R &RtR]R &RtR]R &R t R]R &Rt R]R&Rt R]R&R t R]R&R t R]R&R tR]R&RtR]R&R tR]R&R tR]R&RtR#)LeftCoreFeaturer(rplabelzCallable[..., bool]in_use unchangedztuple[str, ...] secret_env private_envrF off_platformsr1r> enable_envchannel_env_prefixesclicommand old_commandold_clir~terminal_backendrN)__name__ __module__ __qualname____firstlineno____annotations__rrrFrr>rrrrrrr~r__static_attributes__rrrrrs K J N#%J$#%K% !#Ho"%'M?'Hc #%J$,./.CMGSK "G_!Jcrrr_zHome AssistantzRHASS_TOKEN/HASS_URL, platforms.homeassistant and the ha_* tool names are unchanged) rprrrrrrFrr>rrreSpotifyzyour Spotify login, the spotify toolset and the spotify_* tools are unchanged; `hermes auth spotify` is now `hermes spotify login`)rprrrrrLangfusezzyour Langfuse keys and HERMES_LANGFUSE_* settings are unchanged; the plugin is now `langfuse` (was observability/langfuse)zobservability/langfuse)rprrrrrr~z mcp-servezHermes as an MCP serverc R#)Fr)r_s&,rrsV[rzWthe conversation tools keep their names; MCP clients change their args to ["mcp-serve"]zhermes mcp serve)rprrrrrrz&Singularity/Apptainer terminal backendzterminal.backend: singularity, terminal.singularity_image (TERMINAL_SINGULARITY_IMAGE) and the container_* limits are unchanged)rprrrrzagent-importersz`hermes import-agent`zU`hermes import-agent`, its flags and your import-sync.json sync sources are unchangedz import-agent)rprrrrrztuple[LeftCoreFeature, ...]rc V^8dQhRRRR/#)rrrrr(r)rs"rrrsNNN3Nrc ^RIHpVP RVP R\ VP\ V!444 R2#)rget_hermes_home moved out of core into the 'z' plugin: install it with ``)rrrrpr r)rrs& r_install_sentencersG0}}o:7>>:JK o6G1HIJ! MNrc V^8dQhRRRR/#)rr>r(rr)rs"rrrs@@C@C@rcha\V3Rl\4R4pV'dR\V4 2#R#)zFor an unknown platform name that left core: the sentence that names its install command for the active home, else ``""``. Appended to "unknown platform" errors (``send_message``).c3t<"TF-qP'gKVPS8XgK)VxK/ R#5irI)r>)rKrsr>s& rrM(platform_install_hint.."s$Ry!JJA1::;QAAy 88 8N. r1rrr)r>rsf rplatform_install_hintrs3RyRTXYG07R!'*+ ,?R?rc V^8dQhRRRR/#)rrr(rr)rs"rrr&s@@3@3@rcha\V3Rl\4R4pV'dR\V4 2#R#)zFor a ``terminal.backend`` value that left core: the sentence that names its install command for the active home, else ``""``. Appended to "unknown terminal backend" errors.c3t<"TF-qP'gKVPS8XgK)VxK/ R#5irI)r)rKrsrs& rrM0terminal_backend_install_hint..)s)ay!,>,>A1CUCUY`C`AAyrNrr1r)rrsf rterminal_backend_install_hintr&s3ayacghG07R!'*+ ,?R?rc V^8dQhRRRR/#rr'r(rr)rs"rrr-s\\c\c\rc8a\V3Rl\4R4#)ztThe catalog plugin a bundled key that left core now names (``observability/langfuse`` -> ``langfuse``), else ``""``.c3<"TF7qP'gKVPS8XgK)VPxK9 R#5irIr~rprKrsr's& rrM&legacy_plugin_alias..0s)V9a QUAU9sAAAr1)rr)r'sfrlegacy_plugin_aliasr-s V9VXZ [[rc V^8dQhRRRR/#)rrpr(rset[str]r)rs"rrr3sTTsTxTrc\Uu0uF5qP'gKVPV8XgK)VPkK7 up#uupi)zUBundled keys that now name catalog *plugin* (inverse of :func:`legacy_plugin_alias`).)rr~rp)rprss& rlegacy_plugin_keysr3s1"+ S)Q||LF@RLALL) SS SsAAAc(V^8dQhRRRRRRRR/#)rprogr(valueactionrr)rs"rrr8s.ffSffcf3frc aa^RIHp\V!44p\VV3Rl\4R4pVes\ VP V4pV'dRMR\VP V4 R2pVP RVP RVP R VP RV 2 #SR 8Xd\V3R l\4R4pM$SR 8Xd\V3R l\4R4pMRpVfR#\VP V4p \ VP V4'gRV R2pMSR 8XdRV PRR4 R2MRpSR 8XdMRPRR VS344p VP RVP RT R S RT;'gR RV 2 #SVP9dRS R2M VPp V RVP RV 2#)aaFor a command a left-core plugin took over: ``hermes auth [] `` (core's old login spelling), core's old nested spelling (``hermes mcp serve``), or the plugin's own ``hermes `` / ``hermes `` / ``hermes `` while the plugin is not loaded, the line saying where it went and how to get it for the active home, else ``""``.rc3~<"TF2qP'gKVPS RS 28XgK.VxK4 R#5i) N)r)rKrsrrs& rrM%moved_command_hint..?s3_Y--!AMMPTvUVW\V]M^<^!!Ys == =Nr1z Install it with: ``.rz ' plugin: `z` is now `hermes z hermes authc3t<"TF-qP'gKVPS8XgK)VxK/ R#5irI)rrKrsrs& rrMrFs#I9a!%%5.9rhermesc3<"TF=pS'gK SVPVP.VPO59gK9VxK? R#5irI)rrrrs& rrMrHs7b9a%AEE199CaWXW`W`Ca:a9s A'A Az Enable it with: `z install z enable rc38"TFq'gK VxK R#5irIr)rKps& rrMrSsF"@QAqq"@s  loginz`hermes rz' plugin, which is not loaded.)rrrrrplugin_presentrpr rrrreplacejoinr) rrrrrmovedpresentr6rinstalloldrs ff& rmoved_command_hintr8s 1 ! "D _Y_ae fE  t4b#67G VZ7[6\\^!_;;-w~~>NkZ]Y^_ '6#4#4W"5Ru> ?#(GOO#;hugQ EW1'..1AA_`c_d eerc V^8dQhRRRR/#rr)rs"rrrZs??C?C?rcha\V3Rl\4R4pV'd\V4 R2#R#)aFor a plugin name nothing resolves to (so the plugin is not installed): the bundled key of a plugin that left core (``observability/langfuse``) or its catalog name, the line naming the install command for the active home, else ``""``. Appended to "No plugin named ..." errors.c3<"TF9qP'gKSVPVP39gK5VxK; R#5irIrrs& rrM$moved_plugin_hint..^s0^y!LLATallTUT\T\E]=]AAysAA AN.r1rr'rsf rmoved_plugin_hintrZs3^y^`deG/6( ) +>B>rr _attemptedzdict[str, list[str]] _undeliveredc$V^8dQhRRRRRR/#)rrpr(rrrr)r)rs"rrrfs!0030d0t0rc>VR, V, P4#)zQInstalled in *home* (enabled or not: a user who disabled it chose to). Read-only.ru)is_dir)rprs&&rrrfs 9 v % - - //rc$V^8dQhRRRRRR/#)rrr selectionrOrr)r)rs"rrrks!99?9t99rcaaRV3Rllo\;QJdV3RlV4F 'gK R# R#!V3RlV44#)zWhether core resolved *feature*'s toolsets on for a platform selecting *selection*: named directly, or through a ``hermes`` / ``hermes-`` composite that included them.c V^8dQhRRRR/#)rr'r(rr)r)rs"rr#_core_carried..__annotate__nssscsdsrc<VSP9gVR8XdR#VPR4;'d,V\R4RPRR4SP9#)rTzhermes-N-r)rF startswithlenrrrs&rcarries_core_carried..carriesnsW 7## #tx'7y)rrd3y>?.C.K.KCQT.U]d]r]r.rrrc3F<"TFpS!\V44xK R#5irIrJ)rKr'r s& rrM _core_carried..rs8idws4y!!is!TF)rP)rrr sf&@r _core_carriedrks:ss 38i83383838i8 88r_left_core_scoped_left_core_installedc(V^8dQhRRRRRRRR/#) rrBrrzr(rrrr)r)rs"rrr{s.GGDGsG_GGrcVPV4p\V\4;'dVP\ \ V49#rI)r6r#rOrpmapr(rBrzrdones&&& r_markedr{s3 ::c?D dD ! F FgnnC&FFrc$V^8dQhRRRRRR/#)rrBrrrrr)r)rs"rrrs&IIII4IrcVVP'*;'g\V\V4#rI)rFr _SCOPED_KEY)rBrs&&r _scope_keptrs"  H H76;#HHrc(V^8dQhRRRRRRRR/#) rrBrrzr(rrrNoner)rs"rrrs.``$`S`?`t`rcVPV4p\0\V\4'd\ \ V4MRmVP k4W&R#)Nr)r6sortedr#rOrr(rprs&&& r_markr!s> ::c?D^jt.D.DCTN"^w~~^_FKrc$V^8dQhRRRRRR/#)rrrrrrrr)rs"rrrs!'&'&D'&?'&t'&rc^RIHpHp^RIHpVR, pV!V4p\ VP V4;'d\V\V4'*p\Wa4'd V'gR#V'd\V\V4\Wa4'EgVPR4p\V\4'dTM/pVP4U U u/uFwr\V 4V!V 4bK p p p VP Fp V P#V R4K VPR4p \V \4'dT M/p V P4FwrVfWP 9dKVe\%W4'dK2\V PV 4\&4'dV PV 4M.pVP(Uu.uFpVV9gK VNK up;p'gK\+0\-\V4mVm4W&K V 'dWR&\V\.V4V!WV4R#uup p iuupi)aKeep *feature*'s core-era toolset scope, and mark it installed once its plugin is in *home*, in one config write. Scope: record the toolsets in ``known_plugin_toolsets[platform]`` (= off) for every platform where core had them off: a saved ``platform_toolsets`` list that does not carry them, or no list on an ``off_platforms`` platform. Platforms core resolved them on for are left alone. A one-time conversion per home and row, independent of installation: a plugin installed before the update (it stays inert on a core that still ships the feature) still needs it. Completion is marked under ``_left_core_scoped`` so a later run never undoes a choice the user made since (``hermes tools``). Raises when config.yaml cannot be read or written.)atomic_config_writeread_user_config_raw)parse_platform_toolsets_valuerNrEknown_plugin_toolsets)hermes_cli.configr$r%hermes_cli.toolset_validationr&rrpr_INSTALLED_KEYrr!r6r#rrSr(r setdefaultrrOrFr rr)rrr$r%r&pathrB installedsavedrvrVr>knownrcurrenttsmissings&& r_record_migrationr4sLK - D !$ 'Fw~~t4eeWV^]d=e9eI6##I fng. v ' ' ./#E400bKP;;=Y=41c!f;A>>= Y--H  ! !(D 1. 23#E400b#-#3#3#5 H X5J5J%J$w)J)J-7 (8KT-R-Reii)XZG(/(8(8N(8"Bg.__annotate__s . .s .t .rc<^RIHp^RIHpHpV!S4pT!RRRTSf \ 4MSR7V!V4# T!T4i;i)r)dashboard_install_plugin)reset_hermes_home_overrideset_hermes_home_overrider1FT)forceenable catalog_nameassume_deps_consent)hermes_cli.plugins_cmdrHrrIrJr )r'rHrIrJr9rArs& r_install_install_into.._installsLCY(. .+BeDW[Y`Yh@S@U18: 'u - &u -s < Ar)rrArPsfd r _install_intorRs . . Orc V^8dQhRRRR/#)rerrorr(rr)rs"rrrsLLLLrc0VP4Uu.uF*qP4'gKVP4NK, pp\RV4R4pT;'g#V'dV^,PR4#RPR4#uupi)zOne line for a notice: git's own ``fatal:`` / ``error:`` line when *error* ends with raw git stderr (a failed clone), else its first non-empty line.c3"TFDqPR4'gKVPR^4^,P4xKF R#5i)fatal::N)rWzerror:)r splitr:)rKlines& rrM_first_cause..s9kED__UiEj/$**S!$Q'--//Es A/ANz unknown errorr) splitlinesr:rrstrip)rTrZlinescauses& r _first_causer`sy',&6&6&8 I&8dJJL\TZZ\&8E I kEkmq rE  = =%eAh E Ed KK_ E Ed KK Js BBc ,V^8dQhRRRRRRRRR R /#) rrrrrrrCr7r8rr)r)rs"rrrs2toCX+04rc V!VP4pVPR4'd?\ W4V!RVP RVP RVP R24R #\WP4\\VPR4;'gR 44pV!R VP R VP R V R\VPV4 R2 4R# \dpRRR\T4/pRp?LRp?ii;i \d"p\ P RY4Rp?ELRp?ii;i)okFrTNz/left-core install marker not written for %s: %su ✓ u& moved out of core — installed the 'z' plugin from the catalog (z).Tr1r; moved out of core and its 'z/' plugin could not be installed automatically: z. Run `r) rpr"r(r6r4rrrrr r`r )rrrr7resultr?rTs&&$$ r _install_onerfs-2(zz$ W d , fW]]O#I'..IYZ))*" . /$' VZZ066B7 8E&;GNN;KL(8(N'Or ST  2wC12  W LLJD V V Ws.C* D* D5D  D D=D88D=r7c ,V^8dQhRRRRRRRRR R /#) rrrrrCr7r8rXr)r list[str]r)rs"rrrs3t)>EZ"/8rc.p\WVR7F3p\WWR7'gKVPVP4K5 V#)zcInstall every left-core plugin *home* uses and lacks. Returns installed plugin names; never raises.)r7rXrr7)r@rfrTrp)rrr7rXr-rs&$$$ r migrate_homerksBID{C w @ @   W^^ ,D rc V^8dQhRRRR/#)rr7r8rrhr)rs"rrrs**3* *rc aa ^RIHp^RIHpRV3Rllp/pV!4Fsp\ WS!V4R7p\ V4;'d \ V4pTF9o TPS PT3S .34^,PT4K; Ku .p VP4EF8wo p \V 4^8dL\4'd<S!RS P R \V 4 R R P#R V 44 R 24V!4;_uu_4\%V 4Fwr\'VS \)V4V!V4R7'dV PS P4KFW^,Rp V 'dWS!RS P RR P#RV 44 R2R P#V 3RlV 44,R,4M RRR4EK; V # \d#p\PRYX4Rp?EKRp?ii;i +'giEK;i \*d S!R4T #i;i)a``hermes update`` hook: every profile home sharing this venv. Grouped by plugin and each home's unattended consent like the memory migration: homes of one group share dependency answers, and a failure names the rest of its group in one line instead of failing them one by one.)shared_dependency_answers)dependency_homesc V^8dQhRRRR/#)rrrrr8r)rs"rr'migrate_all_homes..__annotate__sRRtR 5Rrc<aVV3Rl#)cN<S!R\S4 RVP4 24#)z [z] )r lstrip)messagerr7s&rr5migrate_all_homes..labelled..s%sST):(;2gnn>N=O#PQrr)rr7sfrlabelled#migrate_all_homes..labelleds QQrr7z&left-core migration skipped for %s: %sNz z is used in z profiles (z, c38"TFp\V4xK R#5irIr rKhs& rrM$migrate_all_homes..(s!@%Q+a..%zA); your answers to its dependency questions apply to all of them.rju ⚠ The 'z' plugin was not installed for c38"TFp\V4xK R#5irIr{r|s& rrMr~2s(FAQrz either. Run c3X<"TFpR\SPV4 R2xK! R#5i)rN)r rp)rKr}rs& rrMr~3s+'a\`WX!,` (with `-p `) for the rest.)hermes_cli.plugins_cmd_installrnpm.plugins_stateror@r)rr"rrr+rprTvaluesr r rr enumeraterfrRKeyboardInterrupt)r7rnrorwpendingrfeaturesrAr?r-homesindexrestrsd @rmigrate_all_homesrs)I1RRKMG " (4.9H8n<<t););rc aa a ^RIHpV!4e.#^RIHpHp\ V!44pV!V4o RV V3Rllo Se&\ PS .4F pS !V4K S \9d.#\PS 4RV 3Rllp\WFRRR 7pV'g.#^R I H pV!4'gFVF=p V!R V P R V P R \V PV4 R24K? .#.p VFp \!WI\#VRR7VR7'gK$V P%V P4SfKEV P&'gKY\)V4'gKlV!RV P R24K V # \*d%p \,P/RT RR7.uRp ? #Rp ? ii;i)a:Agent/gateway start hook for the active home: one attempt per process per home. With *say* (an agent's startup-warning sink) outcomes are delivered now, together with any a gateway-start attempt queued for this home; without it they are logged and queued for the home's first agent. Returns installed plugin names.)worker_config_snapshotN)rrc V^8dQhRRRR/#rrur(rrr)rs"rr(recover_at_startup..__annotate__SsSSSSrc<Sf(\PS.4PV4R#S!V4R# \d\P RRR7R#i;i)Nz'left-core migration notification failedTrw)rr+rTr"rr)rurzr7s&rdeliver#recover_at_startup..deliverSsU ;  # #C , 3 3G <  S L S LLBTL R Ss8"AAc V^8dQhRRRR/#rr)rs"rrrcsrcb<VP4p\PV4S!V4R#rI)r:rwarning)rurs&rreport"recover_at_startup..reportcs"--/wrT)r7rXr5)lazy_installs_allowedu⚠ rdzo' plugin is not installed, so it is off. security.allow_lazy_installs is off, so Hermes did not fetch it: run `r)rArjzrr"rr)r7rrrrrurrrrr-r?rrzsd @@rrecover_at_startuprDs @+ A ! "D $ CSS #''R0G G 1 j NN3 D$MI4$&&#gmm_,HHXY))9'..$)O(PPRTU$I  GD=t3TZ`aa  0?w'7'7'7ODdS sIF,F?AF#F,F F!F4F F?F:4F?:F?c V^8dQhRRRR/#)rr'z Optional[str]rrr)rs"rrrs P Pm P Prcaa^RIHp\V!44o\;QJd$VV3Rl\4F 'gK RM RM!VV3Rl\44'd\ RR7R#R#)a``hermes `` names a command a left-core plugin registers, and the active home uses that feature but lacks the plugin: run :func:`recover_at_startup` now, before plugin commands are discovered, so the command it installs runs in this same invocation. A home nothing migrated yet (a Docker image swap runs no ``hermes update``) whose only Hermes process is a scheduled ``hermes import-agent --sync`` never starts an agent or a gateway to do it.rc3<"TFspS;'deSVPVP.VPO59;'d5\VPS4'*;'dVP S4xKu R#5irI)rrrrrpr)rKrsrr's& rrM&recover_for_command..sw 2'0!   DQUUAII: ::  >RSRZRZ\`Ca?a  xx~ '0s A>/A>"A>$A>TFc8\V\PR7#))file)printsysstderr)rus&rr%recover_for_command..suW3::/NrryN)rrrrPrr)r'rrsf @rrecover_for_commandrsR 1 ! "D s 2'0 2sss 2'0 222NO2r)r])HASS_URL)r_)acpwebhook)HASS_)HERMES_LANGFUSE_SECRET_KEY)HERMES_LANGFUSE_PUBLIC_KEYHERMES_LANGFUSE_BASE_URL)claw)r1)B__conditional_annotations____doc__ __future__rloggingrr dataclassesrpathlibrtypingrrr<rrr r r r r getLoggerrrLEFT_CORE_TERMINAL_KEYSr%r?rWrarnrrrrrrrrrrrrrrsetrrrrrr*rrr!r4r@rRr`rfrrkrrrr)rs@rrso4# !%   8 $ 89UV2d. hPR hpEp, Ge G 8&6u6 /%/81E1 $***\&6?Sf" #3EP_"  .H   O<2N+ ";D[m); $LUg=&   (?H\i G(* &(TN @@\ T fD?u H%' "'0 9" (G I` '&T#E#"#L 4 L*]b%**e*Z;;| Pr