+ jHj7Oa0t$Rt^RIHt^RIt^RIHt^RIHt^RI H t ]P!] 4t RtRtRtR tR tR tR R ltRRltRRltR:RRllt]!RR7!RR44tRRltRRltRRltRRltR:R R!lltR"R#ltR:R$R%lltR&R'lt R(R)lt!.t"R*]#R+&R,R-lt$R.R/lt%R0R1lt&R2R3lt'R:R4R5llt(R:R6R7llt)R8R9lt*R#);ucBoot-time verdict for ``gateway.multiplex_profiles`` (the default is on, and there is no opt-out). ``GatewayConfig.from_dict`` leaves the flag ``None`` when neither config.yaml nor ``GATEWAY_MULTIPLEX_PROFILES`` set it. Turning the default on must not make a default gateway double-bind a fleet that still runs per-profile gateways (two pollers on one bot token, port fights), so the implicit default is a *request*: the gateway runs the same preflight ``hermes gateway migrate --multiplex`` runs and multiplexes only when the fold would have been safe. An explicit ``true`` is never second-guessed. An explicit ``false`` is RETIRED (multiplex-only ruling): it parses, it is logged, and it is then resolved exactly like an unset key. The key itself survives because it is still the RUNTIME mode flag every scoped code path reads (``config.multiplex_profiles``) — what it can no longer do is pin a second gateway process onto this host. The refusal is logged, never fatal: the gateway comes up standalone exactly as before the default flipped, and the log names the blocker plus ``hermes gateway migrate --multiplex``. ) annotationsN) dataclass)Path)Optionalz.only one profile exists (nothing to multiplex)zLthis profile is standalone (gateway.standalone: true); it serves only itselfzgateway.auto_multiplex_migration is false, so this gateway serves only its own profile; run `hermes gateway migrate --multiplex` to serve every profileugateway.standalone is a temporary compatibility shim while multiplexing gaps are fixed; it will be removed once they are — plan to fold this profile with `hermes gateway migrate --multiplex`.zgateway.multiplex_profiles: false is retired and was rewritten to true; one gateway per host serves every profile. A per-profile gateway is `gateway.standalone: true` in that profile's config (temporary shim) or `--force`.z.multiplex_opt_out_rewrittenc V^8dQhRRRR/#) default_homerreturnOptional[bool])formats"F/home/ubuntu/.hermes/hermes-agent/hermes_cli/gateway_multiplex_mode.py __annotate__r:s$>c^RIHpHpV!4pVeV#\V4R, pVP 4'gR#^RIHpV!V4;'g/p\VPR4\4'dVPR4M/pVPR4pVfVPR4pVfR#\V\4'dV!V4p V fR#T #\V4#)ajThe operator's explicit choice for the DEFAULT profile's gateway: a recognized ``GATEWAY_MULTIPLEX_PROFILES``, else ``gateway.multiplex_profiles`` (or the top-level alias) as written in its config.yaml; ``None`` when neither is set. Raw read on purpose: the callers are other processes (``hermes -p X ...`` has X's config loaded) asking about the default's file.) _bool_token _env_multiplex_profiles_overrideN config.yamlread_user_config_rawgatewaymultiplex_profilesT) gateway.configrrrexistshermes_cli.configr isinstancegetdictstrbool) rrrenvcfg_pathrcfggateway_sectionvalueparseds & r explicit_multiplex_flagr&:s M * ,C  L!M1H ??  6 x ( . .BC,6swwy7I4,P,Pcggi(VXO GG( )E }##$89 }%U#~t161 ;rc V^8dQhRRRR/#)rr$r r r )r s"r rrTs###N#rcV'dR#R#)zHow boot reads an explicit ``multiplex_profiles``: ``true`` is final; the retired ``false`` settles exactly like an unset key (``None``: the boot preflight decides).TNr )r$s&r settled_explicit_flagr)Ts4"d"rc$V^8dQhRRRRRR/#)rrrhomer r r )r s"r rrZs&HHDHHHrcV^RIHpV!V4'dR#\\V44#)aOOffline twin of the boot verdict for named profile *home* under *default_home*'s gateway: ``False`` for a ``gateway.standalone: true`` secondary (``profiles_to_serve`` never serves it), ``True`` for an explicit ``true`` on the default, ``None`` when boot settles it (unset or the retired ``false``, see :func:`resolve_multiplex_mode`).profile_is_standaloneF)hermes_cli.profilesr.r)r&)rr+r.s&& r host_serves_named_profiler0Zs& :T"" !8!F GGrc V^8dQhRRRR/#)rrOptional[Path]r rr )r s"r rres++n++rc^RIHp^RIHpVe \ V4MV!4pV!V4pVe \ V4#\ V4pVfR#R#)u7Does the default profile's gateway serve every profile? For CLI/dashboard processes: the LIVE gateway's ``served_profiles`` record when one runs (it settled the unset default itself), else the explicit flag, else False — an unset flag is decided by the gateway at boot, never guessed here. The one thing that can no longer report "standalone" is an explicit ``false``: it is RETIRED (warned about and ignored at boot, see :func:`resolve_multiplex_mode`), so answering False from it made every CLI surface contradict the gateway that was about to multiplex anyway. get_default_hermes_root)recorded_served_profilesFT)hermes_constantsr5#hermes_cli.gateway_multiplex_servedr6rrr&)rr5r6rootrecordedflags& r default_gateway_multiplexesr<esR9L!-!94 ?V?XD'-HH~ "4 (DL5*d*rT)frozenc:]tRt^yt$R]R&R]R&RtR]R&RtR#) MultiplexDecisionrenabledrsourcereasonr N)__name__ __module__ __qualname____firstlineno____annotations__rC__static_attributes__r rr r?r?ys M KFCrr?cV^8dQhRR/#)rr rr )r s"r rrs``d`rcb^RIHpHp^RIHpV!4pV!V4R9;'d V!V4#)get_hermes_homeprofile_name_for_homer-)Ndefault)r7rNrOr/r.)rNrOr.r+s r _standalone_launcherrQs0G9  D  &.? ? _ _DYZ^D__rcV^8dQhRR/#)rr zOptional[MultiplexDecision]r )r s"r rrsHH,GHrcV\4'gR#RVn\RR\4#)zOThe per-profile opt-out also binds callers supplying an explicit GatewayConfig.NFguard)rQrr?STANDALONE_PROFILE_REASON)configs&r standalone_launcher_decisionrWs&  ! ! %F UG-F GGrcV^8dQhRR/#)rr z Optional[str]r )r s"r rrs''M'rc^RIHp\4'd\#\ V!RRR74^8d\ #^RIHpHpH pV!4pV'dV#V!4pVP'd,RPRVP44pRV RV R 2#VP'dR PVP4#R #) uFWhy THIS process must not multiplex right now, or None when it may. Mirrors what makes ``hermes gateway migrate --multiplex`` refuse or leave a per-profile gateway in place: hosts whose per-profile gateways the preflight cannot see (s6 slots) stay standalone; a secondary that still runs its own gateway (live process or installed service) or a preflight blocker (duplicate bot credential, port binder without a ``/p//`` ingress) keeps this gateway standalone. Every blocker here is a TRANSIENT, fixable condition, which is why this function is now also the whole answer for an explicit ``gateway.multiplex_profiles: false`` (see :func:`resolve_multiplex_mode`): the host converges the moment the blocker is gone. The launching profile's IDENTITY is deliberately not a blocker: multiplex-only means "the one host process", whichever profile started it. Gating on ``active == 'default'`` made a host whose only gateway runs under a named profile permanently standalone — and every lifecycle verb built on "the default's multiplexer" blind to the process actually serving the host. profiles_to_serveT multiplexinclude_parked)MIGRATE_COMMAND_host_supports_migrationbuild_migration_plan, c3"TFTpRVP RVP'dR\VP4,MVP4 R2xKV R#5i)'z' (zpid )N)namepidr service_label).0ps& r -implicit_multiplex_blocker..sI20xs!%%%6CJ.Q__=NOq Q0s $A7Az profile(s) z. still run their own gateway; fold them with ``z; N)r/r[rQrUlenSINGLE_PROFILE_REASONhermes_cli.gateway_migrater_r`rastandalone_secondariesjoinblockedblockers)r[r_r`ra host_reasonplanowneds r implicit_multiplex_blockerrxs$6((  tD ABQF$$jj*,K  !D """ 20022UG#QRaQbbcdd |||yy'' rcV^8dQhRR/#)rr rr )r s"r rrs%%t%rc^RIHpV!4#)rLr4)r7r5r4s r _default_profile_homer{s8 " $$rc$V^8dQhRRRRRR/#)rdecisionr?rr2r rr )r s"r rrs#'8bfrcVP'dVPR8XdR#Ve \V4M \4pVR, p^RIHpVP 4'dV!V4;'g/M/p\VPR4\4'dVPR4M/pVPRVPR44pVRJdR#^RI H pV!VR4VPR 8Xd*V\, P\R ,R R 7\ P%RTTfRM \'T44R# \d\ P#R RR7R#i;i)aWrite ``gateway.multiplex_profiles: true`` into the DEFAULT profile's config.yaml so the file reads as the gateway behaves. The key has ONE valid value right now (Teknium ruling): an unset key is made explicit ("left unset" was read as "off"), a retired ``false`` is rewritten in place and leaves a one-time marker for the boxed notice. Comment-preserving writer, once, and NEVER on a guard refusal (the file must not say true while the runtime is standalone). Returns True on a write.rTFrrrrT)_write_multiplex_flagretired-opt-out zutf-8)encodingz2could not persist gateway.multiplex_profiles: trueexc_infoz6Wrote gateway.multiplex_profiles: true to %s (was %s).unset)r@rArr{rrrrrrrprREWRITTEN_MARKER_NAME write_textRETIRED_OPT_OUT_REASON Exceptionloggerdebuginforepr)r}rr!rr"sectionin_filers&& r persist_resolved_defaultrs6    x'9)5)A4 %G\G^Lm+H :6>oo6G6G"8,22R(237793Et(L(L#'')$RT''. TW[>[fm = n KKH("?W ?   ITX Ys& E %E 4A$E A E "E10E1cV^8dQhRR/#rr list[str]r )r s"r rrs44i4rc\.RO4#)zTThe one-time boxed notice for a rewritten ``false`` (same box as the guard warning).)uK⚠ gateway.multiplex_profiles: false is retired and was rewritten to true;z*one gateway per host serves every profile.zLA per-profile gateway is `gateway.standalone: true` in that profile's configz(temporary shim) or `--force`.)_boxr rr retired_opt_out_notice_linesrs 3 44rc V^8dQhRRRR/#)rrr2r rr )r s"r rrs * *> *Y *rcVe \V4M \4pV\, pVP4'g.#VP 4\ 4# \ d.u#i;i)zW``hermes update``'s summary: print the rewrite notice ONCE more, then clear the marker.)rr{rrunlinkOSErrorr)rmarkers& r consume_rewritten_noticersa)5)A4 %G\G^L 1 1F ==??   ( ))  sA A*)A*c V^8dQhRRRR/#)rbodyrr r )r s"r rrs++y+Y+rc \RV44^,pRRV,,R,.VUu.uFpRVPV^, 4 R2NK! upORRV,,R,N#uupi)c38"TFp\V4xK R#5iN)rn)rilines& r rk_box..s+ddD dsu┌u─u┐u│ u│u└u┘)maxljust)rwidthrs& r rrsy +d+ +a /E EEM !E ) +<@ ADDTZZ *+3/D A + EEM !E ) ++ As%A5cV^8dQhRR/#)rr r?r )r s"r rrs&7rc\VRR4p\V4pVeV#\V4'd \RR4#VRJp\ 4pV'd\RR V4pM'V'd\RR \4pM \RR R 4pVPVn V# \ d)p\ PRTRR7RT R 2pRp?L~Rp?ii;i)uSettle ``config.multiplex_profiles`` for one gateway boot; the config is updated in place. ``gateway.multiplex_profiles: false`` is RETIRED as a topology opt-out (multiplex-only ruling). The key still parses and still drives the runtime mode this function writes back, but an explicit ``false`` no longer pins a per-profile fleet: it is warned about and resolved exactly like an unset key. That is safe because the unset path is not optimistic — it refuses to multiplex while any real blocker holds (an s6 container, a secondary that still owns a gateway, a duplicate bot credential), so a host that genuinely cannot fold still comes up standalone and says why, and it converges by itself once ``hermes gateway migrate --multiplex`` has run. rNTrVFz3Multiplex preflight failed; starting standalone: %srzpreflight failed (rerTrrPz1gateway.multiplex_profiles unset; default applies) getattrrWr)r?rxrrwarningrr@r)rVcurrent standaloneretired_opt_outblockerexcr}s& r resolve_multiplex_modersf2D9G-f5JW%% x00&O.,.$UGW= $T+<>TU$T96ij ( 0 0F O .Lc\`a&se1-.s B C&C  Czlist[MultiplexDecision]_pending_decisionc V^8dQhRRRR/#rr}r?r Noner )r s"r rrsOO(9OdOrc^RIHpHpV!4'g V.\R&R#\P 4T!VP R8Xd VP MRR7R# \d\PRRR7R#i;i) aPersist a guard refusal into ``gateway_state.json`` so `hermes gateway status` can show why this gateway serves one profile while the default says multiplex; any other verdict clears the field. Only the runtime-lock owner writes that file. The decision is made while the config loads, before the lock claim, and a pre-lock write published this process's pid as a live ``starting`` gateway: a launch racing it read that as an owner and refused, leaving no gateway at all. Until this process holds the lock the decision stays pending; ``publish_pending_multiplex_decision`` writes it once the claim succeeds, and a launch that loses the claim never writes it.)owns_gateway_runtime_lockwrite_runtime_status:NNNNrT)multiplex_standalone_reasonz'could not record the multiplex decisionTr) gateway.statusrrrclearrArCrrr)r}rrs& r record_multiplex_decisionrsmOR(**$,: a !HOO_fLflpq O > NOsA A:A"BBcV^8dQhRR/#)rr rr )r s"r rr2s99D9rcN\'d\\R,4R#R#)zZWrite the decision held back before the runtime-lock claim (called right after the claim).N)rrr rr "publish_pending_multiplex_decisionr2s!"3B"78rc V^8dQhRRRR/#rr )r s"r rr8s++%6+4+rcD\V4VPR8XdD\PR\4\ V4\ 4Fp\V4K R#VPR8Xd-VP\8Xd\PR4R#VPR8Xd@\PRVP4\V4Fp\V4K R#VPR8Xd#\PR4\ V4R#R#)rz%srTz[Single-profile install: gateway.multiplex_profiles unset, serving the default profile only.zHThis gateway stays standalone: %s. It serves only the launching profile.rPzRServing every profile on this host (gateway.multiplex_profiles unset; default on).N) rrArrrrrprintrCrorstandalone_warning_lines)r}rs& r log_multiplex_decisionr8sh'++t34 *02D $K3 G #;P(P qr G # V OO -X6D $K7 I % hi * &rcV^8dQhRR/#rr )r s"r rrLsjj9jrc^RIHpHp^RIHpV!V!44;'gRpV!RRR7UUu.uFwrEWC8wgK VNK upp#uuppi)zZNamed profiles a standalone gateway leaves without a bot (the whole point of the warning).rMrZrPTr\)r7rNrOr/r[)rNrOr[merf_homes r unserved_profilesrLsIG5 0 1 > >YB$5UY$Z i$Z[T^b^hDD$Z ii is A A c$V^8dQhRRRRRR/#)rr}r?unservedzOptional[list[str]]r rr )r s"r rrTs$'8DWclrc$VPR8wgVP\8Xd.#Vf \4pV'g.#^RIHpRRRPV4,RVP 2RV 2.p\V4# \d.pLVi;i)akThe boxed warning a multi-profile host prints when a guard keeps its gateway standalone. Empty for anything but a guard refusal on a host with other profiles to serve: a single-profile install has nothing unserved, so there is nothing to shout about. The same box appears at gateway start, in the ``hermes update`` summary and (as text) in the dashboard banner. rT)r_u?⚠ This gateway is STANDALONE: it serves only its own profile.z.Profiles NOT served (their bots stay silent): rbzWhy: zFix: ) rArCrorrrpr_rrr)r}rr_rs&& r rrTs'!X__8M%M  (*H  :I8499X;NN  !  !  D : H s A?? BBc V^8dQhRRRR/#)r state_pathz Path | Noner z str | Noner )r s"r rrnsGG;G*GrcN^RIHpHpV!V4;'g/pVPR4R9dR#V!V4'gR#VPR4p\T\4'dT'd \T4#R# \\ \ \\3dR#i;i)zThe guard refusal a LIVE standalone gateway published in its ``gateway_state.json`` (this home's, or *state_path*), else ``None``. A stopped, failed or dead record's reason is history.)read_runtime_statusruntime_status_pid_is_live gateway_stateNr)Nstoppedstartup_failed) rrrrr ValueError TypeErrorAttributeError OverflowErrorrr)rrrrecordrCs& r recorded_standalone_reasonrns R$Z066B ::o &*M M*&119: %VS11f3v;F$F ZNM Js!BB BB B$#B$cV^8dQhRR/#rr )r s"r rrsOO9OrcV\4pV'g.#\\RRV44#)zSame box, rebuilt from the live gateway's ``gateway_state.json`` for processes that did not make the decision (``hermes update``'s summary, ``hermes gateway status``).FrT)rrr?)rCs r !recorded_standalone_warning_linesrs)( )F  #$5eWf$M NNrr)+__conditional_annotations____doc__ __future__rlogging dataclassesrpathlibrtypingr getLoggerrDrrorUAUTO_MIGRATION_OPTED_OUT_REASONSTANDALONE_DEPRECATION_NOTICErrr&r)r0r<r?rQrWrxr{rrrrrrrHrrrrrrr)rs@r rs$#!   8 $HjF p,74# H+( $`H'T% :4 *+B.0*/O(9 +(j4G(Or