@leaflow/sdk 0.0.0-dev.519.g9e3ae08 → 0.0.0-dev.526.g367525a

package/dist/assistant/v1/generated/validators/errorStatus.zod.js

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/fieldViolation.zod.d.ts

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/fieldViolation.zod.js

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/{attachmentCountsResource.zod.d.ts → fileCountsResource.zod.d.ts}

@@ -20,16 +20,17 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";
-export declare const AttachmentCountsResource: zod.ZodObject<{
+export declare const FileCountsResource: zod.ZodObject<{
     total: zod.ZodInt;
     totalBytes: zod.ZodInt;
 }, zod.z.core.$strict>;
-export type AttachmentCountsResource = zod.input<typeof AttachmentCountsResource>;
-export type AttachmentCountsResourceOutput = zod.output<typeof AttachmentCountsResource>;
+export type FileCountsResource = zod.input<typeof FileCountsResource>;
+export type FileCountsResourceOutput = zod.output<typeof FileCountsResource>;

package/dist/assistant/v1/generated/validators/{attachmentCountsResource.zod.js → fileCountsResource.zod.js}

@@ -20,14 +20,15 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";
-export const AttachmentCountsResource = zod
+export const FileCountsResource = zod
     .strictObject({
     total: zod.int(),
     totalBytes: zod.int(),

package/dist/assistant/v1/generated/validators/fileDiffResource.zod.d.ts

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/fileDiffResource.zod.js

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/{attachmentListResponseBody.zod.d.ts → fileListResponseBody.zod.d.ts}

@@ -20,29 +20,30 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";
-export declare const AttachmentListResponseBody: zod.ZodObject<{
-    attachments: zod.ZodArray<zod.ZodObject<{
-        byteSize: zod.ZodInt;
-        createdAt: zod.z.ZodISODateTime;
-        draftExpiresAt: zod.ZodNullable<zod.z.ZodISODateTime>;
-        filename: zod.ZodString;
-        height: zod.ZodNullable<zod.ZodInt>;
+export declare const FileListResponseBody: zod.ZodObject<{
+    files: zod.ZodArray<zod.ZodObject<{
         id: zod.ZodString;
-        mime: zod.ZodString;
+        filename: zod.ZodString;
+        mediaType: zod.ZodString;
         type: zod.ZodEnum<{
             text: "text";
             image: "image";
             binary: "binary";
         }>;
-        updatedAt: zod.z.ZodISODateTime;
+        byteSize: zod.ZodInt;
         width: zod.ZodNullable<zod.ZodInt>;
+        height: zod.ZodNullable<zod.ZodInt>;
+        draftExpiresAt: zod.ZodNullable<zod.z.ZodISODateTime>;
+        createdAt: zod.z.ZodISODateTime;
+        updatedAt: zod.z.ZodISODateTime;
     }, zod.z.core.$strict>>;
     nextCursor: zod.ZodNullable<zod.ZodString>;
     counts: zod.ZodUnion<readonly [zod.ZodObject<{
@@ -50,5 +51,5 @@ export declare const AttachmentListResponseBody: zod.ZodObject<{
         totalBytes: zod.ZodInt;
     }, zod.z.core.$strict>, zod.ZodNull]>;
 }, zod.z.core.$strict>;
-export type AttachmentListResponseBody = zod.input<typeof AttachmentListResponseBody>;
-export type AttachmentListResponseBodyOutput = zod.output<typeof AttachmentListResponseBody>;
+export type FileListResponseBody = zod.input<typeof FileListResponseBody>;
+export type FileListResponseBodyOutput = zod.output<typeof FileListResponseBody>;

package/dist/assistant/v1/generated/validators/{attachmentListResponseBody.zod.js → fileListResponseBody.zod.js}

@@ -20,19 +20,20 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";
-import { AttachmentCountsResource } from "./attachmentCountsResource.zod.js";
-import { AttachmentFileResource } from "./attachmentFileResource.zod.js";
-export const AttachmentListResponseBody = zod.strictObject({
-    attachments: zod.array(AttachmentFileResource),
+import { FileCountsResource } from "./fileCountsResource.zod.js";
+import { FileResource } from "./fileResource.zod.js";
+export const FileListResponseBody = zod.strictObject({
+    files: zod.array(FileResource),
     nextCursor: zod.string().nullable().describe("Null on the last page."),
     counts: zod
-        .union([AttachmentCountsResource, zod.null()])
+        .union([FileCountsResource, zod.null()])
         .describe("Null unless `include` asked for it."),
 });

package/dist/assistant/v1/generated/validators/{attachmentFileResource.zod.d.ts → fileResource.zod.d.ts}

@@ -20,28 +20,29 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";
-export declare const AttachmentFileResource: zod.ZodObject<{
-    byteSize: zod.ZodInt;
-    createdAt: zod.z.ZodISODateTime;
-    draftExpiresAt: zod.ZodNullable<zod.z.ZodISODateTime>;
-    filename: zod.ZodString;
-    height: zod.ZodNullable<zod.ZodInt>;
+export declare const FileResource: zod.ZodObject<{
     id: zod.ZodString;
-    mime: zod.ZodString;
+    filename: zod.ZodString;
+    mediaType: zod.ZodString;
     type: zod.ZodEnum<{
         text: "text";
         image: "image";
         binary: "binary";
     }>;
-    updatedAt: zod.z.ZodISODateTime;
+    byteSize: zod.ZodInt;
     width: zod.ZodNullable<zod.ZodInt>;
+    height: zod.ZodNullable<zod.ZodInt>;
+    draftExpiresAt: zod.ZodNullable<zod.z.ZodISODateTime>;
+    createdAt: zod.z.ZodISODateTime;
+    updatedAt: zod.z.ZodISODateTime;
 }, zod.z.core.$strict>;
-export type AttachmentFileResource = zod.input<typeof AttachmentFileResource>;
-export type AttachmentFileResourceOutput = zod.output<typeof AttachmentFileResource>;
+export type FileResource = zod.input<typeof FileResource>;
+export type FileResourceOutput = zod.output<typeof FileResource>;

package/dist/assistant/v1/generated/validators/{uploadedResource.zod.js → fileResource.zod.js}

@@ -20,25 +20,35 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";
-export const UploadedResource = zod.strictObject({
-    byteSize: zod
-        .int()
-        .describe("Size of what was stored. For an image that has been resized, this is the resized size, not what was uploaded."),
-    draftExpiresAt: zod.iso
-        .datetime({ offset: true })
-        .describe("When this upload gets cleared if no message ever references it. Sending a message with this id makes it permanent and this stops applying — a file that belongs to a conversation is kept as long as the conversation is.\n\nIt is here so the editor can say so before it happens. An attachment chip that quietly stops working a week later reads as a bug, and the person who hits it has no way to tell that what they are seeing is a draft being collected."),
-    filename: zod.string(),
-    height: zod.int().nullable().describe("Null unless type is image."),
+export const FileResource = zod
+    .strictObject({
     id: zod.string(),
+    filename: zod.string(),
+    mediaType: zod
+        .string()
+        .describe("The IANA media type detected at intake, not the Content-Type the client sent."),
     type: zod
         .enum(["image", "text", "binary"])
-        .describe("How the assistant will see this file.\n\n- `image` — read directly, and only by models that accept image input\n- `text` — placed inline in the message when small enough, otherwise read on demand\n- `binary` — never read directly; the assistant downloads it onto a cloud instance to work with it"),
-    width: zod.int().nullable().describe("Null unless type is image."),
-});
+        .describe("How the assistant reads the file.\n\n- `image` — read directly, and only by models that accept image input\n- `text` — placed inline in the message when small enough, otherwise read on demand\n- `binary` — never read directly; the assistant downloads it onto a host to work with it\n\nOnly an `image` can be shown in place; everything else is offered for download."),
+    byteSize: zod.int(),
+    width: zod
+        .int()
+        .nullable()
+        .describe("Null unless type is image. Lets a client hold the space before the image loads."),
+    height: zod.int().nullable().describe("Null unless type is image."),
+    draftExpiresAt: zod.iso
+        .datetime({ offset: true })
+        .nullable()
+        .describe("When this upload is cleared if no message ever references it. Null once a message, a tool\ncall or an artifact uses it; such a file is kept as long as what uses it is."),
+    createdAt: zod.iso.datetime({ offset: true }),
+    updatedAt: zod.iso.datetime({ offset: true }),
+})
+    .describe("A stored file, wherever it appears.");

package/dist/assistant/v1/generated/validators/folderCountsResource.zod.d.ts

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/folderCountsResource.zod.js

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/folderListResponseBody.zod.d.ts

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/folderListResponseBody.zod.js

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/folderResource.zod.d.ts

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/folderResource.zod.js

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/itemSourceResource.zod.d.ts

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/itemSourceResource.zod.js

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/lastTurnResource.zod.d.ts

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/lastTurnResource.zod.js

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/lengthAwarePageBindingResource.zod.d.ts

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/lengthAwarePageBindingResource.zod.js

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/lengthAwarePageChannelResource.zod.d.ts

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/lengthAwarePageChannelResource.zod.js

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/listArtifactVersionsParams.zod.d.ts

@@ -0,0 +1,39 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Assistant API
+ * Conversations with agents that operate the Leaflow platform, plus their folders, tasks, files and
+ * chat-app channels.
+ *
+ * A conversation is a thread. A person talks to the main thread; the agent in it can start subagents,
+ * which are threads too and run on their own: stopping the main thread does not stop them, and each
+ * subagent tells its parent when it ends. A thread runs in turns; each turn records the model and
+ * reasoning effort it used and its token usage.
+ *
+ * Models come from the Canopy catalogue. A new thread uses the model it names, the caller's default
+ * from /api/v1/settings, or the first catalogue model that can run an agent. Reasoning models take one
+ * of three efforts — low, medium or high — which are sent to the model unchanged.
+ *
+ * Read a thread's state with get-thread and its transcript with list-thread-items. Follow both live
+ * through EventBus by subscribing to assistant.thread.frame and assistant.resource.updated; after a
+ * reconnection or an assistant.workspace.invalidated message, read them again. list-thread-messages
+ * outlines the person's messages for navigating a long conversation.
+ *
+ * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
+ * parts, then complete the upload and send its file id in a message.
+ *
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
+ * OpenAPI spec version: 2.0.0
+ */
+import * as zod from "zod";
+export declare const listArtifactVersionsParamsCursorMax = 1024;
+export declare const listArtifactVersionsParamsLimitDefault = 50;
+export declare const listArtifactVersionsParamsLimitMax = 200;
+export declare const ListArtifactVersionsParams: zod.ZodObject<{
+    cursor: zod.ZodOptional<zod.ZodString>;
+    limit: zod.ZodDefault<zod.ZodInt>;
+}, zod.z.core.$strict>;
+export type ListArtifactVersionsParams = zod.input<typeof ListArtifactVersionsParams>;
+export type ListArtifactVersionsParamsOutput = zod.output<typeof ListArtifactVersionsParams>;

package/dist/assistant/v1/generated/validators/listArtifactVersionsParams.zod.js

@@ -0,0 +1,41 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Assistant API
+ * Conversations with agents that operate the Leaflow platform, plus their folders, tasks, files and
+ * chat-app channels.
+ *
+ * A conversation is a thread. A person talks to the main thread; the agent in it can start subagents,
+ * which are threads too and run on their own: stopping the main thread does not stop them, and each
+ * subagent tells its parent when it ends. A thread runs in turns; each turn records the model and
+ * reasoning effort it used and its token usage.
+ *
+ * Models come from the Canopy catalogue. A new thread uses the model it names, the caller's default
+ * from /api/v1/settings, or the first catalogue model that can run an agent. Reasoning models take one
+ * of three efforts — low, medium or high — which are sent to the model unchanged.
+ *
+ * Read a thread's state with get-thread and its transcript with list-thread-items. Follow both live
+ * through EventBus by subscribing to assistant.thread.frame and assistant.resource.updated; after a
+ * reconnection or an assistant.workspace.invalidated message, read them again. list-thread-messages
+ * outlines the person's messages for navigating a long conversation.
+ *
+ * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
+ * parts, then complete the upload and send its file id in a message.
+ *
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
+ * OpenAPI spec version: 2.0.0
+ */
+import * as zod from "zod";
+export const listArtifactVersionsParamsCursorMax = 1024;
+export const listArtifactVersionsParamsLimitDefault = 50;
+export const listArtifactVersionsParamsLimitMax = 200;
+export const ListArtifactVersionsParams = zod.strictObject({
+    cursor: zod.string().min(1).max(listArtifactVersionsParamsCursorMax).optional(),
+    limit: zod
+        .int()
+        .min(1)
+        .max(listArtifactVersionsParamsLimitMax)
+        .default(listArtifactVersionsParamsLimitDefault),
+});