+ jHj@Rt^RIHt^RIt^RIt^RIHtHt]P!] 4t Rt Rt RRlt ]!RR04t!R R ]4tR R ltR RltRRRRRRRR/RRlltRRltRR/RRlltRRRR/RRlltR#)aWake an existing agent session from a background completion event. Push-capable adapters (``supports_async_delivery``) get a synthetic ``MessageEvent(internal=True)`` via handle_message; stateless adapters (API server) would run that under a ``build_session_key()`` key that never matches the raw ``X-Hermes-Session-Id`` real turns use (invisible parallel session), so we self-POST ``/v1/chat/completions`` with the raw id header to resume the REAL session. Exception: async-delegation completions: the CLIENT owns the next turn, so they are never self-POSTed as a new ``role=user`` prompt (could cross a pending human-confirmation gate); instead ``persist_delegation_delivery`` writes a durable DELIVERY row (``display_kind= "async_delegation_complete"``, read by TUI/desktop pollers). Failures RAISE (after bounded retries on transient errors) so callers can rewind cursors / retry instead of silently losing the event.) annotationsN)AnyOptionalg@c V^8dQhRRRR/#)adapterrreturnbool)formats"1/home/ubuntu/.hermes/hermes-agent/gateway/wake.py __annotate__r sCC3C4Cc.\\VRR44#)aWhether this adapter can push a message to the user after a turn ends. Reads ``supports_async_delivery`` off the adapter class rather than the request-scoped contextvar (background watchers run outside any bound session context). Adapters that don't declare the flag are push-capable.supports_async_deliveryT)r getattr)rs&r adapter_supports_pushrs !:DA BBr not_foundinvalid_paramsc>a]tRt^0tRtRRR/RV3RlllltRtV;t#)WakeNotAccepteda No adapter admission: retry without treating a healthy chat as dead. ``reason`` is the store's refusal code when the session authority refused it (None: the adapter did not accept); ``permanent`` is set once the refusal is proven final (``refusal_proven_permanent``).reasonNc V^8dQhRRRR/#)rmessagestrr Optional[str]r )r s"r r WakeNotAccepted.__annotate__5sZgrc @<\SV`V4W nRVnR#)FN)super__init__r permanent)selfrr __class__s&&$r rWakeNotAccepted.__init__5s ! r)r r)z%internal wake not accepted by adapter)__name__ __module__ __qualname____firstlineno____doc__r__static_attributes__ __classcell__)r"s@r rr0s ]jnrrc(V^8dQhRRRRRRRR/#)rconfigrprofiler session_idrr r )r s"r r r ;s/"I"IS"I="Ic"IVZ"Irc ^RIp^RIHpV'd V'gR#\V4p^RIHp\ V!V44PV4pVfR#^RIH pV!V!V4R, RR7pTP\T44p TP\4;_uu_4TP4RRR4\!T 4;'dT PR 4;'gTT8H# \d#p \PR YT 4Rp ? R#Rp ? ii;i \dmp \PR YT 4Rp ? TP\4;_uu_4TP4RRR4R# +'giR#;iRp ? ii;i +'giL;i TP\4;_uu_4TP4RRR4i +'gii;i;i) uTrue when a stateless (``api_server``) destination's raw session id is canonically owned by served *profile*'s own session store. A shared-listener mirror platform has no chat/thread/guild anchor a ``profile_routes`` entry could match, so the session store itself is the ownership proof: the row must exist in that profile's ``state.db`` under its own home and carry that profile's stamp (a NULL legacy stamp belongs to the store's own profile — the same rule the dashboard's session routes apply). An unserved profile, a missing row, a row stamped for another profile, or an unreadable store all fail closed. Shared by the Kanban notifier and the background-process wake path. N)PathF)_multiplex_profile_homes) SessionDBzstate.dbT) read_onlyz7wake: session ownership check unavailable for %s/%s: %sz3wake: session ownership lookup failed for %s/%s: %s profile_name) contextlibpathlibr0r gateway.runr1dictget hermes_stater2 Exceptionloggerdebug get_sessionsuppresscloser ) r,r-r.r5r0r1homer2dbexcrows &&& r session_owned_by_profilerE;se W'lG 8,V4599'B <* tDzJ.$ ?nnS_-   + + HHJ, 9 H H#''.1<Z[ [E"2D9   C >K`dlKl/1FGrtH L)&6X`aaab#;K;KTZei-DF[,\^ "7888 RS SE"i ,)>%& $W X4 XJ XRW XXX!b$ L%c#hszzBK L 9YsfADC'$C%% C'/)DD D'D<"DDD%C''D.!DDDDc V^8dQhRRRR/#)revtr8rr )r s"r r r sdtrcVPR4p\V\4'd+VUu.uFp\V\4'gKVNK upM.p\ V4;'g^p\ RV44p\ RV44pR\ VPR4;'gR4RTRT;'g WF, RV/pVPR 4'dHR V'dV^,PR R4MR 2VR &R VR&^RIHpV!R4'gRVR&VPR4;'gVPR4p \V \\34'dWR&V#uupi)zDisplay-only metadata for a persisted delegation delivery row. Mirrors ``tui_gateway.server._async_delegation_display_metadata`` (same ``display_kind`` consumer contract) without importing the TUI stack.resultsc3T"TFqPR4R9gK^xK R#5i)statusN>success completedr9.0rs& r /_delegation_display_metadata..s \WhC[0[!!W( (c3T"TFqPR4R9gK^xK R#5i)rmN>errorfailedrprqs& r rtrus T'QUU8_@S-Sqq'rv delegation_idrM task_countcompleted_count failed_counttask_failure_noticez task_failure: task_indexdelivery_noticer\rO)warning_notifications_enabled api_serverTpresentation_suppressedtotal_duration_secondsduration_seconds) r9 isinstancelistr8lensumrgateway.warning_notificationsrintfloat) ri raw_resultsrsrkr{r|r}r[rdurations & r _delegation_display_metadatarsR'')$KAKKY]A^A^+=+QAt)s E3 E3ric ,V^8dQhRRRRRRRRRR /#) rrrrRrr.rizOptional[dict]rrHr )r s"r r r s1((s(S(c(Xf(rv(rc x"V'g \R4h\VRR4p\V4'd\P!V4GRjxL MRpVf\ RV 24h\VRR4p\V4'd3\P!Wb4GRjxL pV'd \ V4p\P!VPY!\T;'g/44GRjxL \PR V4R#LLn \d\PRTRR7L~i;iLI5i) u_Persist an async-delegation completion as a durable DELIVERY row (see module docstring) WITHOUT running any agent turn. Raises on failure so the caller can release the durable claim and retry. 85957: on stateless api_server sessions the client owns the turn after ``event.complete`` — a completion must never become a new ``role=user`` prompt via the self-post (that starts an unauthorized agent turn and can cross a pending human-confirmation gate). Instead, append the completion to the session transcript as a timeline bookkeeping row (``display_kind="async_delegation_complete"`` + display metadata — the exact shape the TUI/desktop delivery path persists), WITHOUT running any agent turn. Clients polling ``GET /api/sessions/{id}/messages`` see it immediately; the pre-request repair belt folds it into the next real client turn as context. See #85957. zspersist_delegation_delivery: raw session id required to persist the completion on the api_server session transcript_ensure_session_dbNuhpersist_delegation_delivery: api_server SessionDB unavailable — cannot persist completion for session resolve_resume_session_idz6delegation delivery continuation resolve failed for %sT)exc_infoz^async delegation completion persisted as delivery row for api_server session %s (no wake turn)) r]rcallableasyncio to_thread RuntimeErrorrr;r<r=append_delegation_deliveryrinfo)rrRr.riensurerBresolverresolveds&$$$ r persist_delegation_deliveryrs9 OP P W2D 9F19&1A1AG%%f---tB zDDN<QR Rr6=H n$..xDDH ]     %%z9UVYV_V_]_9`  KKhjt+.E n LLQS]hlL m ns`A D: D 6D:DD  D+ D6)D: D:.D8/D: D#D52D:4D55D:c 0V^8dQhRRRRRRRRRRR R /#) rrrrRrr.rOr-rrrHr )r s"r r r sAGGcGCGSG=@G/<GHLGrc "V'd]\V4R8wdM\VRR4p\V4'g\RV: R24hV!W!\V4VR7GRjxL R#^RIp\\VRR4;'gR 4pVR19dR p\ \VR ^4;'gR 4p\\VR R4;'gR4p V 'g \R 4hRV9dVP R4'gRV R2pRV RV R2p RRV 2RV/p R\\VRR4;'gR4RRRRV/.RR/p VR8XdRV R &Rp ^\\4,p\V4EFpV'd1\P!\V^, ,4GRjxL VP\R!7pVPVR"7;_uu_4GRjxL pVPWV R#7;_uu_4GRjxL pVP R$8XdP\R%V 24p \"P%R&W^,V4RRR4GRjxL RRR4GRjxL KVP R'8d>VP'4GRjxL R(,p\R)V R*VP R+V 24hVP)4GRjxL \"P+R,W/^,4RRR4GRjxL RRR4GRjxL R# \R.V R/V R0V 24V hELELELMEL,LLLLnLBL4 +GRjxL 'giM;iRRR4GRjxL EK +GRjxL 'giEK;i \,TP.\03d.pTp \"P%R-Y/^,TT4Rp?EKbRp?ii;i5i)2uIPOST the wake text to the in-pod API server as a normal session turn, using the adapter's own bind host/port/key. Session continuation via ``X-Hermes-Session-Id`` is 403-gated on ``API_SERVER_KEY``, so a missing key is a hard error rather than a wake in a fresh session nobody watches. ``profile`` (a served secondary under ``gateway.multiplex_profiles``) takes the IN-PROCESS route instead of the HTTP one: the shared listener's ``/p//`` mirror authenticates with that profile's own ``API_SERVER_KEY`` — which a route-only profile legitimately does not have — and an unprefixed self-post would resume the session in the DEFAULT profile's store. The caller already holds the owner profile's runtime scope, so the turn lands in that profile's own session. A non-default profile whose adapter cannot run in-process fails closed. defaultrun_internal_session_turnNz"wake self-post for served profile zS requires in-process session delivery; refusing to self-post as the default profile)r.rRr-rO_hostrMz 127.0.0.1_porti!_api_keyzwake self-post requires API_SERVER_KEY: session continuation via X-Hermes-Session-Id is rejected (403) on an unauthenticated API server, so the wake cannot reach the target session:[]zhttp://z/v1/chat/completions AuthorizationzBearer zX-Hermes-Session-Idmodel _model_namez hermes-agentmessagesroleusercontentstreamFr\hermes_notification_category)total)timeout)jsonheadersiz:wake self-post got HTTP 429 (concurrency cap) for session z%s; attempt %d/%di:Ni,Nz"wake self-post failed for session z: HTTP z: z4wake self-post delivered for session %s (attempt %d)zCwake self-post transient failure for session %s (attempt %d/%d): %sz#wake self-post gave up for session z after z attempts: )z0.0.0.0z::*)rrrraiohttpr startswithr_RETRY_DELAYS_SECONDSrangersleep ClientTimeoutWAKE_TURN_TIMEOUT_SECONDS ClientSessionpostrmr<warningrRreadr TimeoutError ClientErrorOSError)rrRr.rOr- in_processrhostportapi_keyurlrpayloadlast_errattemptsattemptrhttprespbodyrCs&$$$$ r rbrbs3w<9,!'+FM  ##4WK@IIJ JJ3wRVVY=>%QG ,2>./(,H3,--H? -- 5gk BC C C C++2K+LG,,W,===99S9HHHD{{c)#/XYcXde$':HPQkS[\ IH>=={{c)&*iik 148*@ GTXT_T_S``bcgbhi))+%%KK VXbnodopIH>== #2  -j\ +V^U_`  a F2 D>H>!2&I>HHHH>===== g117; CH NN`%{Hc C C CsAO! L/!"O!(O!-O! O!(O!1O!7A7O!.L2/O!44N(L5 )N, M7 L8 M7?M  M7L; M7 N*L=+N/O!1$M L? N N NO!NO1!OO!OO!)g@g@g$@)r( __future__rrloggingtypingrr getLoggerr$r<rrr frozensetPERMANENT_REFUSAL_REASONSrrrErLrgrrrbr rr rs d#   8 $" )C&{4D&EFl"IJ  "YR"YW["Y4<"YW["YJ0(im(VGCKG?CGGr