+ jHjJRt^RIHt^RIt^RIt^RIt^RIt^RIHtH t H t H t ^RI H t Ht^RIHt]P"!R4tRRRlltRtR ] !4 R ]!R 4 R 2tR tRt!RR4tR#)zATelegram DM topic-mode mixin for :class:`hermes_state.SessionDB`.) annotationsN)AnyDictListOptional)_sql_preview_raw_sql_session_last_active)StateDbReplacedError hermes_statec V^8dQhRRRR/#) profile_namez Optional[str]returnstr)formats":/home/ubuntu/.hermes/hermes-agent/hermes_state_telegram.py __annotate__rs'''RU'c`\T;'gR4P4pV'dV#R#)uEmpty/missing → ``"default"`` (single namespace for non-multiplexed gateways). Multiplexed callers must pass the *routed* profile (``source.profile``), never the process-global active profile.default)rstrip)r names& r&_normalize_telegram_topic_profile_namers, |!!r " ( ( *D4&Y&rz SELECT s.*, COALESCE(sp.prompt, s.system_prompt) AS _system_prompt_resolved, z, sz AS last_active FROM sessions s LEFT JOIN system_prompts sp ON sp.hash = s.system_prompt_hash WHERE s.source = 'telegram' AND s.user_id = ? zq ORDER BY last_active DESC, s.started_at DESC LIMIT ? a  AND COALESCE(NULLIF(TRIM(s.profile_name), ''), 'default') = ? AND NOT EXISTS ( SELECT 1 FROM telegram_dm_topic_bindings b WHERE b.session_id = s.id ) c]tRt^\tRtRtRRltRRltRRltR R R R R R /RRllt R R RR/RRllt R R /RRllt R R /RRllt R R /RRllt RRltR R /RRlltRRR R /R R!lltR"R#ltR R R$^ /R%R&lltR'tR #)(SessionTelegramTopicsMixinzTelegram DM topic-mode tables, bindings and lookups. Read paths tolerate absent tables (nobody ran ``/topic``) by returning their empty value and never create them; pre-v3 tables left by an upgrade are self-healed on read.c (V!4# \Pd"pR\T49dTuRp?#Rp?MRp?ii;iTP4T!4# \P\ 3d\ PRRR7Tu#i;i)uRun ``read()``; an absent table reads as ``empty``. A pre-v3 table left by an upgrade (#103363) raises ``no such column: profile_name`` — heal it and retry, otherwise the write-only migration is never reached and topic mode silently reads as off forever.zno such column: profile_nameNzFtelegram topic tables are pre-v3 and the heal failed; reading as emptyT)exc_info)sqlite3OperationalErrorrapply_telegram_topic_migrationErrorr loggerwarning)selfreademptyexcs&&& r _topic_read&SessionTelegramTopicsMixin._topic_readas 6M'' -SX= >    / / 1v  34  NNcnrN sL s& ?:??A4BBcV^8dQhRR/#r sqlrr)rs"rr'SessionTelegramTopicsMixin.__annotate__qsKK3Krc 8aaaSPVVV3RlR4#)c(<SPSS4#N) _read_oneparamsr&r.sr.rsF(CrNr*r&r.r5sfffr_topic_read_one*SessionTelegramTopicsMixin._topic_read_oneqs CTJJrcV^8dQhRR/#r-r)rs"rrr/tsII3Irc 8aaaSPVVV3Rl.4#)c(<SPSS4#r2) _read_allr4srr6.ur8rr9r:sfffr_topic_read_all*SessionTelegramTopicsMixin._topic_read_allts CRHHrcV^8dQhRR/#)r rNoner)rs"rrr/ws+!+!+!rc 6aV3RlpSPV4R#)aCreate Telegram DM topic-mode tables on explicit /topic opt-in. Deliberately NOT part of startup reconciliation: operators can upgrade and keep the old bot behavior until a user runs /topic. Also invoked by ``_topic_read`` to heal a pre-v3 table an upgrade left behind (#103363). Schema versions: v1 initial; v2 session_id FK ON DELETE CASCADE (pruning clears bindings); v3 ``profile_name`` on both tables so multiplexed gateways sharing one state.db isolate topic state per profile. See #76423. c <\FwrpVPRV RV R24VPRV R24Uu0uF qD^,kK ppRV9dKQVPRR^4pRV9dR MRpVPR V R 24SPVP 4W R 2R V RV R2RV RV RV RV R V 2 4K VPR4VPR4VPRR4R#uupi)zCREATE TABLE IF NOT EXISTS z ()zPRAGMA table_info('z')r zprofile_name, r session_idz@ WHERE EXISTS (SELECT 1 FROM sessions s WHERE s.id = session_id)zDROP TABLE IF EXISTS _new_legacyz CREATE TABLE z INSERT INTO z) SELECT 'default', z FROM zrCREATE UNIQUE INDEX IF NOT EXISTS idx_telegram_dm_topic_bindings_session ON telegram_dm_topic_bindings(session_id)z|CREATE INDEX IF NOT EXISTS idx_telegram_dm_topic_bindings_user ON telegram_dm_topic_bindings(profile_name, user_id, chat_id)zgINSERT INTO state_meta (key, value) VALUES (?, ?) ON CONFLICT(key) DO UPDATE SET value = excluded.valueN) telegram_dm_topic_schema_version3) _TOPIC_TABLESexecutereplace_rebuild_tablecursor) conntablecolumnsddlrowhavelegacy_columnsliver&s & r_doFSessionTelegramTopicsMixin.apply_telegram_topic_migration.._dosF'4# :5'C5JK*.,,9LUGSU7V*WX*W3A*WX!T)")1A2q!I]imt]tYz| 4UG4@A##KKM5G7*;}UGSUVYUZZ[=\"5'G94HHXX^_d^eelmqlrs(5& LL<  LLP  LLH9 3YsDN)_execute_write)r&r[sf rr"9SessionTelegramTopicsMixin.apply_telegram_topic_migrationws B C rr rhas_topics_enabledNallows_users_to_create_topicsc 0V^8dQhRRRRRRRRRRRR /#) r chat_idruser_idr r_Optional[bool]r`rrEr)rs"rrr/sF ] ] ](+ ];> ]^l ]'5 ]  ]rc  VP4\P!4p\V4pRRlpVPRV\ V4\ V4WfV!V4V!V4V34R#)afEnable Telegram DM topic mode for one private chat/user. Owns the explicit topic migration; SessionDB startup must not create these tables. ``profile_name`` namespaces rows under a shared multiplex ``state.db`` (issue #76423). Callers handling a multiplexed event must pass the routed profile from ``source.profile``, not the process-global active profile. c V^8dQhRRRR/#)r valuerdrz Optional[int]r)rs"rrKSessionTelegramTopicsMixin.enable_telegram_topic_mode..__annotate__s B B> Bm Brc&VfR#V'd^#^#r2r)rgs&r_to_intFSessionTelegramTopicsMixin.enable_telegram_topic_mode.._to_ints =4 AEq Aq Ara INSERT INTO telegram_dm_topic_mode ( profile_name, chat_id, user_id, enabled, activated_at, updated_at, has_topics_enabled, allows_users_to_create_topics, capability_checked_at ) VALUES (?, ?, ?, 1, ?, ?, ?, ?, ?) ON CONFLICT(profile_name, chat_id) DO UPDATE SET user_id = excluded.user_id, enabled = 1, updated_at = excluded.updated_at, has_topics_enabled = excluded.has_topics_enabled, allows_users_to_create_topics = excluded.allows_users_to_create_topics, capability_checked_at = excluded.capability_checked_at N)r"timer _write_sqlr)r&rbrcr r_r`nowrjs&$$$$$ renable_telegram_topic_mode5SessionTelegramTopicsMixin.enable_telegram_topic_modesl ++-iik=lK  B  G c'lC,-w7T/UWZ\ ]rclear_bindingsTc(V^8dQhRRRRRRRR/#)r rbrr rqboolrrEr)rs"rrr/s,!!!-0!NR! !rc Taaa\S4oVVV3RlpVPV4R#)zDisable Telegram DM topic mode for one private chat. ``clear_bindings`` also drops the chat's bindings so a later re-enable starts clean. Never creates the tables; absent tables are a no-op.c F<\P!\P4;_uu_4VP R\ P !4S\ S434S'dVP RS\ S434RRR4R# +'giR#;i)dUPDATE telegram_dm_topic_mode SET enabled = 0, updated_at = ? WHERE profile_name = ? AND chat_id = ?zMDELETE FROM telegram_dm_topic_bindings WHERE profile_name = ? AND chat_id = ?N) contextlibsuppressr r!rOrlr)rSrbrqr s&rr[CSessionTelegramTopicsMixin.disable_telegram_topic_mode.._dosn$$W%=%=>> =YY[,G = "LLg%s7|4?>>>s AB B N)rr])r&rbr rqr[s&ddd rdisable_telegram_topic_mode6SessionTelegramTopicsMixin.disable_telegram_topic_modes$ >lK   C rc(V^8dQhRRRRRRRR/#)r rbrrcr rrsr)rs"rrr/s*:::s:Z]:nr:rc \V4pVPRV\V4\V434pVe\V^,4#R#)zDReturn whether Telegram DM topic mode is enabled for this chat/user.z SELECT enabled FROM telegram_dm_topic_mode WHERE profile_name = ? AND chat_id = ? AND user_id = ? F)rr;rrs)r&rbrcr rWs&$$$ ris_telegram_topic_mode_enabled9SessionTelegramTopicsMixin.is_telegram_topic_mode_enabledsO=lK ""$'G c'lCE #tCF|9E9rc(V^8dQhRRRRRRRR/#)r rbr thread_idr rOptional[dict[str, Any]]r)rs"rrr/s, * * **- *=@ * ! *rc \V4pVPRV\V4\V434pV'd \V4#R#)z?Return the session binding for a Telegram DM topic, if present.z SELECT * FROM telegram_dm_topic_bindings WHERE profile_name = ? AND chat_id = ? AND thread_id = ? N)rr;rdict)r&rbrr rWs&$$$ rget_telegram_topic_binding5SessionTelegramTopicsMixin.get_telegram_topic_bindingsK>lK ""$'G c)nEG tCy)T)rc$V^8dQhRRRRRR/#)r rbrr rlist[dict[str, Any]]r)rs"rrr/s$ + + +-0 +  +rc \V4pVPRV\V434pVUu.uFp\V4NK up#uupi)zFAll bindings for one chat, newest first ([] when the table is absent).zhSELECT * FROM telegram_dm_topic_bindings WHERE profile_name = ? AND chat_id = ? ORDER BY updated_at DESC)rrBrr)r&rbr rowsrWs&$$ r%list_telegram_topic_bindings_for_chat@SessionTelegramTopicsMixin.list_telegram_topic_bindings_for_chatsK>lK ## v 3w< ( &**TcS T***sAc V^8dQhRRRR/#)r rIrrrr)rs"rrr/s**3*Kc*rc dVPR\V434pV'd \V4#R#)zEReverse lookup via the UNIQUE INDEX on session_id; None when unbound.z{ SELECT * FROM telegram_dm_topic_bindings WHERE session_id = ? N)r;rrr&rIrWs&$ r%get_telegram_topic_binding_by_session@SessionTelegramTopicsMixin.get_telegram_topic_binding_by_sessions6""$j/+- tCy)T)rc(V^8dQhRRRRRRRR/#)r rbrrr rintr)rs"rrr/s*+(+(+(+([^+(or+(rc aaa\S4\S4uoo\S4oRVVV3RllpVPV4#)aRemove the binding row for one (chat, thread) pair. Called when the Bot API confirms a topic was deleted externally (``Thread not found`` after the same-thread retry failed); otherwise ``gateway.run._recover_telegram_topic_thread_id`` keeps redirecting inbound messages to the dead topic. If this removes the chat's *last* binding, ``telegram_dm_topic_mode`` is flipped to ``enabled = 0`` in the same transaction, or a user who disabled topics in the Telegram client (not via ``/topic off``) stays stuck. Returns the number of rows deleted; absent binding or unmigrated tables are silent no-ops (never raise from a cleanup hot path). Without this prune, the stale row keeps living in ``telegram_dm_topic_bindings`` and the recovery logic in ``gateway.run._recover_telegram_topic_thread_id`` cheerfully redirects future inbound messages to the deleted topic, causing tool progress, approvals, and replies to land in the wrong place. Issue #31501. cV^8dQhRR/#)r rrr)rs"rrNSessionTelegramTopicsMixin.delete_telegram_topic_binding..__annotate__s   rc<VPRSSS34P;'g^pT'g^#\P !\P4;_uu_4TPRSS34P 4pTf)TPR\P!4SS34RRR4T# \Pd^#i;i +'giT#;i)z DELETE FROM telegram_dm_topic_bindings WHERE profile_name = ? AND chat_id = ? AND thread_id = ? z SELECT 1 FROM telegram_dm_topic_bindings WHERE profile_name = ? AND chat_id = ? LIMIT 1 Nrv)rOrowcountr r!rwrxfetchonerl)rSdeleted remainingrbr rs& rr[ESessionTelegramTopicsMixin.delete_telegram_topic_binding.._dos ,,(';=>FXKKJK $$W%=%=>> LL*'023;(*$LLAlG< ?N#++   ?>Ns#%B;B;"AC;CC C( )rrr])r&rbrr r[s&ddd rdelete_telegram_topic_binding8SessionTelegramTopicsMixin.delete_telegram_topic_bindings@!\3y>=lK   2""3''r managed_modeautoc8V^8dQhRRRRRRRRRRRRRRR R /#) r rbrrrc session_keyrIrr rrEr)rs"rrr/0sN#!#!#!*-#!8;#!JM#!#!'*#!CF#! #!rc $aaaaaaaa VP4\P!4o \S4\S4\S4uooo\S4\S4uoo\S4oVVV VVVVV3RlpVP V4R#)zBind one Telegram DM topic thread to one Hermes session. A session may be linked to only one topic: rebinding the same pair is idempotent; linking the session to a different topic raises ValueError.c <VPRS 34P4pVe9Vwr#p\V4\V4\V43SSS 38wd \R4hVPRSSS S S S SSS3 4R#)z SELECT profile_name, chat_id, thread_id FROM telegram_dm_topic_bindings WHERE session_id = ? Nz3session is already linked to another Telegram topicah INSERT INTO telegram_dm_topic_bindings ( profile_name, chat_id, thread_id, user_id, session_key, session_id, managed_mode, linked_at, updated_at ) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?) ON CONFLICT(profile_name, chat_id, thread_id) DO UPDATE SET user_id = excluded.user_id, session_key = excluded.session_key, session_id = excluded.session_id, managed_mode = excluded.managed_mode, updated_at = excluded.updated_at )rOrr ValueError) rSexisting_sessionlinked_profile linked_chat linked_threadrbrrnr rIrrrcs & rr[;SessionTelegramTopicsMixin.bind_telegram_topic.._do=s#||-!]  $%-HJ   +=M:]'[)93};MNS_ahjsRtt$%Z[[ LL #GYjZfhkmpq srN)r"rlrrr]) r&rbrrcrrIrr r[rns &ddddddd @rbind_telegram_topic.SessionTelegramTopicsMixin.bind_telegram_topic0ss ++-iik&)'lC NCL#G"%k"2C O Z=lK  s s, C rc V^8dQhRRRR/#)r rIrrrsr)rs"rrr/Usrc BVPR\V434pVRJ#)uPTrue if the session is bound to any Telegram DM topic (absent tables → False).z SELECT 1 FROM telegram_dm_topic_bindings WHERE session_id = ? LIMIT 1 N)r;rrs&$ r#is_telegram_session_linked_to_topic>SessionTelegramTopicsMixin.is_telegram_session_linked_to_topicUs/""$j/+ - $rlimitc ,V^8dQhRRRRRRRRRR/#) r rbrrcr rrrrr)rs"rrr/^s4555(+5;>5SV5 5rc  &\V4pVP4;_uu_4pVP\\,\ ,\ V4V\V434P4pRRR4XUu.uFqpPV4NK up# \PdGTP\\ ,\ T4\T434P4pLi;i +'giL;iuupi)zThis user's Telegram sessions not bound to a topic. Read-only: if the bindings table is absent, every session is unlinked and the profile-unscoped query is used. Scoped by ``profile_name`` so multiplexed profiles do not surface each other. See #76423. N) r _read_ctxrO_UNLINKED_SELECT_HEAD_UNLINKED_SCOPE_CLAUSES_UNLINKED_SELECT_TAILrrfetchallr r! _rich_row)r&rbrcr rrSrrWs&$$$$ r(list_unlinked_telegram_sessions_for_userCSessionTelegramTopicsMixin.list_unlinked_telegram_sessions_for_user^s>lK ^^   ||),CCF[[\<U<(*044ts#t44 ++ ||),AACLRUV[R\C](*   5s0C;ABDAC85C;7C88C;; D r)__name__ __module__ __qualname____firstlineno____doc__r*r;rBr"rorzr~rrrrrrr__static_attributes__rrrrr\sA KI+!Z ]?H ]mq ]6: ]D!3<!UY!,:`i: *CL * +3< +*+(aj+(Z#!-3#!IR#!J5AJ5Y[55rrr2))telegram_dm_topic_modezprofile_name, chat_id, user_id, enabled, activated_at, updated_at, has_topics_enabled, allows_users_to_create_topics, capability_checked_at, intro_message_id, pinned_message_idai profile_name TEXT NOT NULL DEFAULT 'default', chat_id TEXT NOT NULL, user_id TEXT NOT NULL, enabled INTEGER NOT NULL DEFAULT 1, activated_at REAL NOT NULL, updated_at REAL NOT NULL, has_topics_enabled INTEGER, allows_users_to_create_topics INTEGER, capability_checked_at REAL, intro_message_id TEXT, pinned_message_id TEXT, PRIMARY KEY (profile_name, chat_id) )telegram_dm_topic_bindingszgprofile_name, chat_id, thread_id, user_id, session_key, session_id, managed_mode, linked_at, updated_ata: profile_name TEXT NOT NULL DEFAULT 'default', chat_id TEXT NOT NULL, thread_id TEXT NOT NULL, user_id TEXT NOT NULL, session_key TEXT NOT NULL, session_id TEXT NOT NULL REFERENCES sessions(id) ON DELETE CASCADE, managed_mode TEXT NOT NULL DEFAULT 'auto', linked_at REAL NOT NULL, updated_at REAL NOT NULL, PRIMARY KEY (profile_name, chat_id, thread_id) )r __future__rrwloggingr rltypingrrrrhermes_state_commonrrhermes_state_errorsr getLoggerr$rrNrrrrrrrrsG" ,,J4   > *'$ P*+,-1#678 V5V5r