polygram 0.6.2 → 0.6.3

package/lib/db.js

@@ -463,6 +463,24 @@ function wrap(db) {
       return db.prepare(sql).all(...args);
     },
 
+    // Re-FK every attachment whose (chat_id, msg_id) is in `msg_ids` over
+    // to a single primary message row. Used when the media-group buffer
+    // coalesces N Telegram messages (each carrying one photo of an album)
+    // into one synthetic turn — siblings were recorded under their own
+    // msg_ids by recordInbound, but Claude needs to see them all under
+    // the primary message so handleMessage's per-message attachment
+    // lookup returns the full album.
+    reassignAttachmentsToMessage({ chat_id, msg_ids, target_message_id }) {
+      if (!Array.isArray(msg_ids) || msg_ids.length === 0) return { changes: 0 };
+      const placeholders = msg_ids.map(() => '?').join(',');
+      return db.prepare(`
+        UPDATE attachments
+           SET message_id = ?, msg_id = (SELECT msg_id FROM messages WHERE id = ?)
+         WHERE chat_id = ? AND msg_id IN (${placeholders})
+           AND message_id != ?
+      `).run(target_message_id, target_message_id, String(chat_id), ...msg_ids, target_message_id);
+    },
+
     // Look up the messages.id auto-pk for an inbound message. Used by
     // recordInbound to FK attachments to the just-inserted message even
     // when an ON-CONFLICT update happened (lastInsertRowid is 0 in that

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "polygram",
-  "version": "0.6.2",
+  "version": "0.6.3",
   "description": "Telegram daemon for Claude Code that preserves the OpenClaw per-chat session model. Migration path for OpenClaw users moving to Claude Code.",
   "main": "lib/ipc-client.js",
   "bin": {

package/polygram.js

@@ -1930,6 +1930,29 @@ function createBot(token) {
       // all-media-no-text groups.
       const primary = messages.find((m) => m.text || m.caption) || messages[0];
       const merged = messages.flatMap((m) => extractAttachments(m));
+
+      // 0.6.0 attachment-table regression fix: recordInbound (called per
+      // sibling on bot.on('message')) inserted each photo's row under its
+      // OWN msg_id. handleMessage looks up attachments via
+      // getAttachmentsByMessage(primary.message_id) — which only returns
+      // the primary's row. Without re-FK'ing the siblings we'd silently
+      // drop N-1 of N photos in any album, exactly the umi-assistant bug
+      // the user hit (saw 1 of 2 photos sent in a Telegram album).
+      const chatId = String(primary.chat.id);
+      const primaryDbId = db.getInboundMessageId({
+        chat_id: chatId, msg_id: primary.message_id,
+      });
+      const siblingMsgIds = messages
+        .filter((m) => m.message_id !== primary.message_id)
+        .map((m) => m.message_id);
+      if (primaryDbId && siblingMsgIds.length) {
+        dbWrite(() => db.reassignAttachmentsToMessage({
+          chat_id: chatId,
+          msg_ids: siblingMsgIds,
+          target_message_id: primaryDbId,
+        }), 'reassign media-group sibling attachments');
+      }
+
       const synthetic = { ...primary, _mergedAttachments: merged };
       // Carry the primary's text verbatim (dispatchRegularMessage re-cleans
       // the mention). Caption → text so downstream sees it uniformly.