@thinkai/tai-api-contract 2.181.0 → 2.182.0

package/dist/generated/openapi.d.ts

@@ -3342,7 +3342,7 @@ export interface paths {
         put?: never;
         /**
          * Upload a Conversations attachment
-         * @description Any workspace member when chat is ready. Validates size/type against the active provider profile (`attachmentLimits` from readiness). Returns metadata; pass `id` as `attachmentIds` on the next POST message. Max 5 MB per file.
+         * @description Any workspace member when chat is ready. Validates size/type against the active provider profile (`attachmentLimits` from readiness). Returns metadata; pass `id` as `attachmentIds` on the next POST message. Max 5 MB per file (JSON bodyLimit is raised for `contentBase64`). When unbound uploads already sit at the per-message file cap (e.g. after an aborted send), the oldest unbound rows are pruned so a new attach can proceed.
          */
         post: operations["postCodeChatAttachment"];
         delete?: never;
@@ -21579,7 +21579,7 @@ export interface operations {
                     "application/json": components["schemas"]["CodeChatAttachmentMetaDto"];
                 };
             };
-            /** @description Validation failed (size, type, totals) */
+            /** @description Validation failed after decode (size, type, totals). Stable codes include `attachment_too_large`, `attachment_total_too_large`, `attachment_too_many`, `attachment_type_unsupported`, `attachment_pdf_too_long`, `attachment_failed`, `invalid_input`. */
             400: {
                 headers: {
                     [name: string]: unknown;
@@ -21607,6 +21607,21 @@ export interface operations {
                     "application/json": components["schemas"]["ErrorMessageDto"];
                 };
             };
+            /** @description Fastify rejected the JSON body before the handler (`request_body_too_large`). Typical when `contentBase64` exceeds the route bodyLimit (aligned with the 5 MB per-file cap after base64 expansion). Decoded-size overruns still return `400` `attachment_too_large`. */
+            413: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    /**
+                     * @example {
+                     *       "error": "Request body is too large.",
+                     *       "code": "request_body_too_large"
+                     *     }
+                     */
+                    "application/json": components["schemas"]["ErrorMessageDto"];
+                };
+            };
             /** @description Could not process the file */
             422: {
                 headers: {