feat(gateway): Telegram session-picker with inline resume buttons and recap context

[immeasurablematt]

What

Adds inline choice buttons for Telegram DM session listing (/sessions and /sessions all) with per-session resume recaps showing last user message, assistant response, and age. Improves the mobile session-resume UX by keeping context visible before the user commits to resuming a session.

Changes

• _format_telegram_sessions_picker — renders numbered context above narrow mobile-safe buttons with per-session latest-user-message excerpts
• _format_telegram_resume_recap — adds visible 'Where you left off' context after a picker-triggered resume, showing last user question + where the assistant left off
• _resume_recap_snippet / _resume_recap_age / _latest_user_context — compact helpers for excerpt formatting, relative timestamps, and reply-quotation stripping
• Integration in /sessions command — Telegram DMs get the inline picker path (guarded by chat_type == "dm" to preserve the session-ownership boundary; group chats and non-Telegram platforms keep the existing text listing)
• Adapter patch — passes metadata through send_choice_picker for correct thread routing
• Tests — exercise picker formatting output, recap age rendering (just now / minutes / hours / days / dates), and user-context extraction with reply-quotation stripping

Why

Currently, /sessions on Telegram returns a dense text list. In a DM, the user has to copy a session ID and paste it into /resume <id>. The inline picker replaces that with numbered context + tap-to-resume buttons — the same number of taps but with context the user can read before committing.

Scope

Telegram DMs only — the chat_type == "dm" guard keeps session-ownership boundaries intact. Other platforms and group chats are unaffected.

[teknium1]

Thanks for the Telegram DM resume UX improvement. The feature addresses a current gap: main still returns the text session listing at gateway/slash_commands.py:4525-4529.

Problems

• The resume picker is unsafe to reuse through the current generic Telegram picker state. The adapter stores one state object per chat at plugins/platforms/telegram/adapter.py:5664-5668, but resolves cp:<index> from that current state at plugins/platforms/telegram/adapter.py:5700-5711 without checking the callback message id. After a user opens a second /sessions picker, tapping a button on the first visible message can resume the session at the matching index from the newer picker.
• The new tests mock send_choice_picker (tests/gateway/test_resume_command.py:106-108) and directly invoke the closure, so they do not cover the Telegram callback/state-replacement path.

Suggested changes

• Bind picker state to the sent message id or a callback token and reject stale-message callbacks before invoking the resume closure registered at gateway/slash_commands.py:4701.
• Add a regression test for two pickers in one chat followed by a tap on the first message.

This is an automated hermes-sweeper review.

[teknium1]

This registers a session-switching closure in the generic picker, but Telegram keeps only one _choice_picker_state[chat_id]. Its callback handler does not validate state['msg_id'] against the clicked message, so after a second /sessions picker replaces state, a tap on the older visible picker resolves an index from the newer list and can resume the wrong session. Bind state to the picker message/token and reject stale callbacks; add a two-picker regression test.

[GottZ]

This was generated by AI during triage.

Summary

Five PRs address the Telegram session-navigation UX gap: #33702 and #33725 target a button-based bare /resume, #43695 adds a separate /sessions picker with a new-session action, #49038 adds a paginated /resume picker, and #75469 adds a Telegram-DM /sessions picker with contextual recaps and message-bound state.

Related pull requests

• Interactive Button-based Telegram Session Resume UI Improvements #33702 [closed] related — (+666/-1) — superseded prototype: Implements an authorized Telegram /resume keyboard, session filtering, and extensive tests, but also introduces unrelated cron retry and auto-pause logic. Although closed, it remains relevant as the original implementation that Interactive Button-based Telegram Session Resume UI Improvements #33725 attempted to resubmit without the scope creep.
• Interactive Button-based Telegram Session Resume UI Improvements #33725 [closed] related — (+0/-0) — empty resubmission: Contributor discussion identifies this as a scoped resubmission of Interactive Button-based Telegram Session Resume UI Improvements #33702, but the cached diff is empty and therefore preserves no implementation. Although closed, it remains relevant because it documents the intended separation of the resume UI from Interactive Button-based Telegram Session Resume UI Improvements #33702's unrelated cron changes.
• feat(telegram): add sessions picker #43695 related — (+450/-1) — superseded, security-incomplete variant: Adds a /sessions picker, resume/new-session callbacks, text fallback, and tests, but bypasses the current _resume_row_visible ownership guard, keys picker state only by chat, and targets the obsolete pre-plugin adapter path. Despite the keep_open review on feat(telegram): add sessions picker #43695, feat(gateway): Telegram session-picker with inline resume buttons and recap context #75469's diff uses the current plugin surface, limits the picker to Telegram DMs, routes selection through the existing /resume checks, and binds generic picker state to the picker message ID.
• feat(telegram): interactive resume session picker with inline keyboard #49038 related — (+186/-2) — superseded paginated variant: Adds pagination and inline /resume selection on the plugin surface, but the callback lacks authorization and visibility revalidation, uses the obsolete synchronous session-switch path, stores only one picker per chat, and has no tests. Despite the keep_open review on feat(telegram): interactive resume session picker with inline keyboard #49038, feat(gateway): Telegram session-picker with inline resume buttons and recap context #75469 preserves tap-to-resume while using the existing resume path and message-ID-bound picker state.
• feat(gateway): Telegram session-picker with inline resume buttons and recap context #75469 related — (+339/-7) — keep open with a salvage path: Adds a Telegram-DM /sessions picker, contextual previews and post-resume recaps, routes selections through /resume, and changes picker state to chat_id:message_id, addressing the contributor's stale-picker design objection. This aligns with the keep_open review, but the added two-picker test only inspects manually populated state and must exercise _handle_choice_picker_callback with two message IDs to verify actual stale-callback dispatch.

Duplicates

#33725 is the empty scoped resubmission of #33702. #43695 and #49038 substantially overlap with #75469 on Telegram inline session selection and are superseded by its current-plugin, DM-scoped, message-bound approach; #33702 is an earlier /resume-specific predecessor with unrelated cron scope.

Suggested consolidation

Keep #75469 open with a salvage path: retain its contextual Telegram-DM picker, existing /resume authorization path, and chat_id:message_id state binding, but require a two-picker regression test that invokes _handle_choice_picker_callback and proves that clicking the older message selects only its own session. Close #43695 as a duplicate of #75469 despite its keep_open review because its diff still uses the obsolete adapter location and retains ownership and stale-keyboard hazards; close #49038 as a duplicate of #75469 despite its keep_open review because its unique pagination is coupled to an unauthenticated callback, obsolete switching logic, chat-only state, and no tests. #33702 and #33725 should remain closed as superseded predecessors.

Cross-PR triage: Reviewed 5 pull requests and 0 issues in this complex. Each diff was read against this issue; Assessment working set: 81 kB of PR diffs, 7 kB of issue/PR text, 5 kB of discussion (5 comments), 0 verify verdicts. verdicts reflect diff content, not PR titles. Part of an automated triage batch.