@volter/twin-telegram 1.0.0 → 1.0.1

package/spec/patches.json

@@ -7,7 +7,7 @@
     "type": "integer",
     "description": "If the message is a reply, ID of the original message (read when reply_parameters is absent)"
    },
-   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 as Postiz calls it sends reply_to_message_id (sendMessage).",
+   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 sends reply_to_message_id (sendMessage).",
    "source": {
     "url": "https://raw.githubusercontent.com/tdlib/telegram-bot-api/e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1/telegram-bot-api/Client.cpp",
     "quote": "result.reply_to_message_id = get_message_id(query, \"reply_to_message_id\");"
@@ -20,7 +20,7 @@
     "type": "integer",
     "description": "If the message is a reply, ID of the original message (read when reply_parameters is absent)"
    },
-   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 as Postiz calls it sends reply_to_message_id (sendMessage).",
+   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 sends reply_to_message_id (sendMessage).",
    "source": {
     "url": "https://raw.githubusercontent.com/tdlib/telegram-bot-api/e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1/telegram-bot-api/Client.cpp",
     "quote": "result.reply_to_message_id = get_message_id(query, \"reply_to_message_id\");"
@@ -33,7 +33,7 @@
     "type": "integer",
     "description": "If the message is a reply, ID of the original message (read when reply_parameters is absent)"
    },
-   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 as Postiz calls it sends reply_to_message_id (sendMessage).",
+   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 sends reply_to_message_id (sendMessage).",
    "source": {
     "url": "https://raw.githubusercontent.com/tdlib/telegram-bot-api/e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1/telegram-bot-api/Client.cpp",
     "quote": "result.reply_to_message_id = get_message_id(query, \"reply_to_message_id\");"
@@ -46,7 +46,7 @@
     "type": "integer",
     "description": "If the message is a reply, ID of the original message (read when reply_parameters is absent)"
    },
-   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 as Postiz calls it sends reply_to_message_id (sendPhoto).",
+   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 sends reply_to_message_id (sendPhoto).",
    "source": {
     "url": "https://raw.githubusercontent.com/tdlib/telegram-bot-api/e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1/telegram-bot-api/Client.cpp",
     "quote": "result.reply_to_message_id = get_message_id(query, \"reply_to_message_id\");"
@@ -59,7 +59,7 @@
     "type": "integer",
     "description": "If the message is a reply, ID of the original message (read when reply_parameters is absent)"
    },
-   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 as Postiz calls it sends reply_to_message_id (sendPhoto).",
+   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 sends reply_to_message_id (sendPhoto).",
    "source": {
     "url": "https://raw.githubusercontent.com/tdlib/telegram-bot-api/e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1/telegram-bot-api/Client.cpp",
     "quote": "result.reply_to_message_id = get_message_id(query, \"reply_to_message_id\");"
@@ -72,7 +72,7 @@
     "type": "integer",
     "description": "If the message is a reply, ID of the original message (read when reply_parameters is absent)"
    },
-   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 as Postiz calls it sends reply_to_message_id (sendPhoto).",
+   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 sends reply_to_message_id (sendPhoto).",
    "source": {
     "url": "https://raw.githubusercontent.com/tdlib/telegram-bot-api/e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1/telegram-bot-api/Client.cpp",
     "quote": "result.reply_to_message_id = get_message_id(query, \"reply_to_message_id\");"
@@ -85,7 +85,7 @@
     "type": "integer",
     "description": "If the message is a reply, ID of the original message (read when reply_parameters is absent)"
    },
-   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 as Postiz calls it sends reply_to_message_id (sendVideo).",
+   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 sends reply_to_message_id (sendVideo).",
    "source": {
     "url": "https://raw.githubusercontent.com/tdlib/telegram-bot-api/e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1/telegram-bot-api/Client.cpp",
     "quote": "result.reply_to_message_id = get_message_id(query, \"reply_to_message_id\");"
@@ -98,7 +98,7 @@
     "type": "integer",
     "description": "If the message is a reply, ID of the original message (read when reply_parameters is absent)"
    },
-   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 as Postiz calls it sends reply_to_message_id (sendVideo).",
+   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 sends reply_to_message_id (sendVideo).",
    "source": {
     "url": "https://raw.githubusercontent.com/tdlib/telegram-bot-api/e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1/telegram-bot-api/Client.cpp",
     "quote": "result.reply_to_message_id = get_message_id(query, \"reply_to_message_id\");"
@@ -111,7 +111,7 @@
     "type": "integer",
     "description": "If the message is a reply, ID of the original message (read when reply_parameters is absent)"
    },
-   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 as Postiz calls it sends reply_to_message_id (sendVideo).",
+   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 sends reply_to_message_id (sendVideo).",
    "source": {
     "url": "https://raw.githubusercontent.com/tdlib/telegram-bot-api/e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1/telegram-bot-api/Client.cpp",
     "quote": "result.reply_to_message_id = get_message_id(query, \"reply_to_message_id\");"
@@ -124,7 +124,7 @@
     "type": "integer",
     "description": "If the message is a reply, ID of the original message (read when reply_parameters is absent)"
    },
-   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 as Postiz calls it sends reply_to_message_id (sendDocument).",
+   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 sends reply_to_message_id (sendDocument).",
    "source": {
     "url": "https://raw.githubusercontent.com/tdlib/telegram-bot-api/e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1/telegram-bot-api/Client.cpp",
     "quote": "result.reply_to_message_id = get_message_id(query, \"reply_to_message_id\");"
@@ -137,7 +137,7 @@
     "type": "integer",
     "description": "If the message is a reply, ID of the original message (read when reply_parameters is absent)"
    },
-   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 as Postiz calls it sends reply_to_message_id (sendDocument).",
+   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 sends reply_to_message_id (sendDocument).",
    "source": {
     "url": "https://raw.githubusercontent.com/tdlib/telegram-bot-api/e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1/telegram-bot-api/Client.cpp",
     "quote": "result.reply_to_message_id = get_message_id(query, \"reply_to_message_id\");"
@@ -150,7 +150,7 @@
     "type": "integer",
     "description": "If the message is a reply, ID of the original message (read when reply_parameters is absent)"
    },
-   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 as Postiz calls it sends reply_to_message_id (sendDocument).",
+   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 sends reply_to_message_id (sendDocument).",
    "source": {
     "url": "https://raw.githubusercontent.com/tdlib/telegram-bot-api/e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1/telegram-bot-api/Client.cpp",
     "quote": "result.reply_to_message_id = get_message_id(query, \"reply_to_message_id\");"
@@ -163,7 +163,7 @@
     "type": "integer",
     "description": "If the message is a reply, ID of the original message (read when reply_parameters is absent)"
    },
-   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 as Postiz calls it sends reply_to_message_id (sendMediaGroup).",
+   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 sends reply_to_message_id (sendMediaGroup).",
    "source": {
     "url": "https://raw.githubusercontent.com/tdlib/telegram-bot-api/e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1/telegram-bot-api/Client.cpp",
     "quote": "result.reply_to_message_id = get_message_id(query, \"reply_to_message_id\");"
@@ -176,7 +176,7 @@
     "type": "integer",
     "description": "If the message is a reply, ID of the original message (read when reply_parameters is absent)"
    },
-   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 as Postiz calls it sends reply_to_message_id (sendMediaGroup).",
+   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 sends reply_to_message_id (sendMediaGroup).",
    "source": {
     "url": "https://raw.githubusercontent.com/tdlib/telegram-bot-api/e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1/telegram-bot-api/Client.cpp",
     "quote": "result.reply_to_message_id = get_message_id(query, \"reply_to_message_id\");"
@@ -189,7 +189,7 @@
     "type": "integer",
     "description": "If the message is a reply, ID of the original message (read when reply_parameters is absent)"
    },
-   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 as Postiz calls it sends reply_to_message_id (sendMediaGroup).",
+   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, and node-telegram-bot-api 0.66.0 sends reply_to_message_id (sendMediaGroup).",
    "source": {
     "url": "https://raw.githubusercontent.com/tdlib/telegram-bot-api/e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1/telegram-bot-api/Client.cpp",
     "quote": "result.reply_to_message_id = get_message_id(query, \"reply_to_message_id\");"
@@ -207,7 +207,7 @@
      "type": "integer"
     }
    },
-   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, in the query string as in the body, and node-telegram-bot-api 0.66.0 as Postiz calls it sends reply_to_message_id (sendMessage).",
+   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, in the query string as in the body, and node-telegram-bot-api 0.66.0 sends reply_to_message_id (sendMessage).",
    "source": {
     "url": "https://raw.githubusercontent.com/tdlib/telegram-bot-api/e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1/telegram-bot-api/Client.cpp",
     "quote": "result.reply_to_message_id = get_message_id(query, \"reply_to_message_id\");"
@@ -225,7 +225,7 @@
      "type": "integer"
     }
    },
-   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, in the query string as in the body, and node-telegram-bot-api 0.66.0 as Postiz calls it sends reply_to_message_id (sendPhoto).",
+   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, in the query string as in the body, and node-telegram-bot-api 0.66.0 sends reply_to_message_id (sendPhoto).",
    "source": {
     "url": "https://raw.githubusercontent.com/tdlib/telegram-bot-api/e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1/telegram-bot-api/Client.cpp",
     "quote": "result.reply_to_message_id = get_message_id(query, \"reply_to_message_id\");"
@@ -243,7 +243,7 @@
      "type": "integer"
     }
    },
-   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, in the query string as in the body, and node-telegram-bot-api 0.66.0 as Postiz calls it sends reply_to_message_id (sendVideo).",
+   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, in the query string as in the body, and node-telegram-bot-api 0.66.0 sends reply_to_message_id (sendVideo).",
    "source": {
     "url": "https://raw.githubusercontent.com/tdlib/telegram-bot-api/e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1/telegram-bot-api/Client.cpp",
     "quote": "result.reply_to_message_id = get_message_id(query, \"reply_to_message_id\");"
@@ -261,7 +261,7 @@
      "type": "integer"
     }
    },
-   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, in the query string as in the body, and node-telegram-bot-api 0.66.0 as Postiz calls it sends reply_to_message_id (sendDocument).",
+   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, in the query string as in the body, and node-telegram-bot-api 0.66.0 sends reply_to_message_id (sendDocument).",
    "source": {
     "url": "https://raw.githubusercontent.com/tdlib/telegram-bot-api/e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1/telegram-bot-api/Client.cpp",
     "quote": "result.reply_to_message_id = get_message_id(query, \"reply_to_message_id\");"
@@ -279,7 +279,7 @@
      "type": "integer"
     }
    },
-   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, in the query string as in the body, and node-telegram-bot-api 0.66.0 as Postiz calls it sends reply_to_message_id (sendMediaGroup).",
+   "why": "The page lists only reply_parameters, but the Bot API server still reads reply_to_message_id (and allow_sending_without_reply) when a request carries no reply_parameters, in the query string as in the body, and node-telegram-bot-api 0.66.0 sends reply_to_message_id (sendMediaGroup).",
    "source": {
     "url": "https://raw.githubusercontent.com/tdlib/telegram-bot-api/e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1/telegram-bot-api/Client.cpp",
     "quote": "result.reply_to_message_id = get_message_id(query, \"reply_to_message_id\");"

package/spec/sources.json

@@ -1,4 +1,12 @@
 {
+  "https://core.telegram.org/api/files": {
+    "status": 200,
+    "checked": "2026-10-15",
+    "quotes": {
+      "s - Server-side resized image, bounded by 100x100 pixels.": true,
+      "w - Server-side resized image, bounded by 2560x2560 pixels.": true
+    }
+  },
   "https://core.telegram.org/bots/api#accent-colors": {
     "status": 200,
     "checked": "2026-10-02",
@@ -355,6 +363,13 @@
       "Wrong file identifier/HTTP URL specified": true
     }
   },
+  "https://raw.githubusercontent.com/tdlib/td/42e6a5259551178d1dab54a22ad96d14bd906e20/td/telegram/PhotoSize.cpp": {
+    "status": 200,
+    "checked": "2026-10-15",
+    "quotes": {
+      "get_photo_sizes_object": true
+    }
+  },
   "https://raw.githubusercontent.com/tdlib/telegram-bot-api/e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1/telegram-bot-api/Client.cpp": {
     "status": 200,
     "checked": "2026-10-02",

package/src/cli.ts

@@ -8,7 +8,7 @@ const [cmd, ...rest] = process.argv.slice(2);
 const port = Number(optionValue(rest, '--port', '0')) || undefined;
 const root = optionValue(rest, '--root') || undefined;
 const readOnly = hasFlag(rest, '--read-only');
-// the World's managed Postgres, which the runtime binds a pack declaring managedDatabase to
+// the selected twin's private Postgres, which the runtime binds a pack declaring managedDatabase to
 const database = optionValue(rest, '--database') || undefined;
 // the World's scenario file, for a model vendor's turns
 const scenarioPath = optionValue(rest, '--scenario') || undefined;

package/src/engine/media.ts

@@ -1,67 +1,30 @@
-// What Telegram reads from an uploaded file's own bytes: an image's width and height (a PhotoSize), and a video's width,
-// height and duration (a Video), each from the format's header as that format defines it. Pure computation over bytes.
+// Telegram's format acceptance and presentation policy over the shared file-header facts.
+import { readImageHeader, readMp4Header } from '@volter/world-core';
 
-export type ImageSize = { width: number; height: number; mime: string };
-export type VideoInfo = { width: number; height: number; duration: number };
-
-const u16be = (b: Uint8Array, i: number): number => (b[i]! << 8) | b[i + 1]!;
-const u32be = (b: Uint8Array, i: number): number => ((b[i]! << 24) >>> 0) + (b[i + 1]! << 16) + (b[i + 2]! << 8) + b[i + 3]!;
-const u16le = (b: Uint8Array, i: number): number => b[i]! | (b[i + 1]! << 8);
-const ascii = (b: Uint8Array, i: number, n: number): string => String.fromCharCode(...b.subarray(i, i + n));
-
-/** An image's size from its header: PNG (IHDR), GIF (logical screen), JPEG (the first start-of-frame); undefined for
- *  anything else (a photo Telegram takes is a .jpg, .jpeg, .gif, .png, .tif or .bmp, MessagesManager.cpp's
- *  PHOTO_EXT_INVALID; the twin reads the first three). */
-export function imageSize(b: Uint8Array): ImageSize | undefined {
-  if (b.length >= 24 && b[0] === 0x89 && ascii(b, 1, 3) === 'PNG' && ascii(b, 12, 4) === 'IHDR') return { width: u32be(b, 16), height: u32be(b, 20), mime: 'image/png' };
-  if (b.length >= 10 && ascii(b, 0, 3) === 'GIF') return { width: u16le(b, 6), height: u16le(b, 8), mime: 'image/gif' };
-  // a JPEG's markers are walked to its first frame header; a JPEG with none, like any other file, has no size
-  const jpeg = b.length >= 4 && b[0] === 0xff && b[1] === 0xd8;
-  for (let i = 2; jpeg && i + 9 < b.length; i += b[i] !== 0xff ? 1 : jpegStep(b, i)) {
-    const marker = b[i + 1]!;
-    // SOF0-SOF15 but DHT (C4), JPG (C8) and DAC (CC) carry the frame's height and width
-    if (b[i] === 0xff && marker >= 0xc0 && marker <= 0xcf && marker !== 0xc4 && marker !== 0xc8 && marker !== 0xcc) return { height: u16be(b, i + 5), width: u16be(b, i + 7), mime: 'image/jpeg' };
-  }
-  return undefined;
+/** Telegram reads PNG's IHDR, GIF's logical screen and JPEG's first frame; other formats have no photo size. */
+export function imageSize(bytes: Uint8Array): { width: number; height: number } | undefined {
+  const image = readImageHeader(bytes);
+  if (!image || image.type === 'image/webp') return undefined;
+  if (image.type === 'image/png' && String.fromCharCode(...bytes.subarray(12, 16)) !== 'IHDR') return undefined;
+  if (image.type === 'image/jpeg' && (!image.jpeg || image.jpeg.frameEnd >= bytes.length)) return undefined;
+  return { width: image.width, height: image.height };
 }
 
-/** How far a JPEG's marker at `i` reaches: a marker with no length (SOI, TEM, RSTn) is its two bytes, any other its
- *  length after them. */
-const jpegStep = (b: Uint8Array, i: number): number => {
-  const marker = b[i + 1]!;
-  return marker === 0xd8 || marker === 0x01 || (marker >= 0xd0 && marker <= 0xd7) ? 2 : 2 + u16be(b, i + 2);
-};
-
-/** An MP4's (ISO base media) duration in whole seconds from its movie header (mvhd), and the first track with a size
- *  from its track header (tkhd: 16.16 fixed-point width and height); undefined for a file that is not one. */
-export function mp4Info(b: Uint8Array): VideoInfo | undefined {
-  if (b.length < 12 || ascii(b, 4, 4) !== 'ftyp') return undefined;
+/** Whole-second duration from the last usable movie header, and the first track whose floored width is nonzero. */
+export function mp4Info(bytes: Uint8Array): { width: number; height: number; duration: number } | undefined {
+  if (bytes.length < 12) return undefined;
+  const file = readMp4Header(bytes);
+  if (!file.fileType) return undefined;
   let duration: number | undefined;
   let width = 0;
   let height = 0;
-  const walk = (start: number, end: number): void => {
-    let i = start;
-    while (i + 8 <= end) {
-      let size = u32be(b, i);
-      const type = ascii(b, i + 4, 4);
-      let header = 8;
-      if (size === 1 && i + 16 <= end) { size = u32be(b, i + 8) * 2 ** 32 + u32be(b, i + 12); header = 16; }
-      if (size === 0) size = end - i;
-      if (size < header || i + size > end) return;
-      if (type === 'moov' || type === 'trak') walk(i + header, i + size);
-      else if (type === 'mvhd') {
-        const v = b[i + header]!;
-        const timescale = v === 1 ? u32be(b, i + header + 20) : u32be(b, i + header + 12);
-        const units = v === 1 ? u32be(b, i + header + 24) * 2 ** 32 + u32be(b, i + header + 28) : u32be(b, i + header + 16);
-        if (timescale) duration = Math.round(units / timescale);
-      } else if (type === 'tkhd' && !width) {
-        const v = b[i + header]!;
-        const at = i + header + (v === 1 ? 88 : 76);
-        if (at + 8 <= i + size) { width = u32be(b, at) >>> 16; height = u32be(b, at + 4) >>> 16; }
-      }
-      i += size;
+  for (const movie of file.movies) {
+    for (const header of movie.headers) {
+      if (header.timescale) duration = Math.round(header.duration / header.timescale);
+    }
+    for (const track of movie.tracks) {
+      if (!width) { width = Math.floor(track.width); height = Math.floor(track.height); }
     }
-  };
-  walk(0, b.length);
+  }
   return duration === undefined ? undefined : { width, height, duration };
 }

package/src/engine/text.ts

@@ -351,7 +351,7 @@ export function parseMarkdown(input: string): Formatted | { error: string } {
 }
 
 /** Entities in TDLib's order: by offset, the longer first. */
-export function sortEntities(entities: Entity[]): Entity[] {
+function sortEntities(entities: Entity[]): Entity[] {
   return [...entities].sort((a, b) => a.offset - b.offset || b.length - a.length);
 }
 
@@ -362,7 +362,7 @@ const isWord = (ch: string | undefined): boolean => ch !== undefined && WORD.tes
  *  inside a word), bot commands (/command, 1-64, optionally @bot), hashtags (#tag with a letter), cashtags ($ABC),
  *  links (http, https, or www.) and e-mail addresses. Where the twin stops: TDLib's own link matcher also takes bare
  *  domains by their top-level domain, and finds bank card numbers; the twin does not. */
-export function findEntities(text: string, skipBotCommands: boolean): Entity[] {
+function findEntities(text: string, skipBotCommands: boolean): Entity[] {
   const found: Entity[] = [];
   const scan = (re: RegExp, type: string, ok: (m: RegExpExecArray) => boolean = () => true): void => {
     for (const m of text.matchAll(re)) {

package/src/index.ts

@@ -1,5 +1,6 @@
 // @volter/twin-telegram — the telegram twin (Protocol 3). A fixed file (create-pack): the descriptor is the manifest's, and the
-// kernel derives the vendor-backed half from the generated surface (architecture, "The real-system adapters").
+// kernel derives the vendor-backed half from the generated surface, unless the manifest declares none (vendorBacked.none;
+// architecture, "The real-system adapters").
 import { packOf, registerPack, type DerivedSurface } from '@volter/world-core';
 import { manifest } from './manifest.ts';
 import surface from './generated/surface.gen.json' with { type: 'json' };

package/src/manifest.ts

@@ -46,11 +46,12 @@ export const manifest: DerivedManifest = {
     // a Telegram account, a person's or a bot's, stored as the Bot API answers a User; its id is an integer the vendor
     // assigns, kept as the subject's id and as its own `id`
     // source: https://core.telegram.org/bots/api#user "Unique identifier for this user or bot."
-    user: { idPrefix: '58104400', ids: '{prefix}{n}', refresh: { none: 'the Bot API reads no user by id and lists none: getMe answers the bot itself, and a person is seen only in the messages and updates that name them' } },
+    user: { idPrefix: '58104400', ids: '{prefix}{n}', unique: [{ fields: ['_username'], refusal: { status: 409, message: 'This username is taken.' } }], refresh: { none: 'the Bot API reads no user by id and lists none: getMe answers the bot itself, and a person is seen only in the messages and updates that name them' } },
     // a chat as getChat answers it (ChatFullInfo); a private chat's id is its person's, a group's and a channel's are
     // the vendor's negative ids (minted by the doors that make them)
     // source: https://core.telegram.org/bots/api#chat "Unique identifier for this chat."
-    chat: { idPrefix: '', ...states.chat, refresh: { get: 'getChat', known: true, query: { chat_id: '{id}' } } },
+    // source: https://raw.githubusercontent.com/tdlib/telegram-bot-api/e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1/telegram-bot-api/Client.cpp "Bad Request: chat not found"
+    chat: { idPrefix: '', ...states.chat, refresh: { get: 'getChat', known: true, query: { chat_id: '{id}' }, gone: { status: 400, says: 'chat not found' } } },
     // one subject per member of a chat, `<chat>:<user>`, stored as getChatMember answers it
     chat_member: { idPrefix: '', ...states.chat_member, refresh: { none: 'the Bot API lists only administrators (getChatAdministrators), and getChatMember reads one member by a user id the World learns only from updates' } },
     // a message, `<chat>:<message_id>`; its message_id counts per chat
@@ -63,7 +64,7 @@ export const manifest: DerivedManifest = {
     // source: https://core.telegram.org/bots/api#file "Unique identifier for this file, which is supposed to be the same over time and for different bots."
     file: { idPrefix: 'AgAD', ids: '{prefix}{letters:12}', refresh: { none: 'getFile reads a file by a file_id the World learns only from messages, and its answer is the download path, not the file' } },
     // a bot's own keeping: its token's SHA-256 and its owner, its updates' counter and the allowed_updates it last asked for
-    _bot: { idPrefix: '' },
+    _bot: { idPrefix: '', unique: [{ fields: ['id'], refusal: { status: 409, message: 'This bot already has credentials.' } }] },
     // the ids the vendor assigns to a basic group and to a channel or supergroup, and a file's download path
     _group: { idPrefix: '-49870000', ids: '{prefix}{n}' },
     _channel: { idPrefix: '-10019876540', ids: '{prefix}{n}' },
@@ -98,15 +99,15 @@ export const manifest: DerivedManifest = {
     bin: 'world-telegram',
     resources: ['user', 'chat', 'chat_member', 'message', 'update', 'file'],
     specSource: 'the Telegram Bot API page (https://core.telegram.org/bots/api, Bot API 10.3), written as OpenAPI in spec/ (provenance in spec/SOURCE.md)',
-    description: "Telegram Bot API twin — a bot's updates by long polling, its messages (text, HTML, MarkdownV2, photos, videos, documents, albums), chats, members and files, as Volter Harness's Chat SDK channel and Postiz call them.",
+    description: "Telegram Bot API twin — a bot's updates by long polling, its messages (text, HTML, MarkdownV2, photos, videos, documents, albums), chats, members and files, as Volter Harness's Chat SDK channel calls them.",
     adoption: { sdks: ['@chat-adapter/telegram', 'node-telegram-bot-api', 'telegraf'], envStems: ['TELEGRAM'] },
     // the libraries above name Telegram in an application; none is Telegram's own
     // source: https://core.telegram.org/bots/samples "these projects are not maintained by Telegram"
-    clientCasesNone: 'Telegram publishes no client library of its own (its samples page lists libraries others maintain): the demand applications call the Bot API through the Chat SDK adapter (Volter Harness) and node-telegram-bot-api (Postiz)',
+    clientCasesNone: 'Telegram publishes no client library of its own (its samples page lists libraries others maintain): the demand applications call the Bot API through the Chat SDK adapter (Volter Harness)',
     hosts: [{ host: 'api.telegram.org' }],
     // the Chat SDK's adapter reads TELEGRAM_API_BASE_URL as its API's base URL (@chat-adapter/telegram 4.39.0, dist/index.js:1039)
     endpointEnv: { name: 'TELEGRAM_API_BASE_URL', note: "the Chat SDK's Telegram adapter reads it as its API base (@chat-adapter/telegram 4.39.0, dist/index.js:1039); node-telegram-bot-api takes a baseApiUrl option only, and reaches the twin by its host" },
-    credentialDoor: { path: '/_twin/bots', body: {}, fill: { TELEGRAM_BOT_TOKEN: 'token', TELEGRAM_TOKEN: 'token', TELEGRAM_BOT_USERNAME: 'username', TELEGRAM_BOT_NAME: 'username' } },
+    credentialDoor: { account: { field: 'account', tenancy: 'Telegram person', source: 'https://core.telegram.org/bots/features#botfather' }, deployment: { field: 'deployment', object: 'Bot', source: 'https://core.telegram.org/bots/features#botfather' },  path: '/_twin/bots', body: {}, fill: { TELEGRAM_BOT_TOKEN: 'token', TELEGRAM_TOKEN: 'token', TELEGRAM_BOT_USERNAME: 'username', TELEGRAM_BOT_NAME: 'username' } },
     // the bot token rides in the path, after /bot (the API's) or /file/bot (a file's download)
     // source: https://core.telegram.org/bots/api#making-requests "https://api.telegram.org/bot<token>/METHOD_NAME"
     auth: { in: 'path', pattern: '/(?:file/)?bot([^/]+)/' },

package/src/semantics/available-methods.ts

@@ -4,7 +4,7 @@ import type { HandlerContext } from '@volter/world-core';
 import { imageSize, mp4Info } from '../engine/media.ts';
 import {
   answer, botOf, chatFor, chatFullView, fileBytes, fileById, formatted, jsonParam, memberKey, memberView, messageView, param,
-  refuse, replyTarget, storeBotMessage, storeFile, textFields, uploadOf, type Row, type Upload,
+  refuse, replyTarget, storeBotMessage, storeFile, photoThumbnails, textFields, uploadOf, type Row, type Upload,
 } from './shared.ts';
 
 // source: https://core.telegram.org/bots/api#sendmessage "Text of the message to be sent, 1-4096 characters after entities parsing"
@@ -50,11 +50,14 @@ function captionOf(ctx: HandlerContext, caption: unknown, parseMode: unknown, en
   return textFields(text, 'caption');
 }
 
-/** A medium's fields on its message, from an upload or a file sent again: a photo's one size, a video's size and
- *  length, a document's name and type. */
-async function mediaFields(ctx: HandlerContext, botId: number, kind: 'photo' | 'video' | 'document', upload: Upload, given: { width?: unknown; height?: unknown; duration?: unknown }): Promise<Row | { refusal: Response }> {
-  const operation = ctx.call.operation.id;
-  let file: Row;
+type MediaKind = 'photo' | 'video' | 'document';
+type PreparedMedia = { upload: Upload; bytes: Uint8Array } & (
+  { kind: 'photo'; size: { width: number; height: number } } |
+  { kind: 'video' | 'document'; fields: Row }
+);
+
+/** Read and validate a medium without creating files, thumbnails or messages. */
+async function prepareMedia(ctx: HandlerContext, kind: MediaKind, upload: Upload, given: { width?: unknown; height?: unknown; duration?: unknown }): Promise<PreparedMedia | { refusal: Response }> {
   let bytes: Uint8Array;
   if ('file' in upload) {
     // a file sent again keeps its type: a photo is not sent as a document, nor a video as a photo
@@ -64,52 +67,59 @@ async function mediaFields(ctx: HandlerContext, botId: number, kind: 'photo' | '
     const real = types[String(upload.file._kind)] ?? 'Document';
     const wanted = kind === 'photo' ? 'Photo' : kind === 'video' ? 'Video' : 'Document';
     if (real !== wanted) return { refusal: refuse(ctx, 400, `Bad Request: can't use file of type ${real} as ${wanted}`) };
-    file = upload.file;
-    bytes = await fileBytes(ctx, file);
+    bytes = await fileBytes(ctx, upload.file);
   }
-  else {
-    bytes = upload.bytes;
-    // source: https://core.telegram.org/bots/api#sendphoto "The photo must be at most 10 MB in size."
-    // source: https://core.telegram.org/bots/api#sendvideo "Bots can currently send video files of up to 50 MB in size, this limit may be changed in the future."
-    // source: https://core.telegram.org/bots/api#senddocument "Bots can currently send files of any type of up to 50 MB in size, this limit may be changed in the future."
-    // Where the documentation stops: the words for a file over its limit are the server's for a file too big
-    // source: https://raw.githubusercontent.com/tdlib/telegram-bot-api/e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1/telegram-bot-api/Client.cpp "Bad Request: file is too big"
-    if (bytes.byteLength > (kind === 'photo' ? 10 : 50) * 1024 * 1024) return { refusal: refuse(ctx, 400, 'Bad Request: file is too big') };
-    if (kind === 'photo' && !imageSize(bytes)) {
+  else bytes = upload.bytes;
+  // source: https://core.telegram.org/bots/api#sendphoto "The photo must be at most 10 MB in size."
+  // source: https://core.telegram.org/bots/api#sendvideo "Bots can currently send video files of up to 50 MB in size, this limit may be changed in the future."
+  // source: https://core.telegram.org/bots/api#senddocument "Bots can currently send files of any type of up to 50 MB in size, this limit may be changed in the future."
+  // Where the documentation stops: the words for a file over its limit are the server's for a file too big
+  // source: https://raw.githubusercontent.com/tdlib/telegram-bot-api/e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1/telegram-bot-api/Client.cpp "Bad Request: file is too big"
+  if (!('file' in upload) && bytes.byteLength > (kind === 'photo' ? 10 : 50) * 1024 * 1024) return { refusal: refuse(ctx, 400, 'Bad Request: file is too big') };
+  const size = kind === 'photo' ? imageSize(bytes) : undefined;
+  if (!('file' in upload)) {
+    if (kind === 'photo' && !size) {
       // an upload that is no image Telegram can read: Telegram's own error for it, which the server relays as it is (its
       // second character an underscore or a capital)
       // source: https://core.telegram.org/method/messages.sendMedia "Failure while processing image."
       // source: https://raw.githubusercontent.com/tdlib/telegram-bot-api/e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1/telegram-bot-api/Client.cpp "(error_message[1] == '_' || ('A' <= error_message[1] && error_message[1] <= 'Z'))) {"
       return { refusal: refuse(ctx, 400, 'Bad Request: IMAGE_PROCESS_FAILED') };
     }
-    const size = kind === 'photo' ? imageSize(bytes)! : undefined;
     // source: https://core.telegram.org/bots/api#sendphoto "The photo's width and height must not exceed 10000 in total. Width and height ratio must be at most 20."
     // (Telegram's own error for it, relayed as it is: an MTProto error's second character is a capital)
     if (size && (size.width + size.height > 10000 || Math.max(size.width, size.height) > 20 * Math.max(1, Math.min(size.width, size.height)))) return { refusal: refuse(ctx, 400, 'Bad Request: PHOTO_INVALID_DIMENSIONS') };
-    file = await storeFile(ctx, bytes, { kind: kind === 'photo' ? 'photos' : kind === 'video' ? 'videos' : 'documents', bot: botId, ...(upload.mime ? { mime: upload.mime } : {}), ...(upload.name ? { name: upload.name } : {}) }, operation);
   }
-  const ids = { file_id: file.file_id, file_unique_id: file.file_unique_id };
-  if (kind === 'photo') {
-    const size = imageSize(bytes) ?? { width: 0, height: 0 };
-    // Where the documentation stops: the page gives a photo's sizes as "Available sizes of the photo" and names none;
-    // the twin keeps the one it was given
-    // source: https://core.telegram.org/bots/api#message "Optional. Message is a photo, available sizes of the photo"
-    return { photo: [{ ...ids, file_size: bytes.byteLength, width: size.width, height: size.height }] };
-  }
-  const name = typeof file._name === 'string' ? file._name : undefined;
-  const mime = typeof file._mime === 'string' ? file._mime : undefined;
+  if (kind === 'photo') return { kind, upload, bytes, size: size ?? { width: 0, height: 0 } };
+  const name = 'file' in upload ? upload.file._name : upload.name;
+  const mime = 'file' in upload ? upload.file._mime : upload.mime;
+  const fields = { ...(typeof name === 'string' && name ? { file_name: name } : {}), ...(typeof mime === 'string' && mime ? { mime_type: mime } : {}), file_size: bytes.byteLength };
   if (kind === 'video') {
     const info = mp4Info(bytes);
     // the request's own width, height and duration, else the file's
     // source: https://core.telegram.org/bots/api#sendvideo "Duration of sent video in seconds"
     const num = (v: unknown, fallback: number): number => (typeof v === 'number' ? v : typeof v === 'string' && /^\d+$/.test(v) ? Number(v) : fallback);
-    return { video: { ...ids, width: num(given.width, info?.width ?? 0), height: num(given.height, info?.height ?? 0), duration: num(given.duration, info?.duration ?? 0), ...(name ? { file_name: name } : {}), ...(mime ? { mime_type: mime } : {}), file_size: bytes.byteLength } };
+    return { kind, upload, bytes, fields: { width: num(given.width, info?.width ?? 0), height: num(given.height, info?.height ?? 0), duration: num(given.duration, info?.duration ?? 0), ...fields } };
   }
-  return { document: { ...ids, ...(name ? { file_name: name } : {}), ...(mime ? { mime_type: mime } : {}), file_size: bytes.byteLength } };
+  return { kind, upload, bytes, fields };
+}
+
+/** Persist a validated medium and assemble its message fields. */
+async function mediaFields(ctx: HandlerContext, botId: number, media: PreparedMedia): Promise<Row> {
+  const operation = ctx.call.operation.id;
+  const upload = media.upload;
+  const file = 'file' in upload ? upload.file : await storeFile(ctx, media.bytes, { kind: media.kind === 'photo' ? 'photos' : media.kind === 'video' ? 'videos' : 'documents', bot: botId, ...(upload.mime ? { mime: upload.mime } : {}), ...(upload.name ? { name: upload.name } : {}) }, operation);
+  const ids = { file_id: file.file_id, file_unique_id: file.file_unique_id };
+  if (media.kind === 'photo') {
+    // its smaller sizes first, then the photo as it was given
+    // source: https://core.telegram.org/bots/api#message "Optional. Message is a photo, available sizes of the photo"
+    const thumbnails = await photoThumbnails(ctx, file, media.size.width, media.size.height, operation);
+    return { photo: [...thumbnails, { ...ids, file_size: media.bytes.byteLength, ...media.size }] };
+  }
+  return { [media.kind]: { ...ids, ...media.fields } };
 }
 
 /** One medium sent to a chat with its caption. */
-async function sendMedium(ctx: HandlerContext, kind: 'photo' | 'video' | 'document'): Promise<Response> {
+async function sendMedium(ctx: HandlerContext, kind: MediaKind): Promise<Response> {
   const { id: botId } = botOf(ctx);
   const access = chatFor(ctx, botId, param(ctx, 'chat_id'), 'write');
   if ('refusal' in access) return access.refusal;
@@ -119,9 +129,10 @@ async function sendMedium(ctx: HandlerContext, kind: 'photo' | 'video' | 'docume
   if ('refusal' in caption) return caption.refusal as Response;
   const reply = replyTarget(ctx, access.chat, botId);
   if ('refusal' in reply) return reply.refusal;
-  const media = await mediaFields(ctx, botId, kind, upload, { width: param(ctx, 'width'), height: param(ctx, 'height'), duration: param(ctx, 'duration') });
+  const media = await prepareMedia(ctx, kind, upload, { width: param(ctx, 'width'), height: param(ctx, 'height'), duration: param(ctx, 'duration') });
   if ('refusal' in media) return media.refusal as Response;
-  const row = await storeBotMessage(ctx, botId, access.chat, { ...media, ...caption }, reply.key, ctx.call.operation.id);
+  const fields = await mediaFields(ctx, botId, media);
+  const row = await storeBotMessage(ctx, botId, access.chat, { ...fields, ...caption }, reply.key, ctx.call.operation.id);
   return answer(messageView(ctx, row));
 }
 
@@ -164,21 +175,22 @@ export async function sendMediaGroup(ctx: HandlerContext): Promise<Response> {
   const reply = replyTarget(ctx, access.chat, botId);
   if ('refusal' in reply) return reply.refusal;
   // every part checked before any is sent
-  const prepared: Array<{ kind: 'photo' | 'video' | 'document'; upload: Upload; caption: Row; item: Row }> = [];
+  const prepared: Array<{ media: PreparedMedia; caption: Row }> = [];
   for (const item of items) {
     const upload = uploadOf(ctx, item.media, botId);
     if ('refusal' in upload) return upload.refusal;
     const caption = captionOf(ctx, item.caption, item.parse_mode, item.caption_entities);
     if ('refusal' in caption) return caption.refusal as Response;
-    prepared.push({ kind: item.type as 'photo' | 'video' | 'document', upload, caption, item });
+    const medium = await prepareMedia(ctx, item.type as MediaKind, upload, { width: item.width, height: item.height, duration: item.duration });
+    if ('refusal' in medium) return medium.refusal;
+    prepared.push({ media: medium, caption });
   }
   // the album's one media_group_id, the World's for it
   // source: https://core.telegram.org/bots/api#message "Optional. The unique identifier inside this chat of a media message group this message belongs to"
   const group = await ctx.issue('_media_group');
   const sent: Row[] = [];
   for (const p of prepared) {
-    const fields = await mediaFields(ctx, botId, p.kind, p.upload, { width: p.item.width, height: p.item.height, duration: p.item.duration });
-    if ('refusal' in fields) return fields.refusal as Response;
+    const fields = await mediaFields(ctx, botId, p.media);
     const row = await storeBotMessage(ctx, botId, access.chat, { media_group_id: group, ...fields, ...p.caption }, reply.key, ctx.call.operation.id);
     sent.push(messageView(ctx, row));
   }
@@ -205,7 +217,7 @@ export async function getChat(ctx: HandlerContext): Promise<Response> {
   const { id: botId } = botOf(ctx);
   const access = chatFor(ctx, botId, param(ctx, 'chat_id'), 'read');
   if ('refusal' in access) return access.refusal;
-  return answer(chatFullView(ctx, access.chat));
+  return answer(chatFullView(access.chat));
 }
 
 // source: https://core.telegram.org/bots/api#getchatmember "Use this method to get information about a member of a chat."
@@ -227,6 +239,8 @@ export async function getFile(ctx: HandlerContext): Promise<Response> {
   const file = fileById(ctx, param(ctx, 'file_id'), botId);
   // source: https://raw.githubusercontent.com/tdlib/telegram-bot-api/e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1/telegram-bot-api/Client.cpp "invalid file_id"
   if (!file) return refuse(ctx, 400, 'Bad Request: invalid file_id');
+  // a thumbnail's pixels are not rendered by the twin
+  if (file._thumbnail_of !== undefined) return ctx.gap();
   // source: https://raw.githubusercontent.com/tdlib/telegram-bot-api/e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1/telegram-bot-api/Client.cpp "Bad Request: file is too big"
   if (Number(file.file_size ?? 0) > 20 * 1024 * 1024) return refuse(ctx, 400, 'Bad Request: file is too big');
   let path = typeof file.file_path === 'string' ? file.file_path : undefined;
@@ -243,9 +257,9 @@ export async function getFile(ctx: HandlerContext): Promise<Response> {
 
 // source: https://core.telegram.org/bots/api#getfile "The file can then be downloaded via the link https://api.telegram.org/file/bot<token>/<file_path> , where <file_path> is taken from the response."
 export async function downloadFile(ctx: HandlerContext): Promise<Response> {
-  botOf(ctx);
+  const { id: botId } = botOf(ctx);
   const path = String(ctx.call.params.file_path ?? '');
-  const file = ctx.rowsRaw('file').find((r) => r.deleted !== true && r.file_path === path);
+  const file = ctx.rowsRaw('file').filter((r) => r.file_path === path).map((r) => fileById(ctx, r.file_id, botId)).find((r) => r?.file_path === path);
   // source: https://raw.githubusercontent.com/tdlib/telegram-bot-api/e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1/telegram-bot-api/HttpConnection.cpp "return send_http_error(404,"
   if (!file) return refuse(ctx, 404, 'Not Found');
   const bytes = await fileBytes(ctx, file);