+ jHjU RRt^RIHt^RIHt^RIHtHtRRltRR/RR llt R#) aWhich runtime record describes a profile the host multiplexer may serve. One rule for ``/api/status`` and the messaging card so the two surfaces never pick different records for the same profile. Read-only: it selects and projects existing ``gateway_state.json`` records and writes nothing. ``gateway.status`` is resolved at call time so its test seams (``monkeypatch.setattr(gateway.status, ...)``) still intercept. ) annotations)Path)AnyOptionalc V^8dQhRRRR/#)livenessrreturn Optional[int])formats":/home/ubuntu/.hermes/hermes-agent/gateway/status_served.py __annotate__rsAAAAc@VPR8XdR#VP#)z``liveness.pid`` when it was proven on THIS host; None for a health-probe answer, whose PID belongs to the remote container and may collide with an unrelated local one.healthN)sourcepid)rs&r local_liveness_pidrs??h.4@HLL@r gateway_pidNc(V^8dQhRRRRRRRR/#)rhomer own_runtimezOptional[dict[str, Any]]rr r r )r s"r rrs2\\ \5\GT\\rc^RIHpVeVPWR7eR#VPV4pVeV^,'gR#VwrVVe WR8wdR#VP V4;'gRp/VCRVP Wg4/C#)aThe multiplexer's record projected onto ``home``'s profile (bare platform keys, the shape a standalone gateway writes) when it is that profile's live runtime record, else None. - ``own_runtime`` wins whenever it proves a live gateway of ``home`` -- an own ``--force`` one, or the host's own record on the host itself, which must stay whole so other profiles' ``:`` failures remain visible there; - a missing/unreadable multiplexer record (``(pid, {})``) is no record; - ``gateway_pid`` (a PID the caller proved on this host) must BE the multiplexer, so a gateway of the profile's own holding its lock keeps its record. )statusN) expected_homedefault platforms)gatewayrget_runtime_status_running_pid multiplexer_liveness_for_profileprofile_name_for_home"profile_platforms_from_multiplexer)rrrrservedmux_pidrecordnames&&$ r served_profile_runtimer's6#H#H#H#i#u  4 4T :F ~VAYYOG7#9  ' ' - : :D [f [k6#L#LV#Z [[r) __doc__ __future__rpathlibrtypingrrrr'r rr r,s0# A \W[\\r