@vercel/board 0.25.0 → 0.26.0

package/dist/{server-BgK1sgj7.mjs → server-Bphio_82.mjs}

@@ -1,5 +1,5 @@
-import { t as createBoard } from "./exports-ByvYtxFT.mjs";
-import { t as http } from "./backend-http-Cs-UKpYp.mjs";
+import { t as createBoard } from "./exports-NFjBgIT2.mjs";
+import { t as http } from "./backend-http-F0W6e36G.mjs";
 //#region src/server/index.ts
 /**
 * The handle on a board. With a `backend`, the board lives there: `a2()` keeps it in this
@@ -9,8 +9,8 @@ import { t as http } from "./backend-http-Cs-UKpYp.mjs";
 function board(options = {}) {
 	return createBoard(options, {
 		http: () => http(),
-		sync: () => import("./engine-SeaJ_CIY.mjs"),
-		serving: () => import("./serving-rXQcEgTO.mjs")
+		sync: () => import("./engine-ROa7-IQY.mjs"),
+		serving: () => import("./serving-CvOWEym2.mjs")
 	});
 }
 //#endregion

package/dist/{serving-rXQcEgTO.mjs → serving-CvOWEym2.mjs}

@@ -1,2 +1,2 @@
-import { i as ownTeamId, n as discoveryIdentity, r as ownProjectId, t as oidcTokens } from "./tokens-U-XRlEfq.mjs";
+import { i as ownTeamId, n as discoveryIdentity, r as ownProjectId, t as oidcTokens } from "./tokens-BuCU-61R.mjs";
 export { discoveryIdentity, oidcTokens, ownProjectId, ownTeamId };

package/dist/sync-github.d.mts

@@ -1,5 +1,5 @@
-import { S as SyncUnit, _ as withUserTokens, d as ResolvedTarget, f as SyncContext, h as UserTokens, o as ProviderPost, r as ProviderDelivery, y as SyncFn } from "./provider-C_sj4-GL.mjs";
-import { n as ChatSyncProvider } from "./chat-provider-6eYkL2ef.mjs";
+import { S as SyncUnit, _ as withUserTokens, d as ResolvedTarget, f as SyncContext, h as UserTokens, o as ProviderPost, r as ProviderDelivery, y as SyncFn } from "./provider-Cdg1qadh.mjs";
+import { n as ChatSyncProvider } from "./chat-provider-DsNEBQiA.mjs";
 import { z } from "zod";
 import { Adapter } from "chat";
 //#region src/sync/github.d.ts

package/dist/sync-kapso.d.mts

@@ -1,5 +1,5 @@
-import { S as SyncUnit, f as SyncContext, y as SyncFn } from "./provider-C_sj4-GL.mjs";
-import { n as ChatSyncProvider, t as ChatInput } from "./chat-provider-6eYkL2ef.mjs";
+import { S as SyncUnit, f as SyncContext, y as SyncFn } from "./provider-Cdg1qadh.mjs";
+import { n as ChatSyncProvider, t as ChatInput } from "./chat-provider-DsNEBQiA.mjs";
 import { z } from "zod";
 import { Adapter } from "chat";
 //#region src/sync/kapso.d.ts

package/dist/sync-linear.d.mts

@@ -1,5 +1,5 @@
-import { S as SyncUnit, c as ReceivedEvent, d as ResolvedTarget, f as SyncContext, o as ProviderPost, r as ProviderDelivery, y as SyncFn } from "./provider-C_sj4-GL.mjs";
-import { n as ChatSyncProvider, t as ChatInput } from "./chat-provider-6eYkL2ef.mjs";
+import { S as SyncUnit, c as ReceivedEvent, d as ResolvedTarget, f as SyncContext, o as ProviderPost, r as ProviderDelivery, y as SyncFn } from "./provider-Cdg1qadh.mjs";
+import { n as ChatSyncProvider, t as ChatInput } from "./chat-provider-DsNEBQiA.mjs";
 import { z } from "zod";
 import { Adapter } from "chat";
 //#region src/sync/linear.d.ts

package/dist/sync-slack.d.mts

@@ -1,6 +1,6 @@
-import { f as ExternalLink } from "./folds-CRYY14kc.mjs";
-import { C as channels, _ as withUserTokens, d as ResolvedTarget, f as SyncContext, h as UserTokens, o as ProviderPost, r as ProviderDelivery, y as SyncFn } from "./provider-C_sj4-GL.mjs";
-import { n as ChatSyncProvider, t as ChatInput } from "./chat-provider-6eYkL2ef.mjs";
+import { f as ExternalLink } from "./folds-jS9wlh9_.mjs";
+import { C as channels, _ as withUserTokens, d as ResolvedTarget, f as SyncContext, h as UserTokens, o as ProviderPost, r as ProviderDelivery, y as SyncFn } from "./provider-Cdg1qadh.mjs";
+import { n as ChatSyncProvider, t as ChatInput } from "./chat-provider-DsNEBQiA.mjs";
 import { z } from "zod";
 import { Adapter } from "chat";
 //#region src/sync/slack.d.ts

package/dist/sync.chat.d.mts

@@ -1,2 +1,2 @@
-import { i as externalAuthor, n as ChatSyncProvider, r as ChatTransport, t as ChatInput } from "./chat-provider-6eYkL2ef.mjs";
+import { i as externalAuthor, n as ChatSyncProvider, r as ChatTransport, t as ChatInput } from "./chat-provider-DsNEBQiA.mjs";
 export { ChatInput, ChatSyncProvider, ChatTransport, externalAuthor };

package/dist/sync.d.mts

@@ -1,3 +1,3 @@
-import { d as ExternalFile, l as ExternalAuthor, u as ExternalEvent } from "./folds-CRYY14kc.mjs";
-import { A as SyncOverrides, C as channels, D as EventBase, E as render, M as SyncRoot, N as envelope, O as ProviderEvent, P as eventSchema, S as SyncUnit, T as mirror, _ as withUserTokens, a as ProviderOptions, b as SyncIn, c as ReceivedEvent, d as ResolvedTarget, f as SyncContext, g as connectUserTokens, h as UserTokens, i as ProviderFile, j as SyncResult, k as RootOverride, l as RenderInput, m as UnreadableError, n as FileDelivery, o as ProviderPost, p as SyncProvider, r as ProviderDelivery, s as Receive, u as Renderer, v as Sync, w as into, x as SyncOut, y as SyncFn } from "./provider-C_sj4-GL.mjs";
+import { d as ExternalFile, l as ExternalAuthor, u as ExternalEvent } from "./folds-jS9wlh9_.mjs";
+import { A as SyncOverrides, C as channels, D as EventBase, E as render, M as SyncRoot, N as envelope, O as ProviderEvent, P as eventSchema, S as SyncUnit, T as mirror, _ as withUserTokens, a as ProviderOptions, b as SyncIn, c as ReceivedEvent, d as ResolvedTarget, f as SyncContext, g as connectUserTokens, h as UserTokens, i as ProviderFile, j as SyncResult, k as RootOverride, l as RenderInput, m as UnreadableError, n as FileDelivery, o as ProviderPost, p as SyncProvider, r as ProviderDelivery, s as Receive, u as Renderer, v as Sync, w as into, x as SyncOut, y as SyncFn } from "./provider-Cdg1qadh.mjs";
 export { EventBase, type ExternalAuthor, ExternalEvent, type ExternalFile, type FileDelivery, type ProviderDelivery, type ProviderEvent, type ProviderFile, type ProviderOptions, type ProviderPost, type Receive, ReceivedEvent, type RenderInput, type Renderer, ResolvedTarget, type RootOverride, type Sync, type SyncContext, type SyncFn, type SyncIn, type SyncOut, SyncOverrides, SyncProvider, type SyncResult, type SyncRoot, type SyncUnit, UnreadableError, type UserTokens, channels, connectUserTokens, envelope, eventSchema, into, mirror, render, withUserTokens };

package/dist/{tokens-U-XRlEfq.mjs → tokens-BuCU-61R.mjs}

@@ -1,5 +1,5 @@
-import { l as unauthorized } from "./errors-Bven0k29.mjs";
-import { f as markVerified, m as trustedIssuers, n as TOKENS, r as VERCEL_ISSUER, u as issuerName } from "./auth-BwWH3Twu.mjs";
+import { l as unauthorized } from "./errors-CusN4x2l.mjs";
+import { f as markVerified, m as trustedIssuers, n as TOKENS, r as VERCEL_ISSUER, u as issuerName } from "./auth-lTkOgvcE.mjs";
 import { createRemoteJWKSet, decodeJwt, jwtVerify } from "jose";
 //#region src/server/identity.ts
 let fromDisk;

package/dist/{types-8yq2VnKI.d.mts → types-aCAf6lGU.d.mts}

@@ -1,4 +1,4 @@
-import { a as ExternalCopy, c as SyncedThread, g as BoardEvent, o as Message } from "./folds-CRYY14kc.mjs";
+import { a as ExternalCopy, c as SyncedThread, g as BoardEvent, o as Message } from "./folds-jS9wlh9_.mjs";
 import { t as A2Store } from "./store-D0MhBvg6-4Z2L0Kqd.mjs";
 //#region src/store/types.d.ts
 /**

package/dist/{watchers-hash-C4CJg7K1.mjs → watchers-hash-BfDPW95j.mjs}

@@ -1,8 +1,8 @@
 import { n as DIRECT_UPLOAD_BYTES_MAX, t as ATTACHMENT_BYTES_MAX } from "./files-SniSmeEr.mjs";
 import { S as storable, a as AttachmentId, c as ChannelPath, d as LabelKey, g as MessageText, l as Emoji, m as MESSAGE_TEXT_MAX, n as ActorId, p as Labels, x as platformAvatar } from "./schemas-Be08nyfW.mjs";
 import { a as Link, i as ExternalTarget, n as ExternalEvent, o as Origin, t as ExternalAuthor } from "./external-BV_cUncs.mjs";
-import { r as badRequest, t as HttpError } from "./errors-Bven0k29.mjs";
-import { o as options } from "./commands-BtL4jFq8.mjs";
+import { r as badRequest, t as HttpError } from "./errors-CusN4x2l.mjs";
+import { o as options } from "./commands-nEG47RM_.mjs";
 import { z } from "zod";
 //#region src/api/routes.ts
 /**
@@ -662,7 +662,7 @@ const routes = {
 const SYNC = "@sync";
 //#endregion
 //#region src/version.ts
-const VERSION = "0.25.0";
+const VERSION = "0.26.0";
 //#endregion
 //#region src/server/routing.ts
 /** board()'s own routes: the files it serves, and sync's, which run where board() does. */
@@ -865,7 +865,7 @@ const FILTER_FLAGS = {
 	by: options.by,
 	mentions: options.mentions,
 	label: options.label,
-	from: options.from,
+	source: options.source,
 	text: options.text
 };
 /** `--mentions` alone means mentions of me; `--mentions @ada`, mentions of ada. */
@@ -961,7 +961,7 @@ function parseWatchTail(expression) {
 		...values.by ? { by: values.by.replace(/^@/, "") } : {},
 		...values.mentions ? { mentions: values.mentions.replace(/^@/, "") } : {},
 		...values.label?.length ? { label: values.label } : {},
-		...values.from ? { from: values.from } : {},
+		...values.source ? { from: values.source } : {},
 		...values.text ? { text: values.text } : {}
 	});
 	if (!parsed.success) {

package/docs/01-board/04-messages.md

@@ -164,7 +164,7 @@ await team.reply('812', { text: 'fixed, see after', attachments: [shot] })
 A retry shouldn't post twice. Give a post or reply an ID of your own:
 
 ```bash
-vb post deploys "a1b2c3 is live" --id deploy-a1b2c3
+vb post deploys "a1b2c3 is live" --idempotency-key deploy-a1b2c3
 ```
 
 The same ID with the same write returns the message it already posted. The same

package/docs/01-board/05-reading.md

@@ -75,14 +75,14 @@ read includes it.
 | `--re <id>` | the thread rooted at `<id>`: the root and its replies |
 | `--by <handle>` | messages by that actor: a handle without the `@`, or an exact actor ID |
 | `--mentions` | messages that mention you; `--mentions @ada` for someone else |
-| `--from <source>` | where it was written: a sync key (`slack`, `github`), or `board` |
+| `--source <source>` | where it was written: a sync key (`slack`, `github`), or `board` |
 | `--label <key>` | messages with that label; `key=value`, or `key=a\|b` for either |
 | `--text <words>` | text containing the words, case-insensitive (a substring, not search) |
 | `--after <id>` | messages after that message ID or cursor; for `read`, threads with activity after it |
 
 ```bash
 vb read prs --label state=open                  # what's pending
-vb read issues --label tag.bug --from github
+vb read issues --label tag.bug --source github
 vb read --mentions                              # everywhere I'm mentioned
 vb read errors-www --by ada --text ENOTFOUND
 ```

package/docs/01-board/06-watchers.md

@@ -21,7 +21,7 @@ const team = board({
   // sync as in Sync
   watch: {
     triage: {
-      tail: 'firehose --from slack',
+      tail: 'firehose --source slack',
       run: async ({ event, board }) => {
         if (event.type === 'message.posted' && event.message?.re === null)
           await board.reply(event.message.id, 'Thanks! Tracking it.') // synced to the Slack thread
@@ -37,13 +37,13 @@ export const { scheduler } = backend
 would print, exactly as `vb tail --json` prints it. Try it in a terminal first:
 
 ```bash
-vb tail firehose --from slack --json
+vb tail firehose --source slack --json
 ```
 
 ## The expression
 
 A channel (or `prefix/` for a subtree) and the shared
-[filters](./05-reading.md#filters): `--re`, `--by`, `--mentions`, `--from`,
+[filters](./05-reading.md#filters): `--re`, `--by`, `--mentions`, `--source`,
 `--label`, `--text`, and `--all`.
 
 - **Positions aren't filters.** A watcher starts at the head when it's deployed

package/docs/02-sync/01-overview.md

@@ -95,7 +95,7 @@ see [Sync functions](./02-functions.md).
 
 **Entry keys** (`slack`, `github`, or `acme` for a second Slack workspace) are
 names you choose; the adapter decides the platform. The key appears in external
-IDs (`acme:C0999XYZ:1727.9`), in sync targets, in `--from` filters, and in the
+IDs (`acme:C0999XYZ:1727.9`), in sync targets, in `--source` filters, and in the
 webhook path (`/webhooks/acme`).
 
 **Map keys** are the platform's names or IDs: `'#prs'` or `'C0123ABC'` for
@@ -303,7 +303,7 @@ written to the log. It needs `post` and `read` in the thread's channel.
 vb sources                              # the board's sync entries and their platforms
 vb inbox slack                          # raw platform events, newest first: did Slack send it?
 vb inbox slack '#errors-www' --limit 5
-vb tail --from slack --all              # board events from Slack, delivery receipts included
+vb tail --source slack --all              # board events from Slack, delivery receipts included
 ```
 
 `vb inbox` needs `sync` in every channel for the board's own inbox, and every

package/docs/03-guides/03-ci.md

@@ -24,7 +24,7 @@ jobs:
       - uses: actions/checkout@v4
       # your deploy steps…
       - if: failure()
-        run: npx -y @vercel/board post errors-www "deploy failed on $SHA" --label source=ci --id "deploy-$SHA"
+        run: npx -y @vercel/board post errors-www "deploy failed on $SHA" --label source=ci --idempotency-key "deploy-$SHA"
         env:
           BOARD_URL: https://team.example/api/board
           SHA: ${{ github.sha }}
@@ -34,7 +34,7 @@ jobs:
   whose audience is the board's URL, so it's good for that board and nothing
   else. Without `id-token: write`, GitHub gives the job no token, so the CLI
   falls through to a `vercel login` the runner doesn't have, and fails.
-- **`--id` makes a retried step post once.** The same ID with the same write
+- **`--idempotency-key` makes a retried step post once.** The same ID with the same write
   returns the message already posted.
 - **The post is an ordinary thread.** If `errors-www` mirrors a Slack channel,
   it lands there, and a reply in Slack reaches the board.

package/docs/03-guides/04-triage.md

@@ -18,10 +18,10 @@ messages.
 
 ```bash
 # in a terminal:
-vb tail firehose --from slack --json
+vb tail firehose --source slack --json
 ```
 
-`tail` prints one line of JSON per event, live, until Ctrl-C. `--from slack`
+`tail` prints one line of JSON per event, live, until Ctrl-C. `--source slack`
 keeps messages that came from Slack. Each line carries the event and the
 message it concerns, as it is after the event:
 
@@ -38,7 +38,7 @@ report is a `message.posted` whose message has `re: null`: a thread root.
 
 ```bash
 # triage.sh: runs until you stop it
-vb tail firehose --from slack --json | while read -r event; do
+vb tail firehose --source slack --json | while read -r event; do
   [ "$(jq -r '.type' <<<"$event")" = "message.posted" ] || continue
   [ "$(jq -r '.message.re' <<<"$event")" = "null" ] || continue
   id=$(jq -r '.message.id' <<<"$event")
@@ -63,7 +63,7 @@ prints it, and exits, so each turn handles one event. Every event carries a
 ```bash
 # triage-turn.sh: one event per run
 last=$(cat .triage-cursor 2>/dev/null)
-next=$(vb wait firehose --from slack ${last:+--after "$last"} --json --timeout 1h) || exit 0
+next=$(vb wait firehose --source slack ${last:+--after "$last"} --json --timeout 1h) || exit 0
 jq -r '.cursor' <<<"$next" > .triage-cursor
 
 [ "$(jq -r '.type' <<<"$next")" = "message.posted" ] || exit 0
@@ -117,7 +117,7 @@ const team = board({
   // sync: { slack: slack('slack/acme', channels({ '#firehose': 'firehose' })) },
   watch: {
     triage: {
-      tail: 'firehose --from slack',
+      tail: 'firehose --source slack',
       run: async ({ event, board }) => {
         const message = event.message
         if (event.type !== 'message.posted' || !message || message.re !== null) return

package/docs/04-reference/01-cli.md

@@ -47,6 +47,11 @@ const code = await createApp({
   onError: (failure, { json }) => console.error(json ? JSON.stringify(failure) : failureLines(failure).join('\n')),
   // { reason, message }: a write that went through, with something to say. With --json, it's in the result.
   onWarning: (warning) => console.error(warning.message),
+  // Your Vercel login, and the team whose board to use when --scope names none, as this CLI
+  // resolves its own: asked for only when a request needs them. Help, a typo, or misuse never asks.
+  // A login that throws fails the request: board never falls back to `vercel login`'s.
+  login: async () => process.env.VERCEL_AUTH_TOKEN!,
+  team: async () => process.env.VERCEL_ORG_ID ?? null,
 }).run(process.argv.slice(3))
 ```
 
@@ -485,7 +490,7 @@ schedules that reply in that thread. `--all` adds done and canceled ones.
 ### post
 
 ```text
-vb post <channel|id> ["<text>"] [--label k=v]... [--attach <file>]... [--sync <target>]... [--no-sync] [--id <key>]
+vb post <channel|id> ["<text>"] [--label k=v]... [--attach <file>]... [--sync <target>]... [--no-sync] [--idempotency-key <key>]
 ```
 
 Starts a thread. The channel is created by its first post. Given a message ID
@@ -499,7 +504,7 @@ for new threads only.
 | `--attach <file>` | uploads a file (at most 4 MB, or 100 MB on a board whose blob store takes direct uploads; 10 per message) and attaches it. Every file is checked before any uploads. A board that keeps no files refuses: ``error: this board keeps no files: pass `blob` to `a2()` `` |
 | `--sync <target>` | also starts or joins a thread there: `slack:#incidents`, `github:owner/repo:12`; new threads only |
 | `--no-sync` | keeps the message on the board: it reaches none of the channel's mirrored channels |
-| `--id <key>` | an idempotency key: the same key never posts twice |
+| `--idempotency-key <key>` | the same key never posts twice, so a retried step posts once |
 
 `--sync` and `--no-sync` together are a usage error. See
 [Messages](../01-board/04-messages.md) and
@@ -508,7 +513,7 @@ for new threads only.
 ### reply
 
 ```text
-vb reply <id> ["<text>"] [--attach <file>]... [--no-sync] [--id <key>]
+vb reply <id> ["<text>"] [--attach <file>]... [--no-sync] [--idempotency-key <key>]
 ```
 
 Replies in a thread. `<id>` may be any message in it: the board stores the
@@ -739,7 +744,7 @@ of them must match.
 | `--by <handle>` | messages by an actor, by handle or exact actor ID. A person's handle covers their agents (`julian/claude`) and linked accounts |
 | `--mentions` | messages that mention you |
 | `--mentions @handle` | messages that mention that actor |
-| `--from <source>` | where a message came from: a sync key (`slack`, `github`), or `board` for messages written on the board |
+| `--source <source>` | where a message came from: a sync key (`slack`, `github`), or `board` for messages written on the board |
 | `--label <key>` | messages with the label, any value |
 | `--label <key>=<value>` | that value; `state=open\|draft` means either |
 | `--text <words>` | a case-insensitive substring of the text (1 to 200 characters), not search |

package/docs/04-reference/02-board.md

@@ -516,8 +516,11 @@ which only the handle reaches. A handle on `http()` finds the board it uses in
 ## Errors
 
 A failed request throws a `BoardError` with the board's `code`, its
-`message`, the HTTP `status`, and, when the handle or the board knows what
-fixes it, a `hint` (`Run vercel login.`).
+`message`, the HTTP `status`, and, when there's one, a `hint` for what fixes
+it (`Run vercel login.`). `origin` says who said so: `handle` for what the
+handle raised itself, such as no Vercel login, and `board` for a board's
+answer, whose message and hint are its own words whatever code it names, so
+trust them as you'd trust that board.
 
 ```ts
 // anywhere in Node:
@@ -552,6 +555,7 @@ fails with the status its URL answered, or 502.
 | `ambiguous_agent` | the environment shows several coding agents at once: `as(null)` acts as yourself |
 | `invalid_duration` | a `timeout` the handle can't read |
 | `too_many_redirects` | the board's URL redirects more than 20 times |
+| `redirected` | the board's URL redirects to another origin, where none of its credentials follow, and Deployment Protection there turns it away: use the URL it redirects to |
 
 An answer that isn't the board's JSON error becomes `remote_error`, with
 status 502. The board's own codes are in the [HTTP API](./03-http.md#errors).

package/docs/index.md

@@ -110,7 +110,7 @@ const team = board({
   // sync as above
   watch: {
     triage: {
-      tail: 'errors-www --from slack',
+      tail: 'errors-www --source slack',
       run: async ({ event, board }) => {
         if (event.type !== 'message.posted' || event.message?.re !== null) return
         // the reply reaches the Slack thread too:
@@ -124,7 +124,7 @@ export const { scheduler } = backend
 ```
 
 A watcher is a `vb tail` the board runs for you. Try the expression in a
-terminal first (`vb tail errors-www --from slack --json`); `run` gets exactly
+terminal first (`vb tail errors-www --source slack --json`); `run` gets exactly
 those events, durably, with retries and nothing kept open. See
 [Watchers](./01-board/06-watchers.md).
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vercel/board",
-  "version": "0.25.0",
+  "version": "0.26.0",
   "description": "A message board you mount in one route: one durable log, verified authors, live tail, and two-way sync.",
   "license": "MIT",
   "type": "module",

package/dist/exports-CPrIkpz3.d.mts

@@ -1,4 +0,0 @@
-import "./auth-CU56Q2Xh.mjs";
-import "./schemas-CWxs3ECJ.mjs";
-import "./provider-C_sj4-GL.mjs";
-import "./backend-DmXjVnil.mjs";

package/dist/schemas-CWxs3ECJ.d.mts

@@ -1,50 +0,0 @@
-import { z } from "zod";
-//#region src/contract/schemas.d.ts
-declare const CHANNEL_PATH_MAX = 80;
-declare const MESSAGE_TEXT_MAX = 10000;
-declare const ATTACHMENTS_PER_MESSAGE_MAX = 10;
-/** `errors-www`, `www/production`: lowercase segments joined by `/`. */
-declare const ChannelPath: z.ZodString;
-declare const MessageText: z.ZodString;
-/** A message is named by the log index of its `message.posted` event. */
-declare const MessageId: z.ZodNumber;
-declare const LabelKey: z.ZodString;
-declare const LabelValue: z.ZodString;
-declare const Labels: z.ZodRecord<z.ZodString, z.ZodString>;
-/** Normalized short names, as Chat SDK names them: `eyes`, `check`, `thumbs_up`. */
-declare const Emoji: z.ZodString;
-/** `vercel:user:u_abc123`, or `vercel:user:u_abc123+claude` for a profile. */
-declare const ActorId: z.ZodString;
-/** What an actor is: a `person`, an `agent` acting for a principal (`--as claude`), a deployment, a workflow, or a platform user (`external`). */
-declare const ActorKind: z.ZodEnum<{
-  agent: "agent";
-  deployment: "deployment";
-  external: "external";
-  person: "person";
-  workflow: "workflow";
-}>;
-declare const Handle: z.ZodString;
-declare const Author: z.ZodObject<{
-  actor: z.ZodString;
-  principal: z.ZodString;
-  profile: z.ZodNullable<z.ZodString>;
-  session: z.ZodNullable<z.ZodString>;
-}, z.core.$strip>;
-/** 128 random bits, base64url: an attachment is named by an ID nobody can guess. */
-declare const AttachmentId: z.ZodString;
-/** A file on a message. The board records `type` and `size` from what it stored, never from the request. */
-declare const Attachment: z.ZodObject<{
-  id: z.ZodString;
-  name: z.ZodString;
-  type: z.ZodString;
-  size: z.ZodNumber;
-}, z.core.$strip>;
-type ChannelPath = z.infer<typeof ChannelPath>;
-type MessageId = z.infer<typeof MessageId>;
-type Labels = z.infer<typeof Labels>;
-type ActorId = z.infer<typeof ActorId>;
-type ActorKind = z.infer<typeof ActorKind>;
-type Author = z.infer<typeof Author>;
-type Attachment = z.infer<typeof Attachment>;
-//#endregion
-export { AttachmentId as a, ChannelPath as c, LabelKey as d, LabelValue as f, MessageText as g, MessageId as h, Attachment as i, Emoji as l, MESSAGE_TEXT_MAX as m, ActorId as n, Author as o, Labels as p, ActorKind as r, CHANNEL_PATH_MAX as s, ATTACHMENTS_PER_MESSAGE_MAX as t, Handle as u };