@ada-cx/messaging-bridge 1.12.0 → 1.12.1

package/dist-npm/shared-utils/file-upload.d.ts

@@ -27,17 +27,11 @@ export declare const IMAGE_ATTACHMENT_MAX_BYTES: number;
 /**
  * How many images one send may carry.
  *
- * Not an api limit on this path. `MAX_DESCRIBED_IMAGE_ATTACHMENTS` is read in
- * one api runtime site, `resolve_email_image_attachments_suffix`, which is the
- * email channel; the bot path posts one `downloadable` per image and describes
- * each through `resolve_uploaded_file_message_body`, which caps nothing. api
- * also never reads `attachment_group_id` outside analytics, so it cannot batch
- * a group into one describe budget. A fourth image would be hosted, rendered
- * *and* described — in its own reasoner turn.
- *
- * So the cap is a product decision about that cost, not a ceiling api imposes:
- * each extra image buys another bot turn and another describe call. Match it to
- * `MAX_DESCRIBED_IMAGE_ATTACHMENTS` by coincidence of value only.
+ * api answers one send in one reasoner turn and describes at most
+ * `MAX_DESCRIBED_IMAGE_ATTACHMENTS` of its images there. It holds at most
+ * `MAX_HELD_ROWS` rows besides the final row, so a fourth image would start
+ * a turn of its own. Keep this value equal to `MAX_DESCRIBED_IMAGE_ATTACHMENTS`
+ * (3) and to `MAX_HELD_ROWS` plus the final row (2 + 1).
  */
 export declare const IMAGE_ATTACHMENT_MAX_COUNT = 3;
 /** The image types api's attachments route accepts; HEIC/HEIF are transcoded to JPEG there. */

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@ada-cx/messaging-bridge",
-	"version": "1.12.0",
+	"version": "1.12.1",
 	"description": "Types, test mocks, and a thin CDN loader for building a custom app UI on Ada Messaging's bridge contract. The bridge runtime always loads from Ada's CDN.",
 	"type": "module",
 	"license": "ISC",