+ jHjFRt^RIHt^RIt^RIt^RIt^RIt^RIt^RIH t ^RI H t ^RI H t HtHt^RIHt^RIHt^RIHt^R IHtHt^R IHt^R IHt^R IHt^R IH t ] 'd ^RI!H"t"^RI#H$t$]PJ!R4t&RRlt'RRlt(!RR4t)R#)zTelegram forum-topic and Discord auto-thread binding/rename methods for GatewayRunner (MRO mixin). ``gateway.run`` internals are imported lazily inside method bodies (import cycle), so ``patch("gateway.run.X")`` keeps intercepting them at call time.) annotationsN)suppress)Path) TYPE_CHECKINGOptionalTuple)&project_compaction_message_for_displayt)Platform)_prefix_within_utf16_limit utf16_len) MessageEvent) SessionSourcereplace_source)is_truthy_value) GatewayRunner) TurnRunnerz gateway.runcV^8dQhRR/#)returntuple)formats"7/home/ubuntu/.hermes/hermes-agent/gateway/run_topics.py __annotate__r sRReRc.\R4\R43#)zgateway.topic.restore_step_1zgateway.topic.restore_step_2r rrr_topic_restore_stepsr s , -q1O/P QQrc V^8dQhRRRR/#rtitlestrrr)rs"rrr$s]]3]3]rc\P!RR\T;'gR44P4;'g \ R4#)z\s+ gateway.topic.default_title)resubr#stripr r"s&r_collapse_titler,$s7 66&#s5;;B/ 0 6 6 8 \ \A>[<\\rc ]tRt^(tRt]RRl4tRt]RRl4tRRlt R R lt R R lt R Rlt RRlt RRltRRltRRltRRltRRltRRltRRltRR ltR!R"ltR#R$ltR%R&ltR'R(ltR)R*ltR+R,ltR-R.ltR/R0ltR1R2ltR3R4ltR5R6lt R7R8lt!R9R:lt"R;R<lt#R=R>lt$RSR@RAllt%RBRClt&RDRElt'RFRGlt(RHRIlt)RJRKlt*RLRMlt+RNROlt,RPRQlt-RRt.R?#)TGatewayTopicThreadsMixinzVTelegram forum-topic and Discord auto-thread binding/rename methods for GatewayRunner.c V^8dQhRRRR/#rsourcerrr#r)rs"rr%GatewayTopicThreadsMixin.__annotate__.sPP]PsPrc r\\VRR4;'gR4P4;'gR#)zProfile namespace for topic-mode rows: the profile stamped on the routed event, never the process-global one (under multiplex that mis-attributes state across bots sharing state.db). See #76423. profileNr&default)r#getattrr*r1s&r_telegram_topic_profile_name5GatewayTopicThreadsMixin._telegram_topic_profile_name-s1769d399r:@@BOOiOrc B\VRR4pVfR#\VRV4#)zPThe sync SessionDB handle, or None. Only for callers that provably run off-loop. _session_dbN_db)r6)self session_dbs& r_sync_session_db)GatewayTopicThreadsMixin._sync_session_db6s)T=$7 !)tUwz5*/UUrc V^8dQhRRRR/#rr1rrboolr)rs"rrr2<sQQ Q$Qrc jVP\P8H;'dVPR8H#)dm)platformr TELEGRAM chat_typer7s&r_is_telegram_dm(GatewayTopicThreadsMixin._is_telegram_dm;s*("3"33PP8H8HD8PPrc V^8dQhRRRR/#rBr)rs"rrr2?s=Trc NVPV4'dVP4MRpVfR#VP\VP4\VP 4VP V4R7pVRJ# \d\PRRR7R#i;i)z>Return whether Telegram DM topic mode is active for this chat.NFchat_iduser_id profile_namez(Failed to read Telegram topic mode stateTexc_info) rIr?is_telegram_topic_mode_enabledr#rNrOr8 Exceptionloggerdebug)r=r1r>raws&& r_telegram_topic_mode_enabled5GatewayTopicThreadsMixin._telegram_topic_mode_enabled?s040D0DV0L0LT**,RV   ;;FNN+S5H!>>vF<Cd{   LLCdL S sA A>>"B$#B$c V^8dQhRRRR/#rBr)rs"rrr2Ps  M d rc VPV4;'dFVPV4;'d-\VP;'gR4VP9#)zUTrue for the main Telegram DM (or General topic) when topic mode has made it a lobby.r&)rIrXr# thread_id_TELEGRAM_GENERAL_TOPIC_IDSr=r1s&&r_is_telegram_topic_root_lobby6GatewayTopicThreadsMixin._is_telegram_topic_root_lobbyPs]   ( P PT-N-Nv-V P PF$$**+t/O/OO rc V^8dQhRRRR/#rBr)rs"rrr2Ws  m  rc \VP;'gR4pVPV4;'d;VPV4;'d"\ V4;'dW P 9#)z9True for a user-created Telegram private-chat topic lane.r&)r#r\rIrXrCr])r=r1tids&& r_is_telegram_topic_lane0GatewayTopicThreadsMixin._is_telegram_topic_laneWsq&""((b)   ( J JT-N-Nv-V J JS  J J!)I)II rc V^8dQhRRRR/#rr1rrz Optional[str]r)rs"rrr2_s]]=]]]rc \VP;'gR4pV'dVPV4 RV 2#R#)zCooldown key (profile, chat_id): profiles sharing a Telegram private chat_id under multiplex must not suppress each other's lobby reminders / capability hints. See #76423. r&:N)r#rNr8)r=r1rNs&& r_telegram_topic_cooldown_key5GatewayTopicThreadsMixin._telegram_topic_cooldown_key_s? fnn**+KR$33F;>+; C% % 2s rc V^8dQhRRRR/#rBr)rs"rrr2us@@=@T@rc <VPVRVP4#)zXRate-limit root-DM lobby reminders to one per cooldown window, not one per prompt typed._telegram_lobby_reminder_ts)ry#_TELEGRAM_LOBBY_REMINDER_COOLDOWN_Sr^s&&r$_should_send_telegram_lobby_reminder=GatewayTopicThreadsMixin._should_send_telegram_lobby_reminderus..v7TVZV~V~rc V^8dQhRRRR/#rBr)rs"rrr2ysBBMBdBrc <VPVRVP4#)z]Rate-limit the BotFather Threads Settings screenshot (repeated /topic must not re-upload it)._telegram_capability_hint_ts)ry$_TELEGRAM_CAPABILITY_HINT_COOLDOWN_Sr^s&&r%_should_send_telegram_capability_hint>GatewayTopicThreadsMixin._should_send_telegram_capability_hintys-..v7UW[XAXAB BrcV^8dQhRR/#rrr#r)rs"rrr2s--C-rc \R4#)zgateway.topic.root_lobbyr r=s&r"_telegram_topic_root_lobby_message;GatewayTopicThreadsMixin._telegram_topic_root_lobby_messages+,,rcV^8dQhRR/#rr)rs"rrr2s++#+rc \R4#)zgateway.topic.root_newr rs&r _telegram_topic_root_new_message9GatewayTopicThreadsMixin._telegram_topic_root_new_messages)**rc V^8dQhRRRR/#rgr)rs"rrr2s___=_rc JVPV4'd \R4#R#)zgateway.topic.new_headerN)rdr r^s&&r_telegram_topic_new_header3GatewayTopicThreadsMixin._telegram_topic_new_headers$040L0LV0T0Tq+,^Z^^rcV^8dQhRR/#rr)rs"rrr2s''3'rc \R4#)zgateway.topic.helpr rs&r_telegram_topic_help_text2GatewayTopicThreadsMixin._telegram_topic_help_texts%&&rc V^8dQhRRRR/#rr1rrNoner)rs"rrr2s   ]  VZ  rc  tVP4pVe%VP'dVP'gR#TP\ VP4\ VP4\ VP ;'gR4VP VPVPV4R7R#)zPPersist the Telegram topic -> Hermes session binding for topic lanes (off-loop).Nr&)rNr\rO session_key session_idrP) r?rNr\bind_telegram_topicr#rOrrr8)r=r1 session_entryr>s&&& r_record_telegram_topic_binding7GatewayTopicThreadsMixin._record_telegram_topic_bindings**,  V^^^6;K;K;K &&'3v7G7G3HRUV\VdVdVjVjhjRk%11m>V>V::6B ' rc$V^8dQhRRRRRR/#)rr1rreasonr#rrr)rs"rrr2s( ^ ^= ^\_ ^dh ^rc VPV4'gR#VPW4R# \d\P RTRR7R#i;i)abUpdate the topic binding to ``session_entry.session_id``: a stale binding after a mid-turn compression rotation reloads the oversized parent next message, retriggering compression. Telegram topic lanes persist a (chat_id, thread_id) -> session_id row so reopening a topic in a fresh process resumes the right Hermes session. See #20470, #29712, #33414. Nz*telegram topic binding refresh failed (%s)TrQ)rdrrTrUrV)r=r1rrs&&&$r_sync_telegram_topic_binding5GatewayTopicThreadsMixin._sync_telegram_topic_bindingsQ++F33  ^  / / F ^ LLEvX\L ] ^s.#AAc V^8dQhRRRR/#rgr)rs"rrr2s>> >->rc VVPV4'dR#VPV4#)uAdapter-ingress recovery hook (sync, called off-loop before session keying): lobby recovery, except when ``dm_topic_auto_transfer`` is on — then the root-DM source is left alone so ``_transfer_telegram_root_dm`` can open a fresh topic (and fall back to this recovery itself).N)%_telegram_topic_auto_transfer_enabled!_recover_telegram_lobby_thread_idr^s&&r!_recover_telegram_topic_thread_id:GatewayTopicThreadsMixin._recover_telegram_topic_thread_ids)  5 5f = =55f==rc V^8dQhRRRR/#rgr)rs"rrr2s -rc VPV4'd<VP'd*VP'dVPV4'gR#\ VP ;'gR4pV'dW P 9dR#VP4pVfR#VP\ VP4VPV4R7pT;'gR Fyp\ TPR4;'gR4\ TP48XgKA\ TPR4;'gR4pT'd Yb8wdTu#Ru# R# \d\PRRR7R#i;i) aPin lobby-shaped topic-mode DM replies (missing ``message_thread_id`` or General) to the user's most-recent bound topic. Never rewrite a non-lobby, unbound thread id: a brand-new DM topic is also "unknown" until its first message is recorded. None = leave the source alone.Nr&rNrPztopic-recover: read failedTrQrOr\r)rIrNrOrXr#r\r]r?%list_telegram_topic_bindings_for_chatr8rTrUrVru)r=r1inboundr>bindingsb recovereds&& rr:GatewayTopicThreadsMixin._recover_telegram_lobby_thread_ids@ $$V,,FNNN&...44V<<f&&,,"- w&F&FF**,   !GGFNN+$:[:[\b:cHH RA155#))r*c&...AAk 2 8 8b9 $-)2FyPDP   LL5L E s%5E%%"F  F c V^8dQhRRRR/#rBr)rs"rrr2skk-kTXkrc VPV4pVe\VRR4MRp\\VRR4;'g/PR44#)zThe RECEIVING bot's ``extra.dm_topic_auto_transfer`` (default False): under multiplexing each bot owns its opt-in. Off keeps the v0.22 lobby recovery (#136567). No state.db read.Nconfigextradm_topic_auto_transfer)_delivery_adapter_forr6rru)r=r1adapter platform_cfgs&& r+_telegram_dm_topic_auto_transfer_configuredDGatewayTopicThreadsMixin._telegram_dm_topic_auto_transfer_configuredsR,,V4;B;Nww$7TX  gt D J JOOPhijjrc V^8dQhRRRR/#rBr)rs"rrr2swwMwdwrc VVPV4;'dVPV4#)zZThe key is on and ``source`` is a ``/topic``-mode root DM (reads state.db: call off-loop).)rr_r^s&&rr>GatewayTopicThreadsMixin._telegram_topic_auto_transfer_enableds'??GvvDLnLnouLvvrc V^8dQhRRRR/#)rr1rrzOptional[tuple[str, bool]]r)rs"rrr2s99}9Ic9rc "VP'dGVPV4'd0\P!VPV4GRjxL 'gR#VP V4pVe\ VRR4MRpRp\V4'd/V!\VP4\R44GRjxL pV'd:\PRVPVPV4\V4R3#\P!VP V4GRjxL pV'dVR3#R#LL~ \d\PRRR7Li;iL>5i) a[Adapter-ingress transfer hook for an opted-in root-DM message (#139136). ``(thread_id, True)``: a fresh topic was created and the turn runs there. ``(thread_id, False)``: creating it failed, so the message falls back to lobby recovery (the last bound topic). ``None``: not applicable (key off, not a topic-mode root DM) or nothing to recover to. N_create_dm_topicr'z9Failed to auto-transfer Telegram root DM into a new topicTrQzBtelegram topic auto-transfer: chat=%s user=%s root -> new topic %sF)rNrasyncio to_threadr_rr6callableintr rTrUrVinforOr#r)r=r1r create_topicr\rs&& r_transfer_telegram_root_dm3GatewayTopicThreadsMixin._transfer_telegram_root_dms2d&V&VW]&^&^$..t/Q/QSYZZZ,,V4ELEXww(:DA^b  L ! ! i".s6>>/BAFcDd"ee   KK\  Cy>4' '!++D,R,RTZ[[ %. 5!8D8[f i Xcg h i \sk)E($E(D: E(9E((D>=D<>D>E( AE('E&( E(4E(<D>>"E# E("E##E(c V^8dQhRRRR/#)rr1rrdictr)rs"rrr2stt]tttrc Za"\VPV4RR4pVe\VR4'gRR/#VP4GRjxL oR T3R llpRR/R Uu/uF qDT!T4bK upC#L) \d\ P RRR7RR/u#i;iuupi5i) z?Read Telegram private-topic capability flags via Bot API getMe._botNget_mecheckedFz1Failed to fetch Telegram getMe topic capabilitiesTrQcV^8dQhRR/#)rnamer#r)rs"rrOGatewayTopicThreadsMixin._get_telegram_topic_capabilities..__annotate__s B B Brc<\SV4'd \SV4#\SRR4p\V\4'dW9d W,#\S\4'dSP V4#R#) api_kwargsN)rqr6 isinstancerru)rrmes& r_fieldIGatewayTopicThreadsMixin._get_telegram_topic_capabilities.._fieldser4  r4(( \48J*d++0B!''#-b$#7#7266$< AT Ar)has_topics_enabledallows_users_to_create_topics)r6rrqrrTrUrV)r=r1botrkrs&& @r _get_telegram_topic_capabilities9GatewayTopicThreadsMixin._get_telegram_topic_capabilitiessd008&$G ;gc844u% % &zz|#B  B B4s:q#r:qQvayL:q#rss$ & LLLW[L \u% % &$ssF7B+A:A8A:B+#B&4B+8A::&B# B+"B##B+c V^8dQhRRRR/#rr)rs"rrr2sUU-UDUrc n"VPV4pVe VP'd\VRR4MRp\V4'gR#V!\ VP4\ R44GRjxL pT'gR#TPTP\ R4R\T4/R 7GRjxL p\TR R4p\TR R4pT'dTe\TR 4'gR#TP\ TP4\ T4RR7GRjxL R#L \ d\PRRR7R#i;iL \ d\PR RR7R#i;iL\ \ d\PRRR7R#i;i5i)zJCreate/pin the managed System topic after /topic activation when possible.Nrzgateway.topic.system_topic_namez&Failed to create Telegram System topicTrQz gateway.topic.system_topic_intror\)metadata message_idz*Failed to send Telegram System topic introrpin_chat_message)rNrdisable_notificationz)Failed to pin Telegram System topic intro) rrNr6rrr rTrUrVsendr#rqr)r=r1rrr\ send_resultrrs&& r_ensure_telegram_system_topic6GatewayTopicThreadsMixin._ensure_telegram_system_topics,,V4ELEX]c]k]k]kww(:DAqu  %%  *3v~~+>Bc@deeI   ' "D EQ\^abk^lPm!-!K!lDAJgvt,S[=O0P0P  U&&s6>>/BsS]uy&z z z%f  LLADL Q     LLEPTL U   { U LLDtL T Us'F5"F5 (D65D46D6:F5F55E!:E;E! -F5:3F -F .F 2F54D66"EF5EF5E!!"FF5FF5 F "F2.F51F22F5c V^8dQhRRRR/#rr)rs"rrr2"s U U] Ut Urc 6"VPV4p\\4P4PR, R, pVe;VP 'd)\ VR4'dVP4'gR#TPVP \V4\R4VP'dR\VP4/MRR7GRjxL R#L \d\PRR R 7R#i;i5i) zFSend the bundled BotFather Threads Settings screenshot when available.assetsz'telegram-botfather-threads-settings.jpgNsend_image_filez!gateway.topic.setup_image_captionr\)rN image_pathcaptionrz)Failed to send Telegram topic setup imageTrQ)rr__file__resolveparentrNrqexistsrr#r r\rTrUrV)r=r1rrs&& r _send_telegram_topic_setup_image9GatewayTopicThreadsMixin._send_telegram_topic_setup_image"s,,V4(^++-44x?Bkk ?&...IZ8[8[cmctctcvcv  U))3z?ANqLrAGAQAQAQ+s6+;+;'<=W[*   U LLDtL T UsIAD'DD AC0'C.(C0,D.C00"DDDDc V^8dQhRRRR/#r!r)rs"rrr22sRRCRCRrc x\V4p\V4^x8:dV#VR,P4R,#)zVBot API-safe forum topic name: names are 1-128 chars; keep room for multi-byte titles.:NuN...)r,lenrstripr=r"cleaneds&& r_sanitize_telegram_topic_title7GatewayTopicThreadsMixin._sanitize_telegram_topic_title2s4!%(g,#-wQ74=3G3G3IE3QQrc V^8dQhRRRR/#r!r)rs"rrr27sqqCqCqrc ~\V4p\V4^P8:dV#\V^M4P4R,#)zDiscord-safe thread title: the 100-char cap is measured in UTF-16 code units (emoji count double), so truncate with the UTF-16 helpers rather than Python code-point slices.r)r,r r rrs&& r_sanitize_discord_thread_title7GatewayTopicThreadsMixin._sanitize_discord_thread_title7s>"%(#G,2wp8RSZ\^8_8f8f8hkp8pprc V^8dQhRRRR/#rBr)rs"rrr2?s  = T rc VP\P8H;'diVPR8H;'dR\ \ VRR44;'d4\ VP 4;'d\ \ VRR44#)z>Return True only for Discord threads Hermes just auto-created.threadauto_thread_createdFauto_thread_initial_nameN)rFr DISCORDrHrCr6r\r^s&&r_is_discord_auto_thread_lane5GatewayTopicThreadsMixin._is_discord_auto_thread_lane?s OOx// / H HF4D4D4P H HWV%:EBC H HHLVM]M]H^ H HWV%?FG rc$V^8dQhRRRRRR/#)rr1rrr#rr)rs"rrr2Gs#% % -% VY% ^k% rc JaaSP\P8wgMSPR8wg<SP'd*SP 'gSP S4'dS#SPPV4pVfS#RVV3RllpVPpV!V4'gSPPV4pVeVPVP4MRpT;'g/PR4pRpV'dU\\\ \"4;_uu_4\$P&!\(P*!V44pRRR4V!V4'gS#\-SRVP.R7# +'giL8;i)a*source* with the auto-thread markers of the session's opening event, when that event created this same native Discord thread. Native Discord stamps the markers only on the opening event, so a later title retry on a rebuilt agent arrives unmarked. The routing entry's ``origin`` is that opening source and survives restarts. ``replace_source`` keeps the live transport owner and message id.r Nc V^8dQhRRRR/#)roriginzOptional[SessionSource]rrCr)rs"rrRGatewayTopicThreadsMixin._recover_discord_auto_thread_source..__annotate__Ws  &= $ rc<VRJ;'dE\VP4\SP48H;'dSPV4#N)r#r\r)rr=r1s&ropens_this_threadWGatewayTopicThreadsMixin._recover_discord_auto_thread_source..opens_this_threadWsOd">>s6+;+;'<FDTDT@U'U>>55f= r origin_jsonT)r r )rFr r rHr\delivered_via_upstream_relayr session_storelookup_by_session_keyr _db_for_key get_sessionrrur ValueErrorKeyError TypeErrorr from_dictjsonloadsrr ) r=r1rentryrrdbrowrWs ff& r#_recover_discord_auto_thread_source>*44TZZ_EF?$V,,  vGfGf  ?>s 7+F F" c V^8dQhRRRR/#rBr)rs"rrr2ns  ] t rc VP\P8H;'d]\VP4;'d@VP '*;'d'VP R9;'d\VRR4RJ#)u Shape-only check: a relay-delivered Discord CHANNEL event whose reply the connector MAY auto-thread (title-turn registration gate). Deliberately does NOT consult the send-result cache — before delivery the feedback can't exist; the rename lane polls it at fire time.rFT)groupchannel)rFr r rCrNr\rHr6r^s&&r_is_relay_discord_channel_lane7GatewayTopicThreadsMixin._is_relay_discord_channel_lanens OOx// / O OD4H O OQWQaQaMa O O  $88 O O >F$N rc V^8dQhRRRR/#rr1rrOptional[tuple[str, str]]r)rs"rrr2xsm@Yrc  ^RIHpVP\P8wg&VP 'd\ VRR4'gR#\ VRR4pV'd\V4R3#\ VPV4RR4p\V4'gR#\\4;_uu_4V!V!\VP 444uuRRR4# +'giR#;i)u<(thread_id, initial_name) when the RELAY connector auto-threaded our reply — the title-turn sibling of _is_discord_auto_thread_lane (whose markers only exist from turn 2 on; the title turn's source is the PARENT channel event). Preferred: the connector's per-message ``prospective_thread_id`` stamp (anchor message id == the thread it will create), exact even when several auto-threads spawn from one channel; the connector's created-name guard enforces no-clobber. Fallback: the per-chat send-result cache (older connectors), which only ever renamed the FIRST thread. )_as_thread_inforFNprospective_thread_idr&auto_thread_info_for_chat) gateway.runr4rFr r rNr6r#rrrrT)r=r1r4 prospectiveinfo_fns&& r_relay_auto_thread_info0GatewayTopicThreadsMixin._relay_auto_thread_infoxs 0 OOx// /v~~~6#A5IIf&=tD  $b) )$44V<>Y[_`   i "73v~~+>#?@! s 5!C!! C2 c V^8dQhRRRR/#r1r)rs"rrr2s-Lerc "^RIHpHpVPV4pVeV#\ VP V4RR4p\ V4'dVP'gR#V!RR4;'gRp\\4;_uu_4T!V!\VP4V4GRjxL 4uuRRR4#L +'giR#;i5i)a``_relay_auto_thread_info``, waited out until this turn delivers (the legacy send-result path can only answer once the reply is sent; the caller asks at title time, one turn early). The timeout is only a backstop for a turn that never sends: the turn's own inactivity limit.)r4 _float_envNwait_for_auto_thread_infoHERMES_AGENT_TIMEOUTi) r7r4r>r:r6rrrNrrTr#)r=r1r4r>knownwait_fntimeouts&& r_await_relay_auto_thread_info6GatewayTopicThreadsMixin._await_relay_auto_thread_infos <,,V4  L$44V<>Y[_`  3T:BBd i "V^^1Dg)N#NO! #N! s<AC!C3C "C/C 0C7 CC C  CNc ,V^8dQhRRRRRRRRRR /#) rr1rrr#r" relay_infor2rrr)rs"rrr2s=,l,l#,l14,l=@,l-,l ,lrc "Vfh\P!VPV4GRjxL 'g9VPV4'gR#VP V4GRjxL pVfR#\ VRR4'dVP V4MRp\ VRR4pVfR#VRJpV'd V^,M\VP4pVPV4p V'd.RRRVP'd\VP4MR/MR\ VRR4/p \PR Y'dR MR V 4V!W3/V BGRjxL p \PR V\V 44R#ELPELL, \d0\PR \!T4P"RR7R#\$d\P'RRR7R#i;i5i)a Best-effort semantic rename of a newly auto-created Discord thread. ``relay_info`` is the connector's (thread_id, initial_name) feedback, supplied on the title turn where the source is the parent-channel event without auto-thread markers (see _relay_auto_thread_info).Nadapters rename_threadprefer_connector_createdTparent_chat_idonly_if_current_namer z:discord auto-thread rename: thread=%s lane=%s new_title=%rrelaynativez7discord auto-thread rename result: thread=%s applied=%sz_>_ag,h&h&h66v>>#AA&IIJ!8?jRV8W8W$,,V4]a$?  $&,1:a=s6;K;K7L99%@ (/?X^XfXfXfV^^ATlp q176C]_c3de   H gHk  l)*:Y=YYG KKQSceijqer s?'i J0Z  NNNPTU\P]PfPfqu   l LL[fjL k ls)G$E; G$G$ G$#E>$AG$36G$*G$?AG$ FF$F9G$>G$F6G!9G$<G!G!G$ G!!G$c$V^8dQhRRRRRR/#)rr1rlabelr#rrr)rs"rrr2s#:::Z]:bf:rc a^RIHp\P!4pVeVP 4'dR#Tp\\4;_uu_4^RI H pV!V4pRRR4V!V!V4V\S R2R7pRV3Rllp VeVPV 4R#R# \d\ TRR4pLi;i +'giLi;i) zSchedule a best-effort rename coroutine onto the gateway loop from the auto-title thread. The source is copied so the thread never shares the live dataclass with the loop; failures are logged at debug and never propagate.)safe_schedule_threadsafe _gateway_loopNrz failed to schedule)rU log_messagecV^8dQhRR/#)rrrr)rs"rrQGatewayTopicThreadsMixin._schedule_rename_from_title_thread..__annotate__s @ @ @rc~<VP4R# \d\PRSRR7R#i;i)z %s failedTrQN)resultrTrUrV)futrZs&r_log_rename_failureXGatewayTopicThreadsMixin._schedule_rename_from_title_thread.._log_rename_failures5 @  @ [%$ ? @s #<<) r7r\rget_running_loop RuntimeErrorr6 is_closedrrTgateway.session_identityrrUadd_done_callback) r=r1 make_cororZr\loop copied_sourcerfuturerds &&&f r"_schedule_rename_from_title_thread;GatewayTopicThreadsMixin._schedule_rename_from_title_threads 9 8++-D <4>>++  i  @*62M ! * m $d6%PcGd  @ @    $ $%8 9 ) 84$7D 8 ! sB%C%C?C C c(V^8dQhRRRRRRRR/#rr1rrr#r"rrr)rs"rrr2s+  } Z] fi nr rc aaaaS'gR#RoSPV4'g/SPV4oSfSPV4'gR#SPVVVVV3RlR4R#)zJSchedule Discord auto-thread rename from the auto-title background thread.Nc.<SPVSSSR7#))rG)rW)copiedrGr=rr"s&rSGatewayTopicThreadsMixin._schedule_discord_semantic_thread_rename..s4MM EjNrzDiscord semantic thread rename)rr:r.ro)r=r1rr"rGsf&ff@r(_schedule_discord_semantic_thread_renameAGatewayTopicThreadsMixin._schedule_discord_semantic_thread_renamese  0088 55f=J!$*M*Mf*U*U //   -  rc(V^8dQhRRRRRRRR/#rrr)rs"rrr2 s+  M WZ cf ko rc aaaS'd/SPV4'dSPV4'dR#SPVVVV3RlR4R#)z>Schedule a topic rename from the auto-title background thread.Nc*<SPVSS4#r)(_rename_telegram_topic_for_session_title)rur=rr"s&rrvPGatewayTopicThreadsMixin._schedule_telegram_topic_title_rename..s4HHQ[]bcrzTelegram topic title rename)rd$_telegram_topic_auto_rename_disabledro)r=r1rr"sf&ffr%_schedule_telegram_topic_title_rename>GatewayTopicThreadsMixin._schedule_telegram_topic_title_rename sAD88@@DDmDmntDuDu  //  c ) rc V^8dQhRRRR/#rBr)rs"rrr2snn=nTnrc \VRR4pV'd9\VRR4'd&VPPVP4MRpVfR#\ \VRR4;'g/PR44#)z_``gateway.platforms.telegram.extra.disable_topic_auto_rename``; default False (auto-rename on).rN platformsFrdisable_topic_auto_rename)r6rrurFr)r=r1rrs&& rr=GatewayTopicThreadsMixin._telegram_topic_auto_rename_disabledsqx.@F7SY[fhlKmKmv''++FOObinding topic_name rename_topicrrs &&&& rr}AGatewayTopicThreadsMixin._rename_telegram_topic_for_session_titles&&t'C'CVLLLTZTbTbTbjpjzjzjz   4 4V < <  ,,V4IPI\74=*>Ebf H   &!)'3v~~3FFL\L\H]!^.$//T=$7  !  * E E/3v?O?O;P!%!B!B6!J!F!s7;;|#<#B#BCs:V ? 88?  d"7,=tDL'"3v~~+>#fN^N^J_fpqqq'640C&s,>EmmQTVfhlIm ' t&s6>>/BVYZ`ZjZjVkr|}}}YM &!% &   T_c d r~z* t&v~~QWQaQahrsss t d LLS^bL c ds%LI, LLLL/AL00I/ )L A JJ J#JJL/AK34J/5K39L; K3K3.L14J3%J1&J3*L/ J<L?JLJ"J,(L+J,,L/K31J333K0&K)'K0,K3-L/K00K33"LLLLc V^8dQhRRRR/#r0r)rs"rrr2Qs00-0TW0rc "VP'g^RIHpV!\R4R7#\ VP ;'gR4pV'g \R4#VP V4pRp\\4;_uu_4VPPT\ VP;'gR4VR7GRjxL pRRR4V'g \R 4#VPPW4R 7GRjxL TPT4pT'dRMRF9p\YR4p \!T \"4'gK'T P%TR4K; \R4#L +'giL;iL~ \d-p\PR 4\R TR 7uRp?#Rp?ii;i5i)z5Cleanly disable topic mode for a chat via /topic off.)format_session_db_unavailablez,gateway.shared.session_db_unavailable_prefix)prefixr&zgateway.topic.no_chat_idFrMNzgateway.topic.mode_not_enabledrz%Failed to disable Telegram topic modezgateway.topic.disable_failed)errorzgateway.topic.mode_disabled)r}rr)r; hermes_staterr r#rNr8rrTrSrOdisable_telegram_topic_moderU exceptionrjr6rrpop) r=r1rrNrPcurrently_enabledexc cooldown_keyrmstores && r%_disable_telegram_topic_mode_for_chat>GatewayTopicThreadsMixin._disable_telegram_topic_mode_for_chatQs| B0:h8ij jfnn**+/0 088@ ! i &*&6&6&U&UV^^-A-Ar)BQ]'V'! !!56 6 @"">>w>j j j 88@ WcSikkDD-E%&& ,-l.//#!!  k @   D E33? ? @sAGG5G ?E4E2 E4 G G)F F F G&&G!G2E44 F ?GF G!F;5G6G;GGc V^8dQhRRRR/#r0r)rs"rrr2os   RU rc "\R4R\R4R.pVPP\VP4\VP 4VP V4^ R7GRjxL pV'EdVP\R44VFp\VPR 4;'gR4P4pTPR VPR 4;'g \R 4 R VPR4;'gR R2V'dRV 2MR,4K VPR\R4.\4O\RV^,PR4R7N4M0VP\R4R\R4.\4O4RPV4#ELU \d\PRRR7.pELzi;i5i)zgateway.topic.status_enabledr&zgateway.topic.status_how_to)rNrOrPlimitNz)Failed to list unlinked Telegram sessionsTrQzgateway.topic.previous_unlinkedpreviewz- r"zgateway.topic.untitled_sessionu — `id`u — zgateway.topic.restore_onezgateway.topic.restore_examplerzgateway.topic.no_unlinkedzgateway.topic.restore_later )r r;(list_unlinked_telegram_sessions_for_userr#rNrOr8rTrUrVappendrur*extendrjoin)r=r1linessessionssessionrs&& r#_telegram_topic_root_status_message>vFbWH 8 LL<= >#gkk)4::;AAC W-TT3S1TUU[\c\g\ghl\m\s\sqs[ttuv,3wi(=$ LL"a ;<`?S?U`;QR X\H]^` a LL!78"a@]>^xauawx yyy'  LLDtL TH sZG6AG 3G4G 8G6;G6=8G66$G6 G6(B G6G $G3/G62G33G6c$V^8dQhRRRRRR/#)reventrraw_session_idr#rr)rs"rrr2s()t)t<)tY\)tad)trc "VPpVPpVPVP44GRjxL pV'dVP V4GRjxL MRpV'g\ RVP4R7#\ VPR4;'gR4R8wd \ R4#\ VPR4;'gR4\ VP48wd \ R 4#VPVR7GRjxL pVPV4pVP\ VP4\ VP4VR 7GRjxL p \ R 4p V'd!V 'dV PR 4V8wdV #VP\ VP4\ VP4\ VP4VPV4VR VR7GRjxL TP#T4GRjxL ;'gTp Rp \%\&4;_uu_4\)TP+T4GRjxL 4F_pTPR4R8wdK\-T4pTfK,TPR4'gKE\ TPR44p M RRR4\ RT R7pTT 'd\ RT R7,#R,#ELELELELEL \ dp R\ T 49dT uRp ? #hRp ? ii;iEL!L +'giL;i5i)zBRestore an existing Telegram-owned Hermes session into this topic.Nzgateway.topic.session_not_foundrr1r&telegramz"gateway.topic.not_telegram_sessionrOzgateway.topic.not_your_sessionrzgateway.topic.already_linkedrrestored)rNr\rOrr managed_moderPzalready linkedrole assistantcontentzgateway.topic.restoredr+z#gateway.topic.restored_last_message)text)r1r;resolve_session_idr*rr r#rurO#is_telegram_session_linked_to_topicr8rrNr\r_session_key_for_sourcerget_session_titlerrTreversed get_messagesr)r=rrr1r&rrlinked topic_profilecurrent_bindingalready_linkedrr"last_assistantmessage projectedresponses&&& r_restore_telegram_topic_session8GatewayTopicThreadsMixin._restore_telegram_topic_sessions   001E1E1GHH 6@z222d6>CWCWCYZ Z w{{8$** +z 99: : w{{9%++ ,FNN0C C56 6===TT99&A " = ='3v7G7G3HWd!>!  9: ?o.A.A,.OS].]! ! ((FNN+s6;K;K7LVYZ`ZhZhVi 88@Zfp*)  **:66DD* i #"//**E$EF;;v&+5B7K (Y]]9-E-E%(y)A%BN G!-U;\j1BXssprssKI2U    3s8+%%  7%F! s;ML M ML  M-7M%3M?ML AM+L,M M$A#LLL M M! M,MM"M #/MM0M:M M MML L>!L92L>3M8L99L>>MM M Mrr)/rR __module__ __qualname____firstlineno____doc__ staticmethodr8r?rIrXr_rdrjryrrrrrrrrrrrrrrrrrrrr(r.r:rDrWrorxrrr}rrr__static_attributes__rrrr.r.(s `PPV QQ"  ] @B -+_'   ^>8kw96t*U: U R q % N 8$,l`:< * n2dl0< 0)t)trr.)*r __future__rrr#loggingr(rs contextlibrpathlibrtypingrrragent.compaction_displayr agent.i18nr gateway.configr gateway.platforms.baser r gateway.platforms.eventrgateway.sessionrrirutilsrr7rgateway.run_turn_runnerr getLoggerrUrr,r.rrrrsxD#  11K#H0)3!)2   = )R]H tH tr