@leaflow/sdk 0.172.0 → 0.174.0

package/dist/account/v1/generated/models.d.ts

@@ -23,22 +23,64 @@
  * Looking up slugs and claiming custom slugs are rate limited per account. A request over the limit fails with 429, and `meta.retry_after_seconds` on the error states how many seconds to wait before retrying.
  * OpenAPI spec version: 1.0.0
  */
+export interface FieldViolation {
+    /** The path to the rejected field in the request body, such as `items[2].price_id`. */
+    field: string;
+    /** Why the field was rejected, such as `REQUIRED` or `OUT_OF_RANGE`. */
+    reason?: string;
+}
 /**
- * What a given `code` carries alongside the message. The keys depend on the code,
- * and a client that does not recognise one ignores it.
+ * Values that belong to `reason`, one set per reason. Clients use them to fill in
+ * localized text and never parse `message` to obtain them. Keys are documented per
+ * reason; a key that has appeared once keeps appearing.
  */
-export type ErrorMeta = {
-    [key: string]: unknown;
+export type ErrorStatusMetadata = {
+    [key: string]: string;
 };
-export interface Error {
-    code?: string;
+export interface ErrorStatus {
+    /** The HTTP status code of the response. */
+    code: number;
+    /** The canonical name of the status, such as `INVALID_ARGUMENT` or `UNAVAILABLE`. */
+    status: string;
+    /**
+     * A description of the failure for developers. It is always English and is not meant
+     * to be shown to end users as is.
+     */
     message: string;
     /**
-     * What a given `code` carries alongside the message. The keys depend on the code,
-     * and a client that does not recognise one ignores it.
+     * A stable machine-readable code identifying the failure. Clients branch on this value
+     * and render their own text; it does not change once published.
+     */
+    reason?: string;
+    /**
+     * Values that belong to `reason`, one set per reason. Clients use them to fill in
+     * localized text and never parse `message` to obtain them. Keys are documented per
+     * reason; a key that has appeared once keeps appearing.
+     */
+    metadata?: ErrorStatusMetadata;
+    /**
+     * Request fields rejected by the request's constraints. Present on validation
+     * failures; one request may violate several fields.
      */
-    meta?: ErrorMeta;
-    status: number;
+    field_violations?: FieldViolation[];
+    /**
+     * How long the client should wait before retrying, as a duration string such as
+     * `30s`. Present only when waiting can succeed.
+     */
+    retry_delay?: string;
+    /**
+     * The identifier of the request in the service's logs. Quote it when reporting a
+     * failure.
+     */
+    request_id?: string;
+}
+/**
+ * A failed request. The envelope follows the Google REST error format: `code` is the HTTP
+ * status, `status` is its canonical name, and `reason` is the stable machine-readable code
+ * that identifies the failure.
+ */
+export interface Error {
+    error: ErrorStatus;
 }
 /**
  * VERIFIED_ONLY requires identity verification to have completed; a submission under review does not qualify

package/dist/account/v1/generated/validators/error.zod.d.ts

@@ -25,10 +25,19 @@
  */
 import * as zod from "zod";
 export declare const Error: zod.ZodObject<{
-    code: zod.ZodOptional<zod.ZodString>;
-    message: zod.ZodString;
-    meta: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodUnknown>>;
-    status: zod.ZodInt;
+    error: zod.ZodObject<{
+        code: zod.ZodInt;
+        status: zod.ZodString;
+        message: zod.ZodString;
+        reason: zod.ZodOptional<zod.ZodString>;
+        metadata: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodString>>;
+        field_violations: zod.ZodOptional<zod.ZodArray<zod.ZodObject<{
+            field: zod.ZodString;
+            reason: zod.ZodOptional<zod.ZodString>;
+        }, zod.z.core.$strict>>>;
+        retry_delay: zod.ZodOptional<zod.ZodString>;
+        request_id: zod.ZodOptional<zod.ZodString>;
+    }, zod.z.core.$strict>;
 }, zod.z.core.$strict>;
 export type Error = zod.input<typeof Error>;
 export type ErrorOutput = zod.output<typeof Error>;

package/dist/account/v1/generated/validators/error.zod.js

@@ -24,12 +24,9 @@
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";
-export const Error = zod.strictObject({
-    code: zod.string().optional(),
-    message: zod.string(),
-    meta: zod
-        .record(zod.string(), zod.unknown())
-        .optional()
-        .describe("What a given `code` carries alongside the message. The keys depend on the code,\nand a client that does not recognise one ignores it."),
-    status: zod.int(),
-});
+import { ErrorStatus } from "./errorStatus.zod.js";
+export const Error = zod
+    .strictObject({
+    error: ErrorStatus,
+})
+    .describe("A failed request. The envelope follows the Google REST error format: `code` is the HTTP\nstatus, `status` is its canonical name, and `reason` is the stable machine-readable code\nthat identifies the failure.");

package/dist/account/v1/generated/validators/errorStatus.zod.d.ts

@@ -0,0 +1,41 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Account API
+ * Everything that comes before a project is chosen: registration, the account itself, the projects the caller belongs to, and entry into one of them.
+ *
+ * ## Authentication
+ *
+ * Every request carries `Authorization: Bearer <access token>`, obtained by signing in at auth.leaflow.net. The endpoints that need no token say so.
+ *
+ * ## Entering a project
+ *
+ * 1. `QUERY /account/v1/projects` searches the projects the caller belongs to. The first call registers the account, taking the name and email address from the sign-in claims.
+ * 2. `POST /account/v1/projects/{projectId}/scoped-tokens` returns a scoped token for the project chosen.
+ * 3. Every other service is called with that scoped token.
+ *
+ * A scoped token cannot be renewed. Repeat step 2 for a new one, and sign in again at auth.leaflow.net once the access token itself has expired.
+ *
+ * ## Project slugs
+ *
+ * Every project carries a `slug`, the label naming it in its address. Until a custom slug is chosen the slug is the project's `id`, and the address under the `id` keeps working after a custom slug is chosen. `GET /account/v1/projects/by-slug/{slug}` finds the project named by either label.
+ *
+ * Looking up slugs and claiming custom slugs are rate limited per account. A request over the limit fails with 429, and `meta.retry_after_seconds` on the error states how many seconds to wait before retrying.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const ErrorStatus: zod.ZodObject<{
+    code: zod.ZodInt;
+    status: zod.ZodString;
+    message: zod.ZodString;
+    reason: zod.ZodOptional<zod.ZodString>;
+    metadata: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodString>>;
+    field_violations: zod.ZodOptional<zod.ZodArray<zod.ZodObject<{
+        field: zod.ZodString;
+        reason: zod.ZodOptional<zod.ZodString>;
+    }, zod.z.core.$strict>>>;
+    retry_delay: zod.ZodOptional<zod.ZodString>;
+    request_id: zod.ZodOptional<zod.ZodString>;
+}, zod.z.core.$strict>;
+export type ErrorStatus = zod.input<typeof ErrorStatus>;
+export type ErrorStatusOutput = zod.output<typeof ErrorStatus>;

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

@@ -0,0 +1,56 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Account API
+ * Everything that comes before a project is chosen: registration, the account itself, the projects the caller belongs to, and entry into one of them.
+ *
+ * ## Authentication
+ *
+ * Every request carries `Authorization: Bearer <access token>`, obtained by signing in at auth.leaflow.net. The endpoints that need no token say so.
+ *
+ * ## Entering a project
+ *
+ * 1. `QUERY /account/v1/projects` searches the projects the caller belongs to. The first call registers the account, taking the name and email address from the sign-in claims.
+ * 2. `POST /account/v1/projects/{projectId}/scoped-tokens` returns a scoped token for the project chosen.
+ * 3. Every other service is called with that scoped token.
+ *
+ * A scoped token cannot be renewed. Repeat step 2 for a new one, and sign in again at auth.leaflow.net once the access token itself has expired.
+ *
+ * ## Project slugs
+ *
+ * Every project carries a `slug`, the label naming it in its address. Until a custom slug is chosen the slug is the project's `id`, and the address under the `id` keeps working after a custom slug is chosen. `GET /account/v1/projects/by-slug/{slug}` finds the project named by either label.
+ *
+ * Looking up slugs and claiming custom slugs are rate limited per account. A request over the limit fails with 429, and `meta.retry_after_seconds` on the error states how many seconds to wait before retrying.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+import { FieldViolation } from "./fieldViolation.zod.js";
+export const ErrorStatus = zod.strictObject({
+    code: zod.int().describe("The HTTP status code of the response."),
+    status: zod
+        .string()
+        .describe("The canonical name of the status, such as `INVALID_ARGUMENT` or `UNAVAILABLE`."),
+    message: zod
+        .string()
+        .describe("A description of the failure for developers. It is always English and is not meant\nto be shown to end users as is."),
+    reason: zod
+        .string()
+        .optional()
+        .describe("A stable machine-readable code identifying the failure. Clients branch on this value\nand render their own text; it does not change once published."),
+    metadata: zod
+        .record(zod.string(), zod.string())
+        .optional()
+        .describe("Values that belong to `reason`, one set per reason. Clients use them to fill in\nlocalized text and never parse `message` to obtain them. Keys are documented per\nreason; a key that has appeared once keeps appearing."),
+    field_violations: zod
+        .array(FieldViolation)
+        .optional()
+        .describe("Request fields rejected by the request's constraints. Present on validation\nfailures; one request may violate several fields."),
+    retry_delay: zod
+        .string()
+        .optional()
+        .describe("How long the client should wait before retrying, as a duration string such as\n`30s`. Present only when waiting can succeed."),
+    request_id: zod
+        .string()
+        .optional()
+        .describe("The identifier of the request in the service's logs. Quote it when reporting a\nfailure."),
+});

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

@@ -0,0 +1,32 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Account API
+ * Everything that comes before a project is chosen: registration, the account itself, the projects the caller belongs to, and entry into one of them.
+ *
+ * ## Authentication
+ *
+ * Every request carries `Authorization: Bearer <access token>`, obtained by signing in at auth.leaflow.net. The endpoints that need no token say so.
+ *
+ * ## Entering a project
+ *
+ * 1. `QUERY /account/v1/projects` searches the projects the caller belongs to. The first call registers the account, taking the name and email address from the sign-in claims.
+ * 2. `POST /account/v1/projects/{projectId}/scoped-tokens` returns a scoped token for the project chosen.
+ * 3. Every other service is called with that scoped token.
+ *
+ * A scoped token cannot be renewed. Repeat step 2 for a new one, and sign in again at auth.leaflow.net once the access token itself has expired.
+ *
+ * ## Project slugs
+ *
+ * Every project carries a `slug`, the label naming it in its address. Until a custom slug is chosen the slug is the project's `id`, and the address under the `id` keeps working after a custom slug is chosen. `GET /account/v1/projects/by-slug/{slug}` finds the project named by either label.
+ *
+ * Looking up slugs and claiming custom slugs are rate limited per account. A request over the limit fails with 429, and `meta.retry_after_seconds` on the error states how many seconds to wait before retrying.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const FieldViolation: zod.ZodObject<{
+    field: zod.ZodString;
+    reason: zod.ZodOptional<zod.ZodString>;
+}, zod.z.core.$strict>;
+export type FieldViolation = zod.input<typeof FieldViolation>;
+export type FieldViolationOutput = zod.output<typeof FieldViolation>;

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

@@ -0,0 +1,35 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Account API
+ * Everything that comes before a project is chosen: registration, the account itself, the projects the caller belongs to, and entry into one of them.
+ *
+ * ## Authentication
+ *
+ * Every request carries `Authorization: Bearer <access token>`, obtained by signing in at auth.leaflow.net. The endpoints that need no token say so.
+ *
+ * ## Entering a project
+ *
+ * 1. `QUERY /account/v1/projects` searches the projects the caller belongs to. The first call registers the account, taking the name and email address from the sign-in claims.
+ * 2. `POST /account/v1/projects/{projectId}/scoped-tokens` returns a scoped token for the project chosen.
+ * 3. Every other service is called with that scoped token.
+ *
+ * A scoped token cannot be renewed. Repeat step 2 for a new one, and sign in again at auth.leaflow.net once the access token itself has expired.
+ *
+ * ## Project slugs
+ *
+ * Every project carries a `slug`, the label naming it in its address. Until a custom slug is chosen the slug is the project's `id`, and the address under the `id` keeps working after a custom slug is chosen. `GET /account/v1/projects/by-slug/{slug}` finds the project named by either label.
+ *
+ * Looking up slugs and claiming custom slugs are rate limited per account. A request over the limit fails with 429, and `meta.retry_after_seconds` on the error states how many seconds to wait before retrying.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const FieldViolation = zod.strictObject({
+    field: zod
+        .string()
+        .describe("The path to the rejected field in the request body, such as `items[2].price_id`."),
+    reason: zod
+        .string()
+        .optional()
+        .describe("Why the field was rejected, such as `REQUIRED` or `OUT_OF_RANGE`."),
+});

package/dist/assistant/v1/generated/models.d.ts

@@ -22,22 +22,64 @@
  * parts, then complete the upload and send its attachment id in a message.
  * OpenAPI spec version: 2.0.0
  */
+export interface FieldViolation {
+    /** The path to the rejected field in the request body, such as `items[2].price_id`. */
+    field: string;
+    /** Why the field was rejected, such as `REQUIRED` or `OUT_OF_RANGE`. */
+    reason?: string;
+}
 /**
- * What a given `code` carries alongside the message. The keys depend on the code,
- * and a client that does not recognise one ignores it.
+ * Values that belong to `reason`, one set per reason. Clients use them to fill in
+ * localized text and never parse `message` to obtain them. Keys are documented per
+ * reason; a key that has appeared once keeps appearing.
  */
-export type ErrorMeta = {
-    [key: string]: unknown;
+export type ErrorStatusMetadata = {
+    [key: string]: string;
 };
-export interface Error {
-    code?: string;
+export interface ErrorStatus {
+    /** The HTTP status code of the response. */
+    code: number;
+    /** The canonical name of the status, such as `INVALID_ARGUMENT` or `UNAVAILABLE`. */
+    status: string;
+    /**
+     * A description of the failure for developers. It is always English and is not meant
+     * to be shown to end users as is.
+     */
     message: string;
     /**
-     * What a given `code` carries alongside the message. The keys depend on the code,
-     * and a client that does not recognise one ignores it.
+     * A stable machine-readable code identifying the failure. Clients branch on this value
+     * and render their own text; it does not change once published.
+     */
+    reason?: string;
+    /**
+     * Values that belong to `reason`, one set per reason. Clients use them to fill in
+     * localized text and never parse `message` to obtain them. Keys are documented per
+     * reason; a key that has appeared once keeps appearing.
+     */
+    metadata?: ErrorStatusMetadata;
+    /**
+     * Request fields rejected by the request's constraints. Present on validation
+     * failures; one request may violate several fields.
      */
-    meta?: ErrorMeta;
-    status: number;
+    field_violations?: FieldViolation[];
+    /**
+     * How long the client should wait before retrying, as a duration string such as
+     * `30s`. Present only when waiting can succeed.
+     */
+    retry_delay?: string;
+    /**
+     * The identifier of the request in the service's logs. Quote it when reporting a
+     * failure.
+     */
+    request_id?: string;
+}
+/**
+ * A failed request. The envelope follows the Google REST error format: `code` is the HTTP
+ * status, `status` is its canonical name, and `reason` is the stable machine-readable code
+ * that identifies the failure.
+ */
+export interface Error {
+    error: ErrorStatus;
 }
 /**
  * Tokens reported by Canopy. Cache hit rate is cachedInputTokens / inputTokens.

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

@@ -24,10 +24,19 @@
  */
 import * as zod from "zod";
 export declare const Error: zod.ZodObject<{
-    code: zod.ZodOptional<zod.ZodString>;
-    message: zod.ZodString;
-    meta: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodUnknown>>;
-    status: zod.ZodInt;
+    error: zod.ZodObject<{
+        code: zod.ZodInt;
+        status: zod.ZodString;
+        message: zod.ZodString;
+        reason: zod.ZodOptional<zod.ZodString>;
+        metadata: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodString>>;
+        field_violations: zod.ZodOptional<zod.ZodArray<zod.ZodObject<{
+            field: zod.ZodString;
+            reason: zod.ZodOptional<zod.ZodString>;
+        }, zod.z.core.$strict>>>;
+        retry_delay: zod.ZodOptional<zod.ZodString>;
+        request_id: zod.ZodOptional<zod.ZodString>;
+    }, zod.z.core.$strict>;
 }, zod.z.core.$strict>;
 export type Error = zod.input<typeof Error>;
 export type ErrorOutput = zod.output<typeof Error>;

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

@@ -23,12 +23,9 @@
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";
-export const Error = zod.strictObject({
-    code: zod.string().optional(),
-    message: zod.string(),
-    meta: zod
-        .record(zod.string(), zod.unknown())
-        .optional()
-        .describe("What a given `code` carries alongside the message. The keys depend on the code,\nand a client that does not recognise one ignores it."),
-    status: zod.int(),
-});
+import { ErrorStatus } from "./errorStatus.zod.js";
+export const Error = zod
+    .strictObject({
+    error: ErrorStatus,
+})
+    .describe("A failed request. The envelope follows the Google REST error format: `code` is the HTTP\nstatus, `status` is its canonical name, and `reason` is the stable machine-readable code\nthat identifies the failure.");

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

@@ -0,0 +1,40 @@
+/**
+ * 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
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.
+ * OpenAPI spec version: 2.0.0
+ */
+import * as zod from "zod";
+export declare const ErrorStatus: zod.ZodObject<{
+    code: zod.ZodInt;
+    status: zod.ZodString;
+    message: zod.ZodString;
+    reason: zod.ZodOptional<zod.ZodString>;
+    metadata: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodString>>;
+    field_violations: zod.ZodOptional<zod.ZodArray<zod.ZodObject<{
+        field: zod.ZodString;
+        reason: zod.ZodOptional<zod.ZodString>;
+    }, zod.z.core.$strict>>>;
+    retry_delay: zod.ZodOptional<zod.ZodString>;
+    request_id: zod.ZodOptional<zod.ZodString>;
+}, zod.z.core.$strict>;
+export type ErrorStatus = zod.input<typeof ErrorStatus>;
+export type ErrorStatusOutput = zod.output<typeof ErrorStatus>;

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

@@ -0,0 +1,55 @@
+/**
+ * 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
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.
+ * OpenAPI spec version: 2.0.0
+ */
+import * as zod from "zod";
+import { FieldViolation } from "./fieldViolation.zod.js";
+export const ErrorStatus = zod.strictObject({
+    code: zod.int().describe("The HTTP status code of the response."),
+    status: zod
+        .string()
+        .describe("The canonical name of the status, such as `INVALID_ARGUMENT` or `UNAVAILABLE`."),
+    message: zod
+        .string()
+        .describe("A description of the failure for developers. It is always English and is not meant\nto be shown to end users as is."),
+    reason: zod
+        .string()
+        .optional()
+        .describe("A stable machine-readable code identifying the failure. Clients branch on this value\nand render their own text; it does not change once published."),
+    metadata: zod
+        .record(zod.string(), zod.string())
+        .optional()
+        .describe("Values that belong to `reason`, one set per reason. Clients use them to fill in\nlocalized text and never parse `message` to obtain them. Keys are documented per\nreason; a key that has appeared once keeps appearing."),
+    field_violations: zod
+        .array(FieldViolation)
+        .optional()
+        .describe("Request fields rejected by the request's constraints. Present on validation\nfailures; one request may violate several fields."),
+    retry_delay: zod
+        .string()
+        .optional()
+        .describe("How long the client should wait before retrying, as a duration string such as\n`30s`. Present only when waiting can succeed."),
+    request_id: zod
+        .string()
+        .optional()
+        .describe("The identifier of the request in the service's logs. Quote it when reporting a\nfailure."),
+});

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

@@ -0,0 +1,31 @@
+/**
+ * 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
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.
+ * OpenAPI spec version: 2.0.0
+ */
+import * as zod from "zod";
+export declare const FieldViolation: zod.ZodObject<{
+    field: zod.ZodString;
+    reason: zod.ZodOptional<zod.ZodString>;
+}, zod.z.core.$strict>;
+export type FieldViolation = zod.input<typeof FieldViolation>;
+export type FieldViolationOutput = zod.output<typeof FieldViolation>;

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

@@ -0,0 +1,34 @@
+/**
+ * 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
+ * over the WebSocket described under /api/v1/realtime/tickets. 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 attachment id in a message.
+ * OpenAPI spec version: 2.0.0
+ */
+import * as zod from "zod";
+export const FieldViolation = zod.strictObject({
+    field: zod
+        .string()
+        .describe("The path to the rejected field in the request body, such as `items[2].price_id`."),
+    reason: zod
+        .string()
+        .optional()
+        .describe("Why the field was rejected, such as `REQUIRED` or `OUT_OF_RANGE`."),
+});

package/dist/billing/v1/generated/models.d.ts

@@ -560,22 +560,64 @@ export interface SubscriptionCancellation {
     failure_code?: string;
     failure_reason?: string;
 }
+export interface FieldViolation {
+    /** The path to the rejected field in the request body, such as `items[2].price_id`. */
+    field: string;
+    /** Why the field was rejected, such as `REQUIRED` or `OUT_OF_RANGE`. */
+    reason?: string;
+}
 /**
- * What a given `code` carries alongside the message. The keys depend on the code,
- * and a client that does not recognise one ignores it.
+ * Values that belong to `reason`, one set per reason. Clients use them to fill in
+ * localized text and never parse `message` to obtain them. Keys are documented per
+ * reason; a key that has appeared once keeps appearing.
  */
-export type ErrorMeta = {
-    [key: string]: unknown;
+export type ErrorStatusMetadata = {
+    [key: string]: string;
 };
-export interface Error {
-    code?: string;
+export interface ErrorStatus {
+    /** The HTTP status code of the response. */
+    code: number;
+    /** The canonical name of the status, such as `INVALID_ARGUMENT` or `UNAVAILABLE`. */
+    status: string;
+    /**
+     * A description of the failure for developers. It is always English and is not meant
+     * to be shown to end users as is.
+     */
     message: string;
     /**
-     * What a given `code` carries alongside the message. The keys depend on the code,
-     * and a client that does not recognise one ignores it.
+     * A stable machine-readable code identifying the failure. Clients branch on this value
+     * and render their own text; it does not change once published.
+     */
+    reason?: string;
+    /**
+     * Values that belong to `reason`, one set per reason. Clients use them to fill in
+     * localized text and never parse `message` to obtain them. Keys are documented per
+     * reason; a key that has appeared once keeps appearing.
      */
-    meta?: ErrorMeta;
-    status: number;
+    metadata?: ErrorStatusMetadata;
+    /**
+     * Request fields rejected by the request's constraints. Present on validation
+     * failures; one request may violate several fields.
+     */
+    field_violations?: FieldViolation[];
+    /**
+     * How long the client should wait before retrying, as a duration string such as
+     * `30s`. Present only when waiting can succeed.
+     */
+    retry_delay?: string;
+    /**
+     * The identifier of the request in the service's logs. Quote it when reporting a
+     * failure.
+     */
+    request_id?: string;
+}
+/**
+ * A failed request. The envelope follows the Google REST error format: `code` is the HTTP
+ * status, `status` is its canonical name, and `reason` is the stable machine-readable code
+ * that identifies the failure.
+ */
+export interface Error {
+    error: ErrorStatus;
 }
 export interface Product {
     id: ProductID;