+ jHj&Rt^RIHt^RIt^RIHt^RIt^RIt^RItRt Rt RRlt Rt R R lt R tR R ltRR/RRlltRRltRtR#)zBRead-only canonical admission fences for dispatcher reclaim paths.)closingN)PathcVPRV34P4pVfR#\P!VR,4p\ \ P !\VR,4P4R,RR74;_uu_4pVPR VR ,VR ,34P4pRRR4XeV^,R 8Xd V^,R 8H#VeV^,R9dR#^RI H pV!\P!VR,44VR,8g# +'giLu;i \\\\ P 3dR#\P dR#i;i)zAMissing/ambiguous owner receipts never authorize another attempt.zSELECT e.payload FROM task_events e JOIN tasks t ON t.current_run_id=e.run_id WHERE t.id=? AND e.task_id=t.id AND e.kind='owner_admitted' ORDER BY e.id DESC LIMIT 1NFpayloaddbz?mode=roT)urizXSELECT status,outcome FROM session_admissions WHERE target_session_id=? AND request_id=? session_id request_idterminal interrupted process_birthpidbirth>queuedunknown)executefetchonejsonloadsrsqlite3connectras_urihermes_cli.process_identityr psutilProcessOSError ValueErrorKeyErrorError)conntask_idmarkerbindingownerrowr s&& E/home/ubuntu/.hermes/hermes-agent/hermes_cli/kanban_owner_recovery.pyowner_reclaim_pausedr' sC \\ a  HJ ~**VI./ W__T'$-%8%?%?%AJ%NTXY Z Z^c-- z!(!6 8M NPPXPXPZ [ ?s1v3q6]* * ;#a&$99=V^^GEN;<@PPP[ Z Z7== 9 <<sBA+E1D2%E+E?2E2 E =E%F-FFFcVPRW34P4pV'd\P!VR,4M/p\ T\4'dT#/# \\ 3d/u#i;i)zThe newest ``kind`` payload on the task's CURRENT run, or ``{}``. A payload that cannot be read is not a payload that says the attempt is over, so callers treat ``{}`` as "no evidence" rather than as an absence. SELECT e.payload FROM task_events e JOIN tasks t ON t.current_run_id=e.run_id WHERE t.id=? AND e.task_id=t.id AND e.kind=? ORDER BY e.id DESC LIMIT 1r)rrrrr TypeError isinstancedict)r r!kindr%rs&&& r&_latest_run_eventr.$sx ,, R  "03$**S^,!$//77R7  " s'A$$A:9A:c$V^8dQhR\/#returnbool)formats"r& __annotate__r65sBBdBc^RIHp\V4;'d)\V4P VP 44#)uJTrue when ``lock`` was issued by this host — the only pids we can judge. kanban_db) hermes_clir:r4str startswith _host_prefix)lockkbs& r&_host_local_lockrA5s-* : A A#d)..r/@AAr7c\WR4pV'gR#^RIHpV!VPR4VPR44'*#)zRTrue when the owner bound an interpreter to the task's current run and it is dead. worker_boundF _worker_aliver started_at)r.hermes_cli.kanban_db_dispatchrEget)r r!boundrEs&& r&bound_interpreter_gonerJ;s9 d^ .owner_attempt_provably_over..sP47Gs=224sT)r;r:rGrEr.rrrArMtime _to_epoch)DEFAULT_CLAIM_HEARTBEAT_MAX_STALE_SECONDSrRr[any) r r!r@r%nowexpires heartbeatpidsrEs && @r&owner_attempt_provably_overrogs (+;77 ,, ") --5XZ {*3|+<== diik Cll3/0G'. S!456IB4`4`!` 0@PQ R R Dw /D sP4Pss PPs PPsP4PP PPr7 crash_sweepFc$V^8dQhR\/#r0r3)r5s"r&r6r6s::$:r7c~\W4'gR#V'd\W4'dR#\W4'*#)aTrue when a reclaim path must leave this task alone. The pause protects the effects of an attempt that may still be in flight, and stops holding the claim as soon as nothing can still be executing it. A run whose bound interpreter is dead stays the crash sweep's alone (``crash_sweep=True``), so it is booked ``crashed`` and re-queued once rather than ``reclaimed`` by whichever path ticks first. A run that never bound one is released by any path once ``owner_attempt_provably_over``: the shape that used to be unreclaimable forever, because ``bound_interpreter_gone`` was the only override and it needs the ``worker_bound`` event that run never wrote. F)r'rJro)r r!rps&&$r&owner_reclaim_blockedrss1  . .-d<<*49 99r7c0V^8dQhR\R\/#)r1 signalledr2r3)r5s"r&r6r6s G G$ G4 Gr7c\WVR7#)a`The under-lock re-check for a reclaim path, after its termination step. When this host just signalled the run's worker (``signalled``), killing it takes its bound interpreter down too (``_watch_submitter``) and the owner settles the admission ``unknown``: a pause this path caused itself, which would leave a timed-out run for the crash sweep to misbook ``crashed``. Only an interpreter still LIVE (one that bound after the first look) keeps the claim. Without a local signal (a foreign-host claim) the bound interpreter's pid means nothing here, so a "dead" reading is no proof and the plain gate applies. )rp)rs)r r!rus&&$r& owner_reclaim_blocked_after_killrws !I FFr7c aaVV3RlpV!R4V!R4reV0VPR4V8XdVPR4.M.mpVPR4V8Xd(VPR4V9dVPR4#R#)uNThe exit code a managed run's authority recorded for the task's CURRENT run, else None. Managed interpreters are children of the authority, not the dispatcher, so their result is read from the run's ``worker_result`` event (it survives a dispatcher restart and cannot be reaped here). It speaks for the run only under the same claim and from a pid of this run: the dispatcher's own worker, or the owner-side interpreter ``worker_bound`` recorded under that claim — ``session_kanban._record_worker_result`` writes the interpreter's pid, never the spawned submitter's ``tasks.worker_pid``.c<SPRSV34P4pV'd\P!VR,4M/p\ T\ 4'dT#/# \d/u#i;i)r)r)rrrrrr+r,)r-r%rr r!s& r&latest%managed_run_exit_code..latestswll VX_aeWfhhphphr  47djjY0RG%Wd33w;; I sA&A&& A65A6 worker_resultrCr^r exit_codeN)rH)r r!rTr^rzresultrIrnsff&& r&managed_run_exit_coders<?+VN-CE  _ ,0G:0U599U+,[] _D&,jj&>*&LQWQ[Q[\aQbfjQj6::k "tpttr7)__doc__ contextlibrrpathlibrrrgrr'r.rArJrRr[rorsrwrrcr7r&rsZH  48"B H24M)QX::$ Gur7