+ Wj FRt^RIHt^RIHtRRltRRltRRltR #) uWhich daemon a named-profile client must start when nothing serves its home. A ``/profiles/`` home that the default multiplexer serves has no daemon of its own. When the multiplexer is down (restart, update, crash) the profile looks ``absent`` and the ensure loop would spawn a per-profile gateway for it — a second owner that answers this client and then blocks the multiplexer's next all-or-nothing reserve (``Cannot reserve gateway profiles``). The client must start the multiplexer instead, so the start target is decided here from the same facts the multiplexer boots on (``gateway_multiplex_mode.host_serves_named_profile``): a profile's own ``gateway.standalone: true``, the default profile's explicit ``true``, or — when the flag is unset or the retired ``false`` that boot settles like unset — the served set the last multiplexer recorded in the root's ``gateway_state.json`` (a standalone default gateway clears it). ) annotations)Pathc V^8dQhRRRR/#homerreturnz Path | None)formats"XC:\Users\johnn\AppData\Local\hermes\hermes-agent\hermes_cli\gateway_runtime_multiplex.py __annotate__r s**t* *cf^RIHpV!V4fR#VPPpW 8wdV#R#)zPDefault root that may multiplex *home*, when *home* is a named profile under it.)named_profile_homeN)hermes_constantsrparent)rrroots& r multiplexer_root_forrs13$' ;;  D<4)T)r c V^8dQhRRRR/#rr )r s"r r r s L LD L[ Lr cP\V4pVfR#^RIHpV!W4RJdR#T#)aaThe root whose gateway must serve named profile *home* when nothing records a verdict. ``hermes gateway run`` refuses a ``profiles/`` home a gateway of its own unless it authored ``gateway.standalone: true`` (or passes ``--force``); the retired ``multiplex_profiles: false`` no longer opts out, so only a standalone profile keeps its own daemon. Nhost_serves_named_profileF)r!hermes_cli.gateway_multiplex_moder)rrrs& r implied_host_rootrs0  %D |K,T8EA4KtKr c V^8dQhRRRR/#rr )r s"r r r )sHH$H;Hr c\V4pVfR#^RIHpV!W4pVe V'dV#R#^RIHp^RIHpV!VR, 4;'g/PR4p\V\4'gR#VUu0uFqw'gK V!\V44kK ppV!VP4V9dV#R#uupi)a The root whose (possibly stopped) multiplexer serves *home*, else None. ``hermes_cli.gateway.named_profile_served_by_running_multiplexer`` answers the live question; this is its offline twin for the moment no gateway runs, deciding from the boot policy (:func:`hermes_cli.gateway_multiplex_mode.host_serves_named_profile`): a standalone secondary is never served, an explicit ``true`` serves the rest, and an unset or retired ``false`` flag falls back to the ``served_profiles`` the last multiplexer recorded. No evidence keeps it unanswered. Nr)read_runtime_status)normalize_profile_namezgateway_state.jsonserved_profiles) rrrgateway.statusrhermes_cli.profilesrget isinstanceliststrname) rrrverdictrrservedpnamess & r multiplexer_serves_homer*)s  %D |K'3Gt(D(2:!$)="=>DD" I IJ[ \F fd # #5; AVq + #CF +VE A)$))4=4G4G Bs CCN)__doc__ __future__rpathlibrrrr*r r r r.s# #* LHr