@leaflow/sdk 0.0.0-dev.437.gc278ab8 → 0.0.0-dev.439.g15ccd50

package/dist/eventbus/v1/generated/validators/updateNamespaceRequest.zod.d.ts

@@ -0,0 +1,94 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Event Bus API
+ * Event definitions, versions, publishing, and realtime access.
+ *
+ * ## Definitions and messages
+ *
+ * An event is a definition: a name, a description, and one or more versions. A version carries a
+ * JSON Schema that every published payload must satisfy. Messages are not stored here and are
+ * not part of the event definition.
+ *
+ * Every event belongs to a namespace, and its name is the namespace's name, a dot, and at least a
+ * resource and an action, such as `acme.order.created`. A project creates its own namespaces and
+ * defines events in them. Platform namespaces, such as `leaflow.notification`, are maintained by
+ * platform services: their events are listed alongside the project's own and can be subscribed
+ * to, but cannot be changed or published here, and the namespaces cannot be changed or deleted.
+ * Events in a platform namespace are called platform events below.
+ *
+ * A version number never changes meaning. Adding optional properties is allowed within a version;
+ * a breaking change creates a new version. Publishing without a version uses the highest active
+ * version.
+ *
+ * ## Publishing
+ *
+ * Messages are published in batches of up to 64. A batch is validated as a whole: if any message
+ * is rejected, none is published. Publishing returns the identity of each message and does not
+ * wait for consumers. Messages are not stored and are not replayed: a consumer that connects
+ * later does not receive earlier messages.
+ *
+ * Messages published through this API are sent to the current project. A message may name one
+ * `subject`, a member of the project; it is then sent to that member only. Without a subject it is
+ * sent to every member of the project.
+ *
+ * Every publication names a `client_id`. It starts with the prefix returned with a realtime
+ * ticket, `user.{user_id}.project.{project_id}.`, followed by one segment chosen by the
+ * client, such as a random identifier per browser tab. Receivers get it unchanged, so a client
+ * can recognise its own messages. A client ID does not need to be unique: several connections
+ * may share one.
+ *
+ * ## Realtime
+ *
+ * Every message has a topic `{event}/{project_id|-}/{subject|-}/{key levels}`, where `-` stands
+ * for a missing recipient and the key, split at `/`, supplies the remaining levels. A topic filter
+ * uses `+` to match exactly one level and `#`, only as the last level, to match that level and
+ * every level below it, including none. For example, `{event}/{project_id}/-/#` matches every
+ * message sent to the members of a project, and `{event}/-/{user_id}/#` every message sent to one
+ * person outside any project.
+ *
+ * 1. Create a ticket with `POST /api/v1/realtime/tickets`, naming the events to receive. The
+ *    response lists the topic filters the ticket covers and the `client_id_prefix` to use. For a
+ *    platform event they cover messages sent to the caller, messages sent to no recipient and,
+ *    where the caller's permissions allow, messages sent within the project; for a project event
+ *    they cover messages sent within the project. Without a selected project, use
+ *    `POST /api/v1/account/realtime/tickets`; such a ticket covers only messages sent to the
+ *    caller or to no recipient, and cannot publish.
+ * 2. Open a WebSocket to `wss://eventbus.leaflow.cloud/realtime` and send, within 15 seconds:
+ *    `{"type":"authenticate","ticket":"…","client_id":"…"}`. The reply is
+ *    `{"type":"authenticated","client_id":"…","connection_id":"…","expires_at":"…"}`.
+ *    `connection_id` identifies this connection; it is assigned by EventBus and changes on
+ *    every reconnection.
+ * 3. Send `{"type":"subscribe","id":"…","topics":[…]}`. Each topic must be one of the returned
+ *    `topics` or lie within one of them, for example by naming a key level where the ticket has
+ *    `#`; a batch with any other topic is rejected as a whole. The reply is `subscribed`.
+ *    `unsubscribe` takes the same form and replies `unsubscribed`. Both may be sent at any time
+ *    while the connection is open.
+ * 4. Messages arrive as `{"type":"messages","messages":[…]}`, each element an `EventMessage`. A
+ *    message matching several subscriptions on one connection arrives once for each of them.
+ * 5. A connection may switch to another ticket of the same user at any time by sending
+ *    `authenticate` again: to renew before `expires_at`, to move from an account ticket to a
+ *    project ticket, or to move to another project. `client_id` may be omitted while the
+ *    `client_id_prefix` stays the same; when it changes, a client ID under the new prefix is
+ *    required. Subscriptions the new ticket does not cover are removed at once and reported in a
+ *    `{"type":"revoked","topics":[…]}` frame. A ticket for another user closes the connection
+ *    with code 4401, as does letting the ticket expire.
+ *
+ * A connection holding a project ticket may publish the project's own events with
+ * `{"type":"publish","id":"…","messages":[{"event":"…","key":"…","subject":"…","data":{…}}]}`;
+ * the reply is `published` with the identity of each message. `ping` is answered with `pong`.
+ * A rejected request is answered with `{"type":"error","id":"…","code":"…","message":"…"}`.
+ * Every reply carries the `id` of the request it answers.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const updateNamespaceRequestDescriptionMax = 1024;
+export declare const UpdateNamespaceRequest: zod.ZodObject<{
+    description: zod.ZodOptional<zod.ZodString>;
+    status: zod.ZodOptional<zod.ZodEnum<{
+        active: "active";
+        archived: "archived";
+    }>>;
+}, zod.z.core.$strict>;
+export type UpdateNamespaceRequest = zod.input<typeof UpdateNamespaceRequest>;
+export type UpdateNamespaceRequestOutput = zod.output<typeof UpdateNamespaceRequest>;

package/dist/eventbus/v1/generated/validators/updateNamespaceRequest.zod.js

@@ -0,0 +1,90 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Event Bus API
+ * Event definitions, versions, publishing, and realtime access.
+ *
+ * ## Definitions and messages
+ *
+ * An event is a definition: a name, a description, and one or more versions. A version carries a
+ * JSON Schema that every published payload must satisfy. Messages are not stored here and are
+ * not part of the event definition.
+ *
+ * Every event belongs to a namespace, and its name is the namespace's name, a dot, and at least a
+ * resource and an action, such as `acme.order.created`. A project creates its own namespaces and
+ * defines events in them. Platform namespaces, such as `leaflow.notification`, are maintained by
+ * platform services: their events are listed alongside the project's own and can be subscribed
+ * to, but cannot be changed or published here, and the namespaces cannot be changed or deleted.
+ * Events in a platform namespace are called platform events below.
+ *
+ * A version number never changes meaning. Adding optional properties is allowed within a version;
+ * a breaking change creates a new version. Publishing without a version uses the highest active
+ * version.
+ *
+ * ## Publishing
+ *
+ * Messages are published in batches of up to 64. A batch is validated as a whole: if any message
+ * is rejected, none is published. Publishing returns the identity of each message and does not
+ * wait for consumers. Messages are not stored and are not replayed: a consumer that connects
+ * later does not receive earlier messages.
+ *
+ * Messages published through this API are sent to the current project. A message may name one
+ * `subject`, a member of the project; it is then sent to that member only. Without a subject it is
+ * sent to every member of the project.
+ *
+ * Every publication names a `client_id`. It starts with the prefix returned with a realtime
+ * ticket, `user.{user_id}.project.{project_id}.`, followed by one segment chosen by the
+ * client, such as a random identifier per browser tab. Receivers get it unchanged, so a client
+ * can recognise its own messages. A client ID does not need to be unique: several connections
+ * may share one.
+ *
+ * ## Realtime
+ *
+ * Every message has a topic `{event}/{project_id|-}/{subject|-}/{key levels}`, where `-` stands
+ * for a missing recipient and the key, split at `/`, supplies the remaining levels. A topic filter
+ * uses `+` to match exactly one level and `#`, only as the last level, to match that level and
+ * every level below it, including none. For example, `{event}/{project_id}/-/#` matches every
+ * message sent to the members of a project, and `{event}/-/{user_id}/#` every message sent to one
+ * person outside any project.
+ *
+ * 1. Create a ticket with `POST /api/v1/realtime/tickets`, naming the events to receive. The
+ *    response lists the topic filters the ticket covers and the `client_id_prefix` to use. For a
+ *    platform event they cover messages sent to the caller, messages sent to no recipient and,
+ *    where the caller's permissions allow, messages sent within the project; for a project event
+ *    they cover messages sent within the project. Without a selected project, use
+ *    `POST /api/v1/account/realtime/tickets`; such a ticket covers only messages sent to the
+ *    caller or to no recipient, and cannot publish.
+ * 2. Open a WebSocket to `wss://eventbus.leaflow.cloud/realtime` and send, within 15 seconds:
+ *    `{"type":"authenticate","ticket":"…","client_id":"…"}`. The reply is
+ *    `{"type":"authenticated","client_id":"…","connection_id":"…","expires_at":"…"}`.
+ *    `connection_id` identifies this connection; it is assigned by EventBus and changes on
+ *    every reconnection.
+ * 3. Send `{"type":"subscribe","id":"…","topics":[…]}`. Each topic must be one of the returned
+ *    `topics` or lie within one of them, for example by naming a key level where the ticket has
+ *    `#`; a batch with any other topic is rejected as a whole. The reply is `subscribed`.
+ *    `unsubscribe` takes the same form and replies `unsubscribed`. Both may be sent at any time
+ *    while the connection is open.
+ * 4. Messages arrive as `{"type":"messages","messages":[…]}`, each element an `EventMessage`. A
+ *    message matching several subscriptions on one connection arrives once for each of them.
+ * 5. A connection may switch to another ticket of the same user at any time by sending
+ *    `authenticate` again: to renew before `expires_at`, to move from an account ticket to a
+ *    project ticket, or to move to another project. `client_id` may be omitted while the
+ *    `client_id_prefix` stays the same; when it changes, a client ID under the new prefix is
+ *    required. Subscriptions the new ticket does not cover are removed at once and reported in a
+ *    `{"type":"revoked","topics":[…]}` frame. A ticket for another user closes the connection
+ *    with code 4401, as does letting the ticket expire.
+ *
+ * A connection holding a project ticket may publish the project's own events with
+ * `{"type":"publish","id":"…","messages":[{"event":"…","key":"…","subject":"…","data":{…}}]}`;
+ * the reply is `published` with the identity of each message. `ping` is answered with `pong`.
+ * A rejected request is answered with `{"type":"error","id":"…","code":"…","message":"…"}`.
+ * Every reply carries the `id` of the request it answers.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+import { NamespaceStatus } from "./namespaceStatus.zod.js";
+export const updateNamespaceRequestDescriptionMax = 1024;
+export const UpdateNamespaceRequest = zod.strictObject({
+    description: zod.string().max(updateNamespaceRequestDescriptionMax).optional(),
+    status: NamespaceStatus.optional(),
+});

package/dist/notification/v1/generated/functions.d.ts

@@ -59,7 +59,7 @@
  * time returns `CREDENTIAL_TICKET_CONSUMED`.
  * OpenAPI spec version: 1.0.0
  */
-import type { AnnouncementListResource, AnnouncementReadResultResource, AuthorizeRealtimeChannelRequestBody, ChannelListResponseBody, ChannelResource, ConfirmEmailOverrideRequestBody, CountUnreadNotificationsParams, CreateChannelRequestBody, CredentialTicketResource, DeleteTypePreferenceParams, EmailOverrideCodeResource, Error, LengthAwarePageNotificationResource, ListNotificationsParams, ListTypePreferencesParams, ListUserChannelsParams, MarkNotificationsReadRequestBody, NotificationResource, NotificationTypeListResponseBody, PreferencesResource, RealtimeAuthResource, RealtimeConnectionResource, RevealedCredentialResource, TypePreferenceListResponseBody, TypePreferenceResource, UnreadCountResource, UpdateChannelRequestBody, UpdatePreferencesRequestBody, UpdateTypePreferenceParams, UpdateTypePreferenceRequestBody } from "./models.js";
+import type { AnnouncementListResource, AnnouncementReadResultResource, ChannelListResponseBody, ChannelResource, ConfirmEmailOverrideRequestBody, CountUnreadNotificationsParams, CreateChannelRequestBody, CredentialTicketResource, DeleteTypePreferenceParams, EmailOverrideCodeResource, Error, LengthAwarePageNotificationResource, ListNotificationsParams, ListTypePreferencesParams, ListUserChannelsParams, MarkNotificationsReadRequestBody, NotificationResource, NotificationTypeListResponseBody, PreferencesResource, RevealedCredentialResource, TypePreferenceListResponseBody, TypePreferenceResource, UnreadCountResource, UpdateChannelRequestBody, UpdatePreferencesRequestBody, UpdateTypePreferenceParams, UpdateTypePreferenceRequestBody } from "./models.js";
 export type HTTPStatusCode1xx = 100 | 101 | 102 | 103;
 export type HTTPStatusCode2xx = 200 | 201 | 202 | 203 | 204 | 205 | 206 | 207;
 export type HTTPStatusCode3xx = 300 | 301 | 302 | 303 | 304 | 305 | 307 | 308;
@@ -134,7 +134,8 @@ export type countUnreadNotificationsResponse = countUnreadNotificationsResponseS
 export declare const getCountUnreadNotificationsUrl: (params?: CountUnreadNotificationsParams) => string;
 /**
  * Returns the number of unread notifications. This is the value behind the badge in the
- * console, and it is also carried on every realtime event, so it does not normally need to be
+ * console, and it is also carried on every `notification.inbox.created` and
+ * `notification.inbox.read` message delivered by EventBus, so it does not normally need to be
  * requested on its own.
  * @summary Count unread notifications
  */
@@ -765,59 +766,3 @@ export declare const getRevealCredentialUrl: (ticketId: string) => string;
  * @summary Reveal a one-time credential
  */
 export declare const revealCredential: (ticketId: string, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<revealCredentialResponse>;
-export type describeRealtimeConnectionResponse200 = {
-    data: RealtimeConnectionResource;
-    status: 200;
-};
-export type describeRealtimeConnectionResponseDefault = {
-    data: Error;
-    status: Exclude<HTTPStatusCodes, 200>;
-};
-export type describeRealtimeConnectionResponseSuccess = describeRealtimeConnectionResponse200 & {
-    headers: Headers;
-};
-export type describeRealtimeConnectionResponseError = describeRealtimeConnectionResponseDefault & {
-    headers: Headers;
-};
-export type describeRealtimeConnectionResponse = describeRealtimeConnectionResponseSuccess | describeRealtimeConnectionResponseError;
-export declare const getDescribeRealtimeConnectionUrl: () => string;
-/**
- * Returns everything needed to open a realtime connection, and the names of the channels to
- * subscribe to. The parameters are not constants: they differ between environments, so they
- * must be requested rather than compiled in.
- *
- * Realtime delivery is an optimisation. Everything it announces is also readable through the
- * listing operations, so a client that cannot connect stays correct by polling or by
- * refreshing.
- * @summary Describe the realtime connection
- */
-export declare const describeRealtimeConnection: (options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<describeRealtimeConnectionResponse>;
-export type authorizeRealtimeChannelResponse200 = {
-    data: RealtimeAuthResource;
-    status: 200;
-};
-export type authorizeRealtimeChannelResponseDefault = {
-    data: Error;
-    status: Exclude<HTTPStatusCodes, 200>;
-};
-export type authorizeRealtimeChannelResponseSuccess = authorizeRealtimeChannelResponse200 & {
-    headers: Headers;
-};
-export type authorizeRealtimeChannelResponseError = authorizeRealtimeChannelResponseDefault & {
-    headers: Headers;
-};
-export type authorizeRealtimeChannelResponse = authorizeRealtimeChannelResponseSuccess | authorizeRealtimeChannelResponseError;
-export declare const getAuthorizeRealtimeChannelUrl: () => string;
-/**
- * Authorizes one subscription. Realtime clients call this on their own while subscribing; it
- * is not normally called directly.
- *
- * Only two channels are authorized: the one naming you, and the one naming the project in
- * the token. Any other channel returns `REALTIME_CHANNEL_FORBIDDEN`.
- *
- * **Authorization is evaluated once, when the subscription is established.** A subscription
- * already open is not revoked when project membership changes, so realtime events carry
- * identifiers and counts only, never the contents of a notification.
- * @summary Authorize a realtime channel subscription
- */
-export declare const authorizeRealtimeChannel: (authorizeRealtimeChannelRequestBody: AuthorizeRealtimeChannelRequestBody, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<authorizeRealtimeChannelResponse>;

package/dist/notification/v1/generated/functions.js

@@ -78,7 +78,8 @@ export const getCountUnreadNotificationsUrl = (params) => {
 };
 /**
  * Returns the number of unread notifications. This is the value behind the badge in the
- * console, and it is also carried on every realtime event, so it does not normally need to be
+ * console, and it is also carried on every `notification.inbox.created` and
+ * `notification.inbox.read` message delivered by EventBus, so it does not normally need to be
  * requested on its own.
  * @summary Count unread notifications
  */
@@ -722,66 +723,3 @@ export const revealCredential = async (ticketId, options, fetchFn) => {
     const data = body ? JSON.parse(body) : {};
     return { data, status: res.status, headers: res.headers };
 };
-export const getDescribeRealtimeConnectionUrl = () => {
-    return `https://notification.leaflow.cloud/api/v1/realtime`;
-};
-/**
- * Returns everything needed to open a realtime connection, and the names of the channels to
- * subscribe to. The parameters are not constants: they differ between environments, so they
- * must be requested rather than compiled in.
- *
- * Realtime delivery is an optimisation. Everything it announces is also readable through the
- * listing operations, so a client that cannot connect stays correct by polling or by
- * refreshing.
- * @summary Describe the realtime connection
- */
-export const describeRealtimeConnection = async (options, fetchFn) => {
-    const res = await (fetchFn ?? fetch)(getDescribeRealtimeConnectionUrl(), {
-        ...options,
-        method: "GET",
-    });
-    const body = [204, 205, 304].includes(res.status) ? null : await res.text();
-    const data = body ? JSON.parse(body) : {};
-    return { data, status: res.status, headers: res.headers };
-};
-export const getAuthorizeRealtimeChannelUrl = () => {
-    return `https://notification.leaflow.cloud/api/v1/realtime/auth`;
-};
-/**
- * Authorizes one subscription. Realtime clients call this on their own while subscribing; it
- * is not normally called directly.
- *
- * Only two channels are authorized: the one naming you, and the one naming the project in
- * the token. Any other channel returns `REALTIME_CHANNEL_FORBIDDEN`.
- *
- * **Authorization is evaluated once, when the subscription is established.** A subscription
- * already open is not revoked when project membership changes, so realtime events carry
- * identifiers and counts only, never the contents of a notification.
- * @summary Authorize a realtime channel subscription
- */
-export const authorizeRealtimeChannel = async (authorizeRealtimeChannelRequestBody, options, fetchFn) => {
-    const getHeaders = (h) => {
-        if (!h)
-            return {};
-        if (h instanceof Headers)
-            return Object.fromEntries(h.entries());
-        if (Symbol.iterator in h) {
-            return Object.fromEntries(Array.from(h, (entry) => Array.from(entry)));
-        }
-        const headers = {};
-        for (const [name, value] of Object.entries(h)) {
-            if (value !== undefined)
-                headers[name] = value;
-        }
-        return headers;
-    };
-    const res = await (fetchFn ?? fetch)(getAuthorizeRealtimeChannelUrl(), {
-        ...options,
-        method: "POST",
-        headers: { "Content-Type": "application/json", ...getHeaders(options?.headers) },
-        body: JSON.stringify(authorizeRealtimeChannelRequestBody),
-    });
-    const body = [204, 205, 304].includes(res.status) ? null : await res.text();
-    const data = body ? JSON.parse(body) : {};
-    return { data, status: res.status, headers: res.headers };
-};

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

@@ -588,53 +588,6 @@ export interface RevealedCredentialResource {
      */
     username: string | null;
 }
-/**
- * Everything needed to open a realtime connection. The connection speaks the Pusher channels
- * protocol, so any client library for it works.
- */
-export interface RealtimeConnectionResource {
-    /** The path a client posts to while subscribing, relative to this API */
-    auth_path: string;
-    /** The cluster name some client libraries require; empty when the deployment does not use one */
-    cluster: string;
-    /** False when realtime delivery is not configured in this deployment. Every other field is empty and clients should not attempt to connect */
-    enabled: boolean;
-    host: string;
-    /** The application key, which is public and identifies the deployment rather than the caller */
-    key: string;
-    port: number;
-    /**
-     * The channel carrying announcements. It is public: subscribing to it needs no
-     * authorization, because an announcement is addressed to everybody. The events on it
-     * carry an identifier and nothing else, so a client fetches the list and sees the
-     * announcements it is entitled to
-     */
-    announcements_channel: string;
-    /** The channel carrying events about the project in the token; empty when the token names no project */
-    project_channel: string;
-    /** Whether to connect over TLS */
-    secure: boolean;
-    /** The channel carrying events addressed to you */
-    user_channel: string;
-}
-export interface AuthorizeRealtimeChannelRequestBody {
-    /**
-     * The channel being subscribed to
-     * @minLength 1
-     * @maxLength 255
-     */
-    channel_name: string;
-    /**
-     * The connection identifier the realtime server assigned to this client
-     * @minLength 1
-     * @maxLength 128
-     */
-    socket_id: string;
-}
-export interface RealtimeAuthResource {
-    /** The authorization token for this subscription, passed back to the realtime server by the client library */
-    auth: string;
-}
 /**
  * Pagination metadata for stable numbered pages. total_count is returned only when the operation can determine it without an unbounded scan.
  */

package/dist/notification/v1/generated/schemas.zod.d.ts

@@ -105,7 +105,8 @@ export declare const MarkNotificationsReadBody: zod.ZodObject<{
 }, zod.z.core.$strict>;
 /**
  * Returns the number of unread notifications. This is the value behind the badge in the
- * console, and it is also carried on every realtime event, so it does not normally need to be
+ * console, and it is also carried on every `notification.inbox.created` and
+ * `notification.inbox.read` message delivered by EventBus, so it does not normally need to be
  * requested on its own.
  * @summary Count unread notifications
  */
@@ -382,19 +383,3 @@ export declare const DescribeCredentialTicketParams: zod.ZodObject<{
 export declare const RevealCredentialParams: zod.ZodObject<{
     ticketId: zod.ZodUUID;
 }, zod.z.core.$strict>;
-/**
- * Authorizes one subscription. Realtime clients call this on their own while subscribing; it
- * is not normally called directly.
- *
- * Only two channels are authorized: the one naming you, and the one naming the project in
- * the token. Any other channel returns `REALTIME_CHANNEL_FORBIDDEN`.
- *
- * **Authorization is evaluated once, when the subscription is established.** A subscription
- * already open is not revoked when project membership changes, so realtime events carry
- * identifiers and counts only, never the contents of a notification.
- * @summary Authorize a realtime channel subscription
- */
-export declare const AuthorizeRealtimeChannelBody: zod.ZodObject<{
-    channel_name: zod.ZodString;
-    socket_id: zod.ZodString;
-}, zod.z.core.$strict>;

package/dist/notification/v1/generated/schemas.zod.js

@@ -60,7 +60,6 @@
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";
-import { AuthorizeRealtimeChannelRequestBody } from "./validators/authorizeRealtimeChannelRequestBody.zod.js";
 import { ConfirmEmailOverrideRequestBody } from "./validators/confirmEmailOverrideRequestBody.zod.js";
 import { CreateChannelRequestBody } from "./validators/createChannelRequestBody.zod.js";
 import { MarkNotificationsReadRequestBody } from "./validators/markNotificationsReadRequestBody.zod.js";
@@ -128,7 +127,8 @@ export const ListNotificationsQueryParams = zod.strictObject({
 export const MarkNotificationsReadBody = MarkNotificationsReadRequestBody;
 /**
  * Returns the number of unread notifications. This is the value behind the badge in the
- * console, and it is also carried on every realtime event, so it does not normally need to be
+ * console, and it is also carried on every `notification.inbox.created` and
+ * `notification.inbox.read` message delivered by EventBus, so it does not normally need to be
  * requested on its own.
  * @summary Count unread notifications
  */
@@ -397,16 +397,3 @@ export const DescribeCredentialTicketParams = zod.strictObject({
 export const RevealCredentialParams = zod.strictObject({
     ticketId: zod.uuid().describe("The one-time credential"),
 });
-/**
- * Authorizes one subscription. Realtime clients call this on their own while subscribing; it
- * is not normally called directly.
- *
- * Only two channels are authorized: the one naming you, and the one naming the project in
- * the token. Any other channel returns `REALTIME_CHANNEL_FORBIDDEN`.
- *
- * **Authorization is evaluated once, when the subscription is established.** A subscription
- * already open is not revoked when project membership changes, so realtime events carry
- * identifiers and counts only, never the contents of a notification.
- * @summary Authorize a realtime channel subscription
- */
-export const AuthorizeRealtimeChannelBody = AuthorizeRealtimeChannelRequestBody;

package/dist/routes.d.ts

@@ -494,22 +494,6 @@ export declare const routes: readonly [{
     readonly operationId: "update-settings";
     readonly securityScheme: "ScopedToken";
     readonly upstreamUrl: "https://assistant.leaflow.cloud";
-}, {
-    readonly service: "assistant";
-    readonly contract: "assistant";
-    readonly method: "POST";
-    readonly path: "/api/v1/realtime/tickets";
-    readonly operationId: "create-realtime-ticket";
-    readonly securityScheme: "ScopedToken";
-    readonly upstreamUrl: "https://assistant.leaflow.cloud";
-}, {
-    readonly service: "assistant";
-    readonly contract: "assistant";
-    readonly method: "GET";
-    readonly path: "/api/v1/realtime";
-    readonly operationId: "open-realtime";
-    readonly securityScheme: null;
-    readonly upstreamUrl: "https://assistant.leaflow.cloud";
 }, {
     readonly service: "assistant";
     readonly contract: "assistant";
@@ -782,6 +766,14 @@ export declare const routes: readonly [{
     readonly operationId: "submit-weixin-verify-code";
     readonly securityScheme: "ScopedToken";
     readonly upstreamUrl: "https://assistant.leaflow.cloud";
+}, {
+    readonly service: "assistant";
+    readonly contract: "assistant";
+    readonly method: "POST";
+    readonly path: "/api/v1/threads/{thread}/presence";
+    readonly operationId: "renew-thread-presence";
+    readonly securityScheme: "ScopedToken";
+    readonly upstreamUrl: "https://assistant.leaflow.cloud";
 }, {
     readonly service: "billing";
     readonly contract: "billing";
@@ -2757,6 +2749,46 @@ export declare const routes: readonly [{
     readonly operationId: "delete-record-set";
     readonly securityScheme: "ScopedToken";
     readonly upstreamUrl: "https://dns.leaflow.cloud";
+}, {
+    readonly service: "eventbus";
+    readonly contract: "eventbus";
+    readonly method: "GET";
+    readonly path: "/api/v1/namespaces";
+    readonly operationId: "list-namespaces";
+    readonly securityScheme: "ScopedToken";
+    readonly upstreamUrl: "https://eventbus.leaflow.cloud";
+}, {
+    readonly service: "eventbus";
+    readonly contract: "eventbus";
+    readonly method: "POST";
+    readonly path: "/api/v1/namespaces";
+    readonly operationId: "create-namespace";
+    readonly securityScheme: "ScopedToken";
+    readonly upstreamUrl: "https://eventbus.leaflow.cloud";
+}, {
+    readonly service: "eventbus";
+    readonly contract: "eventbus";
+    readonly method: "GET";
+    readonly path: "/api/v1/namespaces/{namespaceName}";
+    readonly operationId: "get-namespace";
+    readonly securityScheme: "ScopedToken";
+    readonly upstreamUrl: "https://eventbus.leaflow.cloud";
+}, {
+    readonly service: "eventbus";
+    readonly contract: "eventbus";
+    readonly method: "PATCH";
+    readonly path: "/api/v1/namespaces/{namespaceName}";
+    readonly operationId: "update-namespace";
+    readonly securityScheme: "ScopedToken";
+    readonly upstreamUrl: "https://eventbus.leaflow.cloud";
+}, {
+    readonly service: "eventbus";
+    readonly contract: "eventbus";
+    readonly method: "DELETE";
+    readonly path: "/api/v1/namespaces/{namespaceName}";
+    readonly operationId: "delete-namespace";
+    readonly securityScheme: "ScopedToken";
+    readonly upstreamUrl: "https://eventbus.leaflow.cloud";
 }, {
     readonly service: "eventbus";
     readonly contract: "eventbus";
@@ -2809,8 +2841,8 @@ export declare const routes: readonly [{
     readonly service: "eventbus";
     readonly contract: "eventbus";
     readonly method: "POST";
-    readonly path: "/api/v1/events/{eventName}:publish";
-    readonly operationId: "publish-event";
+    readonly path: "/api/v1/events:publish";
+    readonly operationId: "publish-events";
     readonly securityScheme: "ScopedToken";
     readonly upstreamUrl: "https://eventbus.leaflow.cloud";
 }, {
@@ -2821,6 +2853,14 @@ export declare const routes: readonly [{
     readonly operationId: "create-realtime-ticket";
     readonly securityScheme: "ScopedToken";
     readonly upstreamUrl: "https://eventbus.leaflow.cloud";
+}, {
+    readonly service: "eventbus";
+    readonly contract: "eventbus";
+    readonly method: "POST";
+    readonly path: "/api/v1/account/realtime/tickets";
+    readonly operationId: "create-account-realtime-ticket";
+    readonly securityScheme: "AccessToken";
+    readonly upstreamUrl: "https://eventbus.leaflow.cloud";
 }, {
     readonly service: "iam";
     readonly contract: "iam";
@@ -3941,22 +3981,6 @@ export declare const routes: readonly [{
     readonly operationId: "reveal-credential";
     readonly securityScheme: "ScopedToken";
     readonly upstreamUrl: "https://notification.leaflow.cloud";
-}, {
-    readonly service: "notification";
-    readonly contract: "notification";
-    readonly method: "GET";
-    readonly path: "/api/v1/realtime";
-    readonly operationId: "describe-realtime-connection";
-    readonly securityScheme: "ScopedToken";
-    readonly upstreamUrl: "https://notification.leaflow.cloud";
-}, {
-    readonly service: "notification";
-    readonly contract: "notification";
-    readonly method: "POST";
-    readonly path: "/api/v1/realtime/auth";
-    readonly operationId: "authorize-realtime-channel";
-    readonly securityScheme: "ScopedToken";
-    readonly upstreamUrl: "https://notification.leaflow.cloud";
 }, {
     readonly service: "support";
     readonly contract: "support";