+ kHjk Rt^RIHt^RIt^RIHtHtHtHt^RI H t ^RI H t ^RI Ht]P!]4t]].]]]]]3,,,3,tRRltR#) aOpt-in root-DM -> fresh topic transfer for Telegram ``/topic`` mode (``dm_topic_auto_transfer``). Off by default: a root-DM message keeps the v0.22 lobby recovery and is answered in the user's most recently bound topic (#136567). With the key on, the runner's transfer hook creates a new topic and the message (and its reply) move there before session keying; if creating the topic fails, the hook answers with the lobby-recovery topic instead (#139136). ) annotationsN)Any AwaitableCallableOptional) coerce_plaintext_gateway_command) MessageEvent)replace_sourcec$V^8dQhRRRRRR/#)adapterreventrreturnNone)formats"W/home/ubuntu/.hermes/hermes-agent/plugins/platforms/telegram/telegram_topic_transfer.py __annotate__rs! % % %L %T %c:"\VRR4p\VRR4pVeVe\VRR4R8wdR#\VRR4'd \V4\VRR4'gVP4'dR#\VP;'g/P R 4;'gR 4P 4'dR#VPVPVPVP4RJdR#V!V4GRjxL pT'gR#TwrVT'g\T\T4R7TnR#\T\T4RR7TnR TnR#L\ \d\PR R R 7R#i;i5i)aRewrite ``event.source`` onto the topic the transfer hook picks; no-op when it declines. Runs at adapter ingress, before session keying, so the turn, its session and its reply all use the new topic. Commands, internal wakes, routed events and non-DM traffic are never moved. _topic_transfer_fnNsource chat_typedmallow_gateway_controlFinternalgateway_session_keyz#telegram topic transfer hook failedT)exc_info) thread_id)r message_id)getattrr get_commandstrmetadatagetstrip_is_sender_authorizeduser_idrchat_id Exceptionloggerdebugr rreply_anchor_override)r r transferrdecidedrcreateds&& rapply_root_dm_topic_transferr1sZ +2';OQU*VH UHd +F6>WV[$-OSW-Wu-u55(/uj%((E,=,=,?,? ENN b % %&; < B BCIIKK$$V^^V5E5Ev~~VZ__ ((  I %fIG "&C NtTEL"$E)  :T Js[A=FFF3F9F E2E0E2F AF0E22"FFFF)__doc__ __future__rloggingtypingrrrrgateway.platforms.basergateway.platforms.eventrgateway.session_identityr getLogger__name__r+tupler#boolTopicTransferFnr1rrrr>s\#55C03   8 $C5)HU395E,F"GGH %r