polygram 0.12.0-rc.2 → 0.12.0-rc.21

package/polygram.js

@@ -28,7 +28,7 @@ const {
   migrateJsonToDb, getClaudeSessionId, resolveSessionForSpawn,
 } = require('./lib/db/sessions');
 const { buildPrompt } = require('./lib/prompt');
-const { filterAttachments } = require('./lib/attachments');
+const { filterAttachments, resolveFileCaps, MAX_TOTAL_BYTES } = require('./lib/attachments');
 // 0.9.0: SDK ProcessManager is the only pm. CLI pm
 // (lib/process-manager.js) deleted in commit 6.
 // Both implementations expose the same public API (constructor +
@@ -51,7 +51,6 @@ const { extractAssistantText } = require('./lib/process/sdk-process');
 const { createChannelsToolDispatcher } = require('./lib/process/channels-tool-dispatcher');
 const { createTmuxRunner } = require('./lib/tmux/tmux-runner');
 const { sweepTmuxOrphans } = require('./lib/tmux/orphan-sweep');
-const { PollScheduler } = require('./lib/tmux/poll-scheduler');
 // rc.42: autosteer-buffer module deleted. Native SDK priority push
 // (pm.injectUserMessage) replaces the buffer + PostToolBatch detour.
 const { createAutosteeredRefs } = require('./lib/autosteered-refs');
@@ -98,6 +97,7 @@ const { startTyping } = require('./lib/telegram/typing');
 // consumer is lib/handlers/download.js.
 const { createReactionManager, classifyToolName } = require('./lib/telegram/reactions');
 const { createMediaGroupBuffer } = require('./lib/media-group-buffer');
+const { applyReactionToMessages } = require('./lib/telegram/album-reactions');
 const { classify: classifyError, detectWedgedSessionError, isTransientHttpError } = require('./lib/error/classify');
 const { createAutoResumeTracker, isAutoResumable } = require('./lib/db/auto-resume');
 const { resolveReplayWindowMs } = require('./lib/db/replay-window');
@@ -462,6 +462,10 @@ function buildSpawnContext(sessionKey) {
     threadId: threadId || null,
     label: getSessionLabel(chatConfig, threadId),
     existingSessionId,
+    // File-send outbound cap inputs: localApi (bot-level) so CliProcess can
+    // resolve the per-chat/topic outbound cap (resolveFileCaps) the same way
+    // it resolves cwd/agent. Override itself lives in chatConfig/topic.
+    localApi: !!config.bot?.apiRoot,
   };
 }
 
@@ -736,8 +740,13 @@ async function handleMessage(sessionKey, chatId, msg, bot) {
 
   if (botAllowsCommands && (text === '/model' || text === '/config' || text === '/effort')) {
     const show = text === '/effort' ? 'effort' : text === '/model' ? 'model' : 'all';
-    const info = formatConfigInfoText(chatConfig, show, sessionKey);
-    const reply_markup = buildConfigKeyboard(chatConfig, show);
+    // Resolve per-topic overrides so a topic's card shows its REAL
+    // agent/model/effort, not the chat-level default — Music topic (thread 3)
+    // showed "Agent: shumabit" instead of music-curation:music-curator
+    // (2026-06-03). getTopicConfig returns {} when there's no active topic.
+    const _cardTopicCfg = getTopicConfig(chatConfig, threadIdStr || null);
+    const info = formatConfigInfoText(chatConfig, show, sessionKey, _cardTopicCfg);
+    const reply_markup = buildConfigKeyboard(chatConfig, show, _cardTopicCfg);
     await sendReply(info, { params: { reply_markup } });
     return;
   }
@@ -755,7 +764,19 @@ async function handleMessage(sessionKey, chatId, msg, bot) {
   const sessionCtx = !pm.has(sessionKey) ? await readSessionContext(sessionKey, chatConfig.cwd) : '';
 
   const rawAtts = extractAttachments(msg);
-  const { accepted, rejected } = filterAttachments(rawAtts);
+  // Backend-derived inbound cap with per-topic/chat override. Cloud → 20MB;
+  // a local Bot API server (config.bot.apiRoot) → 2GB; override via
+  // chats[id].maxFileBytes or topics[t].maxFileBytes, clamped to the
+  // backend ceiling. Bytes-valued config; resolveFileCaps does the clamp.
+  const _inTopicCfg = getTopicConfig(chatConfig, threadIdStr || null);
+  const _fileCaps = resolveFileCaps({
+    localApi: !!config.bot?.apiRoot,
+    override: _inTopicCfg.maxFileBytes ?? chatConfig.maxFileBytes ?? null,
+  });
+  const { accepted, rejected } = filterAttachments(rawAtts, {
+    maxFileBytes: _fileCaps.inBytes,
+    maxTotalBytes: Math.max(_fileCaps.inBytes, MAX_TOTAL_BYTES),
+  });
   for (const { att, reason } of rejected) {
     console.log(`[${label}] attachment skipped: ${att.name} (${reason})`);
     logEvent('attachment-skipped', { chat_id: chatId, msg_id: msg.message_id, name: att.name, reason });
@@ -983,13 +1004,17 @@ async function handleMessage(sessionKey, chatId, msg, bot) {
   const availableEmojis = await getReactionAllowlist(bot, chatId);
   const reactor = createReactionManager({
     apply: async (emoji) => {
-      const params = {
-        chat_id: chatId,
-        message_id: msg.message_id,
-        reaction: emoji ? [{ type: 'emoji', emoji }] : [],
-      };
-      await tg(bot, 'setMessageReaction', params,
-        { source: 'status-reaction', botName: BOT_NAME });
+      // rc.16: mirror the reaction onto album siblings too, so a multi-file
+      // send shows the same status emoji on EVERY item, not just the anchor.
+      // For a normal single message, _albumSiblingMsgIds is undefined and this
+      // is exactly the prior single setMessageReaction. Anchor is awaited
+      // (failure surfaces to the reactor); siblings are best-effort.
+      await applyReactionToMessages({
+        tg, bot, chatId,
+        msgIds: [msg.message_id, ...(msg._albumSiblingMsgIds || [])],
+        emoji,
+        botName: BOT_NAME,
+      });
     },
     availableEmojis,
     logError: (m) => console.error(`[${label}] ${m}`),
@@ -1673,9 +1698,30 @@ function shouldHandle(msg, chatConfig, botUsername) {
 }
 
 function createBot(token) {
+  // Optional self-hosted Telegram Bot API server. When config.bot.apiRoot is
+  // set (e.g. "http://localhost:8081" from a local `telegram-bot-api`
+  // process), grammy routes all Bot API calls there instead of
+  // api.telegram.org — which lifts file send/receive from cloud's 50 MB-out /
+  // 20 MB-in to 2 GB both ways. Omit it (default) → cloud Telegram, unchanged.
+  // The local server is a separate companion daemon; this is just the knob
+  // that points polygram at it. See docs/0.12.0-file-send.md.
+  const apiRoot = config.bot?.apiRoot;
   const bot = new Bot(token, {
-    client: { timeoutSeconds: 60 },
+    client: {
+      // rc.15: with the local Bot API server, getFile DOWNLOADS the file
+      // synchronously (server fetches it from Telegram's DC, then responds) —
+      // a large lossless WAV can take >60s, so the cloud-tuned 60s timeout
+      // fired before the download finished (the file still landed on the
+      // server's disk, but polygram's getFile call already errored). The
+      // local server is localhost, so non-download calls stay fast; the
+      // higher ceiling only matters for big getFile downloads.
+      timeoutSeconds: apiRoot ? 180 : 60,
+      ...(apiRoot ? { apiRoot } : {}),
+    },
   });
+  if (apiRoot) {
+    console.log(`[polygram] using local Telegram Bot API server: ${apiRoot} (2GB file limit)`);
+  }
   let botUsername = '';
   // Cached once @botUsername is known — was recompiling per inbound msg.
   let mentionRe = null;
@@ -1856,6 +1902,10 @@ function createBot(token) {
       }
 
       const synthetic = { ...primary, _mergedAttachments: merged };
+      // rc.16: carry the album sibling msg_ids so the status reactor can mirror
+      // its emoji onto every item (not just the anchor) — see the reactor
+      // `apply` closure + lib/telegram/album-reactions.js.
+      if (siblingMsgIds.length) synthetic._albumSiblingMsgIds = siblingMsgIds;
       // Carry the primary's text verbatim (dispatchRegularMessage re-cleans
       // the mention). Caption → text so downstream sees it uniformly.
       if (!synthetic.text && synthetic.caption) synthetic.text = synthetic.caption;
@@ -2244,19 +2294,13 @@ async function main() {
     const binCheck = verifyPinnedClaudeBin(CLAUDE_CLI_PINNED_VERSION);
     if (binCheck.ok) {
       console.log(
-        `[polygram] tmux backend pinned to claude CLI v${CLAUDE_CLI_PINNED_VERSION}: ${binCheck.path}`,
+        `[polygram] CliProcess pinned to claude CLI v${CLAUDE_CLI_PINNED_VERSION}: ${binCheck.path}`,
       );
       pinnedClaudeBin = binCheck.path;
     } else {
       console.warn(`[polygram] WARNING: ${binCheck.reason}`);
     }
   }
-  // O1 optimization: shared poll-tick scheduler. N TmuxProcess
-  // instances share ONE setInterval instead of spawning N independent
-  // setTimeout chains. Idle when no chats are in flight (zero timers
-  // running). Configurable via config.bot.tmuxPollIntervalMs.
-  const tmuxPollIntervalMs = config.bot?.tmuxPollIntervalMs || 250;
-  const pollScheduler = new PollScheduler({ intervalMs: tmuxPollIntervalMs });
   // 0.11.0: channels backend wiring. Used when a chat opts in via
   // `pm: 'channels'` config. Falls back to SDK gracefully if the pinned
   // claude binary isn't present (see factory.js — channelsClaudeBin
@@ -2282,7 +2326,6 @@ async function main() {
     logger: console,
     tmuxRunner,
     botName: BOT_NAME,
-    pollScheduler,
     // channels backend
     toolDispatcher: channelsToolDispatcher,
     channelsClaudeBin,