Telegram plugin: surface reply_to_message context on inbound channel messages

Feature request for the official telegram plugin (v0.0.6, claude-plugins-official).

Current behavior: inbound messages reach the agent as <channel> tags with chat_id, message_id, user, ts (+ attachment fields). When the sender uses Telegram's reply-to/quote on a specific earlier message, that linkage is dropped — reply_to_message is available on the grammY context inside handleInbound but is not included in the emitted meta, so the agent cannot tell which message was quoted (and the Bot API offers no history lookup to recover it).

Use case: a user replying to one specific agent message to give follow-up context ("this one — change X") — common when an agent sends several messages in a burst. Outbound threading already works (reply_to on the reply tool); inbound is the missing half.

Proposed change (small — in handleInbound's emit meta object):

...(ctx.message?.reply_to_message != null ? {
  reply_to_message_id: String(ctx.message.reply_to_message.message_id),
  reply_to_preview: (ctx.message.reply_to_message.text
    ?? ctx.message.reply_to_message.caption
    ?? '(non-text message)').slice(0, 160),
} : {}),

The caption fallback matters for voice-message workflows where the text rides as the voice caption. Happy to provide more detail. Thanks!