@leaflow/sdk 0.0.0-dev.437.gc278ab8 → 0.0.0-dev.441.gdbb8c45

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

@@ -1,274 +0,0 @@
-/**
- * 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 RealtimeServerMessage: zod.ZodObject<{
-    type: zod.ZodEnum<{
-        error: "error";
-        subscribed: "subscribed";
-        unsubscribed: "unsubscribed";
-        "thread.updated": "thread.updated";
-        "thread.deleted": "thread.deleted";
-        "turn.updated": "turn.updated";
-        "folder.updated": "folder.updated";
-        "folder.deleted": "folder.deleted";
-        "task.updated": "task.updated";
-        "task.deleted": "task.deleted";
-        "item.frame": "item.frame";
-        resync: "resync";
-        pong: "pong";
-    }>;
-    topic: zod.ZodOptional<zod.ZodString>;
-    thread: zod.ZodOptional<zod.ZodObject<{
-        id: zod.ZodString;
-        role: zod.ZodEnum<{
-            main: "main";
-            subagent: "subagent";
-        }>;
-        parentId: zod.ZodNullable<zod.ZodString>;
-        agentName: zod.ZodNullable<zod.ZodString>;
-        title: zod.ZodNullable<zod.ZodString>;
-        folderId: zod.ZodNullable<zod.ZodString>;
-        orderVersion: zod.ZodInt;
-        modelId: zod.ZodString;
-        reasoningEffort: zod.ZodUnion<readonly [zod.ZodEnum<{
-            high: "high";
-            low: "low";
-            medium: "medium";
-        }>, zod.ZodNull]>;
-        approvalMode: zod.ZodEnum<{
-            manual: "manual";
-            guardian: "guardian";
-            yolo: "yolo";
-        }>;
-        status: zod.ZodEnum<{
-            idle: "idle";
-            starting: "starting";
-            running: "running";
-            waiting: "waiting";
-            awaiting_approval: "awaiting_approval";
-            awaiting_input: "awaiting_input";
-        }>;
-        activity: zod.ZodNullable<zod.ZodString>;
-        recentMessage: zod.ZodNullable<zod.ZodString>;
-        todos: zod.ZodArray<zod.ZodObject<{
-            content: zod.ZodString;
-            activeForm: zod.ZodString;
-            status: zod.ZodEnum<{
-                completed: "completed";
-                pending: "pending";
-                in_progress: "in_progress";
-            }>;
-        }, zod.z.core.$strict>>;
-        pendingAction: zod.ZodUnion<readonly [zod.ZodObject<{
-            threadId: zod.ZodString;
-            itemIds: zod.ZodArray<zod.ZodString>;
-            type: zod.ZodEnum<{
-                approval: "approval";
-                question: "question";
-            }>;
-        }, zod.z.core.$strict>, zod.ZodNull]>;
-        subagents: zod.ZodObject<{
-            total: zod.ZodInt;
-            running: zod.ZodInt;
-        }, zod.z.core.$strict>;
-        lastTurn: zod.ZodUnion<readonly [zod.ZodObject<{
-            id: zod.ZodString;
-            type: zod.ZodEnum<{
-                message: "message";
-                compaction: "compaction";
-            }>;
-            status: zod.ZodEnum<{
-                running: "running";
-                completed: "completed";
-                failed: "failed";
-                declined: "declined";
-                cancelled: "cancelled";
-            }>;
-            failureCode: zod.ZodNullable<zod.ZodString>;
-            completedAt: zod.ZodNullable<zod.z.ZodISODateTime>;
-        }, zod.z.core.$strict>, zod.ZodNull]>;
-        context: zod.ZodObject<{
-            usedTokens: zod.ZodNullable<zod.ZodInt>;
-            windowTokens: zod.ZodNullable<zod.ZodInt>;
-        }, zod.z.core.$strict>;
-        usage: zod.ZodObject<{
-            inputTokens: zod.ZodInt;
-            cachedInputTokens: zod.ZodInt;
-            cacheWriteTokens: zod.ZodInt;
-            outputTokens: zod.ZodInt;
-            reasoningTokens: zod.ZodInt;
-            totalTokens: zod.ZodInt;
-            requests: zod.ZodInt;
-            complete: zod.ZodBoolean;
-        }, zod.z.core.$strict>;
-        unread: zod.ZodBoolean;
-        archived: zod.ZodBoolean;
-        messageCount: zod.ZodInt;
-        createdAt: zod.z.ZodISODateTime;
-        updatedAt: zod.z.ZodISODateTime;
-    }, zod.z.core.$strict>>;
-    threadId: zod.ZodOptional<zod.ZodString>;
-    turn: zod.ZodOptional<zod.ZodObject<{
-        id: zod.ZodString;
-        threadId: zod.ZodString;
-        type: zod.ZodEnum<{
-            message: "message";
-            compaction: "compaction";
-        }>;
-        status: zod.ZodEnum<{
-            running: "running";
-            completed: "completed";
-            failed: "failed";
-            declined: "declined";
-            cancelled: "cancelled";
-        }>;
-        firstOrdinal: zod.ZodNullable<zod.ZodInt>;
-        lastOrdinal: zod.ZodNullable<zod.ZodInt>;
-        preview: zod.ZodNullable<zod.ZodString>;
-        modelId: zod.ZodString;
-        reasoningEffort: zod.ZodUnion<readonly [zod.ZodEnum<{
-            high: "high";
-            low: "low";
-            medium: "medium";
-        }>, zod.ZodNull]>;
-        approvalMode: zod.ZodEnum<{
-            manual: "manual";
-            guardian: "guardian";
-            yolo: "yolo";
-        }>;
-        failureCode: zod.ZodNullable<zod.ZodString>;
-        toolCalls: zod.ZodInt;
-        usage: zod.ZodObject<{
-            inputTokens: zod.ZodInt;
-            cachedInputTokens: zod.ZodInt;
-            cacheWriteTokens: zod.ZodInt;
-            outputTokens: zod.ZodInt;
-            reasoningTokens: zod.ZodInt;
-            totalTokens: zod.ZodInt;
-            requests: zod.ZodInt;
-            complete: zod.ZodBoolean;
-        }, zod.z.core.$strict>;
-        streamingOutputTokens: zod.ZodInt;
-        startedAt: zod.z.ZodISODateTime;
-        firstTokenAt: zod.ZodNullable<zod.z.ZodISODateTime>;
-        completedAt: zod.ZodNullable<zod.z.ZodISODateTime>;
-    }, zod.z.core.$strict>>;
-    folder: zod.ZodOptional<zod.ZodObject<{
-        id: zod.ZodString;
-        type: zod.ZodEnum<{
-            custom: "custom";
-            inbox: "inbox";
-        }>;
-        name: zod.ZodString;
-        counts: zod.ZodObject<{
-            total: zod.ZodInt;
-            needsAction: zod.ZodInt;
-            running: zod.ZodInt;
-        }, zod.z.core.$strict>;
-        orderVersion: zod.ZodInt;
-        createdAt: zod.z.ZodISODateTime;
-        updatedAt: zod.z.ZodISODateTime;
-    }, zod.z.core.$strict>>;
-    folderId: zod.ZodOptional<zod.ZodString>;
-    task: zod.ZodOptional<zod.ZodObject<{
-        id: zod.ZodString;
-        threadId: zod.ZodString;
-        name: zod.ZodString;
-        status: zod.ZodEnum<{
-            active: "active";
-            completed: "completed";
-            cancelled: "cancelled";
-            paused: "paused";
-        }>;
-        trigger: zod.ZodObject<{
-            type: zod.ZodEnum<{
-                at: "at";
-                now: "now";
-                interval: "interval";
-                cron: "cron";
-            }>;
-            runAt: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
-            intervalSeconds: zod.ZodOptional<zod.ZodNullable<zod.ZodInt>>;
-            anchorAt: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
-            cron: zod.ZodOptional<zod.ZodNullable<zod.ZodString>>;
-            timezone: zod.ZodDefault<zod.ZodString>;
-            overlapPolicy: zod.ZodDefault<zod.ZodEnum<{
-                skip: "skip";
-                buffer_one: "buffer_one";
-            }>>;
-            catchupSeconds: zod.ZodDefault<zod.ZodInt>;
-        }, zod.z.core.$strict>;
-        action: zod.ZodObject<{
-            type: zod.ZodEnum<{
-                prompt: "prompt";
-                command: "command";
-            }>;
-            prompt: zod.ZodOptional<zod.ZodNullable<zod.ZodString>>;
-            instanceId: zod.ZodOptional<zod.ZodNullable<zod.ZodString>>;
-            command: zod.ZodOptional<zod.ZodNullable<zod.ZodString>>;
-            timeoutSeconds: zod.ZodDefault<zod.ZodInt>;
-        }, zod.z.core.$strict>;
-        nextRunAt: zod.ZodNullable<zod.z.ZodISODateTime>;
-        lastRun: zod.ZodUnion<readonly [zod.ZodObject<{
-            id: zod.ZodString;
-            taskId: zod.ZodString;
-            status: zod.ZodEnum<{
-                running: "running";
-                completed: "completed";
-                failed: "failed";
-                cancelled: "cancelled";
-                queued: "queued";
-                timed_out: "timed_out";
-            }>;
-            startedAt: zod.ZodNullable<zod.z.ZodISODateTime>;
-            finishedAt: zod.ZodNullable<zod.z.ZodISODateTime>;
-            exitCode: zod.ZodNullable<zod.ZodInt>;
-            output: zod.ZodNullable<zod.ZodString>;
-            errorCode: zod.ZodNullable<zod.ZodString>;
-            trigger: zod.ZodEnum<{
-                manual: "manual";
-                schedule: "schedule";
-                assistant: "assistant";
-            }>;
-        }, zod.z.core.$strict>, zod.ZodNull]>;
-        createdAt: zod.z.ZodISODateTime;
-        updatedAt: zod.z.ZodISODateTime;
-    }, zod.z.core.$strict>>;
-    taskId: zod.ZodOptional<zod.ZodString>;
-    cursor: zod.ZodOptional<zod.ZodString>;
-    frame: zod.ZodOptional<zod.ZodObject<{
-        path: zod.ZodString;
-        op: zod.ZodEnum<{
-            set: "set";
-            add: "add";
-            append: "append";
-        }>;
-        value: zod.ZodUnknown;
-    }, zod.z.core.$strict>>;
-    code: zod.ZodOptional<zod.ZodString>;
-    message: zod.ZodOptional<zod.ZodString>;
-}, zod.z.core.$strict>;
-export type RealtimeServerMessage = zod.input<typeof RealtimeServerMessage>;
-export type RealtimeServerMessageOutput = zod.output<typeof RealtimeServerMessage>;

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

@@ -1,64 +0,0 @@
-/**
- * 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 { FolderResource } from "./folderResource.zod.js";
-import { ItemFrame } from "./itemFrame.zod.js";
-import { TaskResource } from "./taskResource.zod.js";
-import { ThreadResource } from "./threadResource.zod.js";
-import { ThreadTurnResource } from "./threadTurnResource.zod.js";
-export const RealtimeServerMessage = zod
-    .strictObject({
-    type: zod.enum([
-        "subscribed",
-        "unsubscribed",
-        "thread.updated",
-        "thread.deleted",
-        "turn.updated",
-        "folder.updated",
-        "folder.deleted",
-        "task.updated",
-        "task.deleted",
-        "item.frame",
-        "resync",
-        "error",
-        "pong",
-    ]),
-    topic: zod.string().optional(),
-    thread: ThreadResource.optional(),
-    threadId: zod.string().optional(),
-    turn: ThreadTurnResource.optional(),
-    folder: FolderResource.optional(),
-    folderId: zod.string().optional(),
-    task: TaskResource.optional(),
-    taskId: zod.string().optional(),
-    cursor: zod
-        .string()
-        .optional()
-        .describe("For `item.frame`. Resubscribe from this cursor to continue after a reconnect."),
-    frame: ItemFrame.optional(),
-    code: zod.string().optional(),
-    message: zod.string().optional(),
-})
-    .describe("A message from the server. `type` determines which fields apply:\n\n- `subscribed` / `unsubscribed` — `topic`\n- `thread.updated` — `thread`; `thread.deleted` — `threadId`\n- `turn.updated` — `turn`, sent while a turn runs so its usage can be shown live\n- `folder.updated` — `folder`; `folder.deleted` — `folderId`\n- `task.updated` — `task`; `task.deleted` — `taskId`\n- `item.frame` — `threadId`, `cursor` and `frame`, an edit to the transcript\n- `resync` — `topic`; the client lost events and reads the current state again\n- `error` — `code` and `message`\n- `pong`");

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

@@ -1,32 +0,0 @@
-/**
- * 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 RealtimeTicketResource: zod.ZodObject<{
-    url: zod.ZodString;
-    ticket: zod.ZodString;
-    expiresAt: zod.z.ZodISODateTime;
-}, zod.z.core.$strict>;
-export type RealtimeTicketResource = zod.input<typeof RealtimeTicketResource>;
-export type RealtimeTicketResourceOutput = zod.output<typeof RealtimeTicketResource>;

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

@@ -1,30 +0,0 @@
-/**
- * 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 RealtimeTicketResource = zod.strictObject({
-    url: zod.string().describe("The WebSocket address, absolute or relative to the API origin."),
-    ticket: zod.string(),
-    expiresAt: zod.iso.datetime({ offset: true }),
-});

package/dist/notification/v1/generated/validators/authorizeRealtimeChannelRequestBody.zod.d.ts

@@ -1,70 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Notification API
- * Read the notifications this platform has sent you, and choose where each kind of notification
- * is delivered.
- *
- * Every service on the platform reports events here rather than contacting you directly. This
- * API is the single place where those events are read, and the single place where delivery is
- * configured.
- *
- * ## Authentication
- *
- * Every request carries a scoped token; see the `bearerAuth` security scheme.
- *
- * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
- * the token. Listing operations return everything addressed to you across every project by
- * default, because a notification is addressed to a person rather than to a project; pass
- * `scope=current_project` to narrow the result to the project in the token.
- *
- * ## Conventions
- *
- * - **Notifications are typed, and the type determines who receives it.** A type such as
- *   `compute.instance.provisioned` is addressed to whoever created the instance, while
- *   `monitoring.alert.raised` is addressed to every member of the project. The full catalogue is
- *   available from `GET /api/v1/notification-types` and is stable: a type identifier is never
- *   reused for a different event.
- * - **Text is rendered at read time from the language on your preferences.** Changing the
- *   language changes the text of everything already in the inbox. Messages already delivered by
- *   email or to an outbound channel are not rewritten, because they have already been sent.
- * - **Times inside rendered text are stated in UTC and say so.** There is no time zone setting.
- *   Clients that can determine the reader's time zone should present `created_at`, `occurred_at`
- *   and the timestamps in `params` — all of which are RFC 3339 — in local time instead. Email
- *   cannot do this, which is why the text it carries is explicit about being UTC.
- * - **Some types must reach you, and those cannot be muted or removed from email.** They are
- *   marked `mandatory` in the catalogue: types you would only find out about by signing in, when
- *   not finding out costs you something — a suspension, a deletion, a credential that expires.
- *   Everything else about them is still configurable, including adding channels of your own.
- * - **Deleting a preference restores the default; it does not turn the type off.** To stop
- *   receiving a type, set `muted` on it.
- * - **Outbound channels deliver nothing until they are verified.** Registering a channel does not
- *   contact it. Verification is a separate operation that sends one message, and only a channel
- *   that has acknowledged it receives anything afterwards.
- * - **Channel endpoints are never returned.** No operation, including the one that registers
- *   them, returns the address that was submitted. A channel entered incorrectly must be deleted
- *   and registered again.
- *
- * ## Rate and volume
- *
- * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
- * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
- * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
- * OpenAPI spec version: 1.0.0
- */
-import * as zod from "zod";
-export declare const authorizeRealtimeChannelRequestBodyChannelNameMax = 255;
-export declare const authorizeRealtimeChannelRequestBodySocketIdMax = 128;
-export declare const AuthorizeRealtimeChannelRequestBody: zod.ZodObject<{
-    channel_name: zod.ZodString;
-    socket_id: zod.ZodString;
-}, zod.z.core.$strict>;
-export type AuthorizeRealtimeChannelRequestBody = zod.input<typeof AuthorizeRealtimeChannelRequestBody>;
-export type AuthorizeRealtimeChannelRequestBodyOutput = zod.output<typeof AuthorizeRealtimeChannelRequestBody>;

package/dist/notification/v1/generated/validators/authorizeRealtimeChannelRequestBody.zod.js

@@ -1,76 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Notification API
- * Read the notifications this platform has sent you, and choose where each kind of notification
- * is delivered.
- *
- * Every service on the platform reports events here rather than contacting you directly. This
- * API is the single place where those events are read, and the single place where delivery is
- * configured.
- *
- * ## Authentication
- *
- * Every request carries a scoped token; see the `bearerAuth` security scheme.
- *
- * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
- * the token. Listing operations return everything addressed to you across every project by
- * default, because a notification is addressed to a person rather than to a project; pass
- * `scope=current_project` to narrow the result to the project in the token.
- *
- * ## Conventions
- *
- * - **Notifications are typed, and the type determines who receives it.** A type such as
- *   `compute.instance.provisioned` is addressed to whoever created the instance, while
- *   `monitoring.alert.raised` is addressed to every member of the project. The full catalogue is
- *   available from `GET /api/v1/notification-types` and is stable: a type identifier is never
- *   reused for a different event.
- * - **Text is rendered at read time from the language on your preferences.** Changing the
- *   language changes the text of everything already in the inbox. Messages already delivered by
- *   email or to an outbound channel are not rewritten, because they have already been sent.
- * - **Times inside rendered text are stated in UTC and say so.** There is no time zone setting.
- *   Clients that can determine the reader's time zone should present `created_at`, `occurred_at`
- *   and the timestamps in `params` — all of which are RFC 3339 — in local time instead. Email
- *   cannot do this, which is why the text it carries is explicit about being UTC.
- * - **Some types must reach you, and those cannot be muted or removed from email.** They are
- *   marked `mandatory` in the catalogue: types you would only find out about by signing in, when
- *   not finding out costs you something — a suspension, a deletion, a credential that expires.
- *   Everything else about them is still configurable, including adding channels of your own.
- * - **Deleting a preference restores the default; it does not turn the type off.** To stop
- *   receiving a type, set `muted` on it.
- * - **Outbound channels deliver nothing until they are verified.** Registering a channel does not
- *   contact it. Verification is a separate operation that sends one message, and only a channel
- *   that has acknowledged it receives anything afterwards.
- * - **Channel endpoints are never returned.** No operation, including the one that registers
- *   them, returns the address that was submitted. A channel entered incorrectly must be deleted
- *   and registered again.
- *
- * ## Rate and volume
- *
- * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
- * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
- * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
- * OpenAPI spec version: 1.0.0
- */
-import * as zod from "zod";
-export const authorizeRealtimeChannelRequestBodyChannelNameMax = 255;
-export const authorizeRealtimeChannelRequestBodySocketIdMax = 128;
-export const AuthorizeRealtimeChannelRequestBody = zod.strictObject({
-    channel_name: zod
-        .string()
-        .min(1)
-        .max(authorizeRealtimeChannelRequestBodyChannelNameMax)
-        .describe("The channel being subscribed to"),
-    socket_id: zod
-        .string()
-        .min(1)
-        .max(authorizeRealtimeChannelRequestBodySocketIdMax)
-        .describe("The connection identifier the realtime server assigned to this client"),
-});

package/dist/notification/v1/generated/validators/realtimeAuthResource.zod.d.ts

@@ -1,67 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Notification API
- * Read the notifications this platform has sent you, and choose where each kind of notification
- * is delivered.
- *
- * Every service on the platform reports events here rather than contacting you directly. This
- * API is the single place where those events are read, and the single place where delivery is
- * configured.
- *
- * ## Authentication
- *
- * Every request carries a scoped token; see the `bearerAuth` security scheme.
- *
- * **Neither the path nor the headers carry a `project_id`**: the current project is determined by
- * the token. Listing operations return everything addressed to you across every project by
- * default, because a notification is addressed to a person rather than to a project; pass
- * `scope=current_project` to narrow the result to the project in the token.
- *
- * ## Conventions
- *
- * - **Notifications are typed, and the type determines who receives it.** A type such as
- *   `compute.instance.provisioned` is addressed to whoever created the instance, while
- *   `monitoring.alert.raised` is addressed to every member of the project. The full catalogue is
- *   available from `GET /api/v1/notification-types` and is stable: a type identifier is never
- *   reused for a different event.
- * - **Text is rendered at read time from the language on your preferences.** Changing the
- *   language changes the text of everything already in the inbox. Messages already delivered by
- *   email or to an outbound channel are not rewritten, because they have already been sent.
- * - **Times inside rendered text are stated in UTC and say so.** There is no time zone setting.
- *   Clients that can determine the reader's time zone should present `created_at`, `occurred_at`
- *   and the timestamps in `params` — all of which are RFC 3339 — in local time instead. Email
- *   cannot do this, which is why the text it carries is explicit about being UTC.
- * - **Some types must reach you, and those cannot be muted or removed from email.** They are
- *   marked `mandatory` in the catalogue: types you would only find out about by signing in, when
- *   not finding out costs you something — a suspension, a deletion, a credential that expires.
- *   Everything else about them is still configurable, including adding channels of your own.
- * - **Deleting a preference restores the default; it does not turn the type off.** To stop
- *   receiving a type, set `muted` on it.
- * - **Outbound channels deliver nothing until they are verified.** Registering a channel does not
- *   contact it. Verification is a separate operation that sends one message, and only a channel
- *   that has acknowledged it receives anything afterwards.
- * - **Channel endpoints are never returned.** No operation, including the one that registers
- *   them, returns the address that was submitted. A channel entered incorrectly must be deleted
- *   and registered again.
- *
- * ## Rate and volume
- *
- * Delivery to outbound channels is limited per channel, and bursts of alerts about one server are
- * summarised rather than sent individually. Nothing is summarised in the inbox: it always holds
- * every notification. A notification that was summarised or suppressed is still readable here.
- *
- * ## One-time credentials
- *
- * Some notifications carry a reference to a credential rather than the credential itself — the
- * initial password of a newly created instance, for example. That credential is readable exactly
- * once, expires on its own, and is destroyed as soon as it has been read. Requesting it a second
- * time returns `CREDENTIAL_TICKET_CONSUMED`.
- * OpenAPI spec version: 1.0.0
- */
-import * as zod from "zod";
-export declare const RealtimeAuthResource: zod.ZodObject<{
-    auth: zod.ZodString;
-}, zod.z.core.$strict>;
-export type RealtimeAuthResource = zod.input<typeof RealtimeAuthResource>;
-export type RealtimeAuthResourceOutput = zod.output<typeof RealtimeAuthResource>;