From fe98d2614d549bcf2123da150f772b25343cf7dc Mon Sep 17 00:00:00 2001
From: thepagent <thepagent@users.noreply.github.com>
Date: Sat, 14 Mar 2026 13:09:00 +0000
Subject: [PATCH] fix: forward forceDocument in channel.ts sendPayload
 (production path)

The telegramPlugin.outbound.sendPayload in channel.ts is the actual
production path used by the plugin registry. It was not forwarding
forceDocument, making the fix in outbound-adapter.ts ineffective.

- Add forceDocument to buildTelegramSendOptions params and output
- Destructure and pass forceDocument in sendPayload

Addresses Codex review on #46119.
---
 extensions/telegram/src/channel.ts | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/extensions/telegram/src/channel.ts b/extensions/telegram/src/channel.ts
index 50509e51fca..a8745591db3 100644
--- a/extensions/telegram/src/channel.ts
+++ b/extensions/telegram/src/channel.ts
@@ -96,6 +96,7 @@ function buildTelegramSendOptions(params: {
   replyToId?: string | null;
   threadId?: string | number | null;
   silent?: boolean | null;
+  forceDocument?: boolean | null;
 }): TelegramSendOptions {
   return {
     verbose: false,
@@ -106,6 +107,7 @@ function buildTelegramSendOptions(params: {
     replyToMessageId: parseTelegramReplyToMessageId(params.replyToId),
     accountId: params.accountId ?? undefined,
     silent: params.silent ?? undefined,
+    forceDocument: params.forceDocument ?? undefined,
   };
 }
 
@@ -386,6 +388,7 @@ export const telegramPlugin: ChannelPlugin<ResolvedTelegramAccount, TelegramProb
       replyToId,
       threadId,
       silent,
+      forceDocument,
     }) => {
       const send =
         resolveOutboundSendDep<TelegramSendFn>(deps, "telegram") ??
@@ -401,6 +404,7 @@ export const telegramPlugin: ChannelPlugin<ResolvedTelegramAccount, TelegramProb
           replyToId,
           threadId,
           silent,
+          forceDocument,
         }),
       });
       return { channel: "telegram", ...result };