fix(telegram): set provider on native command context

Co-authored-by: Serhii Panchyshyn <panchyshyn.serhii@gmail.com>

src/telegram/bot-native-commands.session-meta.test.ts

@@ -102,10 +102,11 @@ describe("registerTelegramNativeCommands — session metadata", () => {
     expect(sessionMocks.recordSessionMetaFromInbound).toHaveBeenCalledTimes(1);
     const call = (
       sessionMocks.recordSessionMetaFromInbound.mock.calls as unknown as Array<
-        [{ sessionKey?: string; ctx?: { OriginatingChannel?: string } }]
+        [{ sessionKey?: string; ctx?: { OriginatingChannel?: string; Provider?: string } }]
       >
     )[0]?.[0];
     expect(call?.ctx?.OriginatingChannel).toBe("telegram");
+    expect(call?.ctx?.Provider).toBe("telegram");
     expect(call?.sessionKey).toBeDefined();
   });
 

src/telegram/bot-native-commands.ts

@@ -578,6 +578,7 @@ export const registerTelegramNativeCommands = ({
             SenderId: senderId || undefined,
             SenderUsername: senderUsername || undefined,
             Surface: "telegram",
+            Provider: "telegram",
             MessageSid: String(msg.message_id),
             Timestamp: msg.date ? msg.date * 1000 : undefined,
             WasMentioned: true,