+ jHja0t$Rt^RIHt^RIt^RIHt^RIHtH t H t H t ^RI H t Ht/tR]R&/tR]R &]P$!4tR R ltR R ltRRRlltRRRlltRRRlltRRRlltRRltR#)uWhich profile homes THIS process ticks, and who owns the cron tick for a given home. One gateway process per host multiplexes every profile, so "does a gateway own cron for profile X" stopped being answerable from the launch home alone: ``gateway.status.owns_gateway_runtime_lock`` is a process-global boolean set once at boot, and every path resolver behind ``is_gateway_runtime_lock_active`` goes through ``get_process_hermes_home()``, which ignores the per-tick ``_profile_cron_scope`` override. Both therefore answer about the LAUNCH home while the ticker is scoped to some other profile. The two predicates here keep those questions apart: * :func:`owns_cron_tick_for` — this process is the host gateway AND ticks that home. * :func:`live_gateway_ticking` — a DIFFERENT, live host gateway holds the runtime lock and its published served set covers that home. Every probe failure answers "no": ownership claims are certainties, never guesses. ) annotationsN)Path)AnyDictOptionalUnion)get_hermes_homehermes_home_keyzdict[str, Path] _ticked_homeszdict[str, str]_ticked_storescV^8dQhRR/#)returnNone)formats"=/home/ubuntu/.hermes/hermes-agent/cron/scheduler_ownership.py __annotate__r$s''D'c^RIHpHp//rCVF'p\V4p\ V4pWcV&V!V4WG&K) \ ;_uu_4\ \4\ V4, pVU u0uFq\9gK\V ,kK up \ VP44, p \P4\PV4\P4\PV4RRR4X'd^RI H p V !V4V!X 4R#R#uup i +'giL7;i)a5Publish the set of profile homes this process's cron ticker owns this cycle. A home that leaves the set also loses its cron worker pool: pools are per home and otherwise live until process exit, so serving (or churning) many profiles leaks one ThreadPoolExecutor and its worker threads per home ever ticked. ) forget_stores store_keyN)discard_parallel_pools)cron.store_healthrrrr _ticked_locksetr r valuesclearupdatecron.schedulerr) homesrrresolvedstoreshomepathkeydepartedkdeparted_storesrs & rregister_ticked_homesr)$s;2fDzd# o  }%H 56>Vh~BU,>!,,hVY\]c]j]j]lYmmX&f% 9x(o&  W s%$D/+ D*<D* A3D/*D// D? cV^8dQhRR/#)r rdictr)rs"rrrBs##d#rcz\;_uu_4\\4uuRRR4# +'giR#;i)zESnapshot of ``home key -> home`` for the profiles this process ticks.N)rr+r rrr ticked_homesr-Bs M" s) : c V^8dQhRRRR/#r r#Optional[Path | str]rboolr)rs"rrrHs$$-$$rc\VeTM \44p\;_uu_4V\9uuRRR4# +'giR#;i)zTTrue when THIS process's cron ticker owns ``home`` (default: the active cron scope).N)r rrr )r#r%s& rserves_profiler3Hs/ $"2$8I JC m# s < A c V^8dQhRRRR/#r/r)rs"rrrOs   1  T  rc|^RIHpVP4'gR#\ T4# \dR#i;i)zTrue when this process is the host gateway multiplexer AND ticks ``home``. The runtime lock alone is not enough: it proves only that this process is the host gateway, not that its ticker visits the profile whose store is being ticked right now. statusF)gatewayr7owns_gateway_runtime_lock Exceptionr3)r#gateway_statuss& rowns_cron_tick_forr<OsB 47799: $  s , ;;c$V^8dQhRRRRRR/#)r recordrr#r0rr1r)rs"rrr_s"11#1-A1T1rc\V\4'gR#^RIHpHpHpVe \ V4M \4pVPR4p\V\4'dVP4'gV!4pV!We4'dR#TPR4p\T\4'gR#T!T4pTRJ;'dY9# \dR#i;i)uITrue when a gateway runtime-status ``record``'s served set covers ``home``. The record is read from the holder's own home, so it always proves that home — that is the pre-multiplex meaning, and a single-profile gateway publishes an EMPTY ``served_profiles``. Other profiles need an explicit entry in the published served set. F)_get_process_hermes_home_profile_label_for_home_same_hermes_homeN hermes_homeTserved_profiles) isinstancer+gateway.statusr@rArBrrgetstrstripr:list) r>r#r@rArBtarget record_homeservedlabels && rrecord_serves_profilerO_s fd # #NN#/d_5Fjj/ +s++;3D3D3F3F24K [ 1 1 2ZZ) *F fd # # #F +E   0 00 sAC:C C"!C"c V^8dQhRRRR/#)r r#r0rzOptional[dict]r)rs"rrr{sCC3C~Crc^RIHpVP4'dR#VP4'gR#VP RR7pVP 4pVeD\ V\4'd.VPR4V8wgVPV4'dR#\Y04'dT#R# \dR#i;i)a+Runtime-status record of ANOTHER live host gateway that ticks ``home``, else None. ``None`` covers every "we cannot prove it" case: this process holds the lock itself, no lock is held, the record does not belong to the lock holder, its heartbeat is stale, or its served set does not name ``home``. r6NF) cleanup_stalepid) r8r7r9is_gateway_runtime_lock_activeget_running_pidread_runtime_statusrEr+rGruntime_status_is_staler:rO)r#r; holder_pidr>s& rlive_gateway_tickingrY{s4  3 3 5 5<<>>#33%3H 335  fd++zz% J.55f==> +6886BdB sB9B9A(B99 CCc V^8dQhRRRR/#)r claimzdict[str, Any]rr1r)rs"rrrs4rcv\VPR4;'gR4PR4p\V4^8gV^,P 4'gR#^RIpV^,VP 48wdR#^RIHpV!\V^,44'*# \dR#i;i)aTrue when the claim's ``by`` names a process on THIS host that provably no longer exists. ``_machine_id()`` stamps ``host:pid[:token]``; a foreign host, an explicit HERMES_MACHINE_ID, or any liveness-probe failure returns False (fail safe: only a proven death shortens the TTL).by:FN) _pid_exists) rHrGsplitlenisdigitsocket gethostnamerFr`intr:)r[partsrdr`s& r_claim_owner_is_deadrhs  $%%2 & , ,S 1E 5zA~U1X--// 8v))+ +.s58}--- s$ B)"B)) B87B8)N)__conditional_annotations____doc__ __future__r threadingpathlibrtypingrrrrhermes_constantsrr r __annotations__r Lockrr)r-r3r<rOrYrh)ris@rrrsg$#--="$ #"$#~~ '<# $  18C8r