@thinkai/tai-api-contract 2.181.0 → 2.182.0

package/openapi/openapi.yaml

@@ -1,7 +1,7 @@
 openapi: 3.0.3
 info:
   title: ThinkAI API
-  version: 2.181.0
+  version: 2.182.0
   description: >
     Contract surface for the AI Driven SDLC backend used by ThinkAI.
     Workspace-scoped routes use `/workspaces/{workspaceId}/...`.
@@ -9154,7 +9154,10 @@ paths:
       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.
+        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.
       operationId: postCodeChatAttachment
       x-test-coverage-skip: thin HTTP over validateAttachment + store insert
       parameters:
@@ -9173,7 +9176,11 @@ paths:
               schema:
                 $ref: "#/components/schemas/CodeChatAttachmentMetaDto"
         "400":
-          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`.
           content:
             application/json:
               schema:
@@ -9192,6 +9199,19 @@ paths:
             application/json:
               schema:
                 $ref: "#/components/schemas/ErrorMessageDto"
+        "413":
+          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`.
+          content:
+            application/json:
+              schema:
+                $ref: "#/components/schemas/ErrorMessageDto"
+              example:
+                error: Request body is too large.
+                code: request_body_too_large
         "422":
           description: Could not process the file
           content:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@thinkai/tai-api-contract",
-  "version": "2.181.0",
+  "version": "2.182.0",
   "private": false,
   "type": "module",
   "main": "dist/index.js",
@@ -21,7 +21,7 @@
   "devDependencies": {
     "@stoplight/spectral-cli": "^6.17.0",
     "@types/node": "^26.6.5",
-    "jsonpath-plus": "^11.1.1",
+    "jsonpath-plus": "^11.2.1",
     "openapi-typescript": "^7.13.0",
     "typescript": "~6.0.3"
   },

package/src/generated/openapi.ts

@@ -3343,7 +3343,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;
@@ -21580,7 +21580,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;
@@ -21608,6 +21608,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: {