@lunora/queue 1.0.0-alpha.9 → 1.0.0-alpha.91

package/README.md

@@ -26,18 +26,36 @@ import { api } from "./_generated/api";
 export const emailQueue = defineQueue<{ to: string }>({
     handler: async (ctx, batch) => {
         for (const message of batch.messages) {
-            await ctx.run(api.email.send, { to: message.body.to });
+            await message.run(api.email.send, { to: message.body.to });
             message.ack();
         }
     },
 });
 ```
 
+`message.run(...)` is `ctx.run(...)` pinned to that message. Call it inside the
+batch loop: when the dispatched function fails deterministically (`400`, `403`,
+`404`, `422`), the consumer acks just that message and retries the rest instead
+of letting one poison message retry — and eventually dead-letter — the whole
+batch.
+
 ```ts
 // inside a mutation/action
 await ctx.queues.emailQueue.send({ to: user.email });
 ```
 
+For one event with several consumers, declare a topic and subscribe to it.
+Each subscription is its own queue, with its own retries and dead-letter queue:
+
+```ts
+// lunora/queues.ts
+export const signups = defineTopic<{ userId: string }>();
+export const welcomeEmail = defineSubscription(signups, { handler: async (ctx, batch) => {} });
+
+// inside a mutation/action
+await ctx.topics.signups.publish({ userId });
+```
+
 Codegen emits the typed `ctx.queues` producer and the worker `queue()` dispatch;
 `@lunora/config` reconciles the wrangler `queues.producers[]` /
 `queues.consumers[]` entries from the same definition. Scaffold a new queue with

package/dist/index.d.mts

@@ -1,3 +1,5 @@
+import { QueueBindingLike, MessageBatchLike, MessageLike, QueueSendOptions, MessageSendRequestLike, QueueSendBatchOptions } from '@lunora/platform';
+export type { MessageBatchLike, MessageLike, MessageSendRequestLike, QueueBindingLike, QueueContentType, QueueRetryOptions, QueueSendBatchOptions, QueueSendOptions } from '@lunora/platform';
 /**
  * Shared types for dispatching a Lunora function back into the worker from a
  * server-initiated context (a workflow body, a queue handler, a scheduled job).
@@ -12,8 +14,45 @@ interface FunctionReference {
 type ArgsOf<F> = F extends FunctionReference ? Record<string, unknown> : never;
 /** Options for a function call made via a dispatch runner. */
 interface RunFunctionOptions {
+  /**
+   * The at-least-once dedup key for THIS ONE CALL, sent to the dispatch
+   * endpoint as the body's `id` and forwarded to the shard as the
+   * replay-dedup `mutationId` — so a redelivery that re-runs the same call
+   * applies it exactly once instead of twice.
+   *
+   * Must be unique per call and stable across redeliveries. It is NOT
+   * {@link RunFunctionOptions.messageId}: the shard's dedup table is keyed
+   * `(identity, mutationId)` with no function path in it, and every
+   * server-initiated dispatch shares the `"system:"` identity, so reusing
+   * one id across two calls makes the second return the FIRST call's cached
+   * result without ever executing. A per-message id is 1:N with the calls a
+   * handler makes; this is 1:1.
+   *
+   * `@lunora/queue`'s `message.run` derives one automatically as
+   * `<messageId>#<n>`, `n` counting that message's calls in order. That is
+   * stable across redeliveries because the handler replays from the start —
+   * it relies on the handler issuing its `run` calls in a DETERMINISTIC
+   * order, which at-least-once replay already assumes. A handler whose call
+   * order varies per attempt (branching on `Date.now()`, `Math.random()`,
+   * or unordered concurrent settles) must pass its own stable ids instead.
+   *
+   * Optional; when omitted the dispatch is at-least-once.
+   */
+  dedupId?: string;
+  /**
+   * Correlate this call with a caller-defined message/item id (e.g. a queue
+   * message's `id`), for failure attribution only — never sent to the
+   * dispatch endpoint. Carried onto the `LunoraError` a deterministic
+   * dispatch failure throws, so a batching consumer (`@lunora/queue`'s push
+   * handler) can read it back and attribute the failure to the one item that
+   * caused it instead of the whole batch. Deliberately NOT the dedup key —
+   * see {@link RunFunctionOptions.dedupId}. Optional and inert when omitted.
+   */
+  messageId?: string;
   /** Route the call to a specific shard (defaults to the worker's root shard). */
   shardKey?: string;
+  /** Abort the dispatch after this many ms; the abort is retryable. Overrides the runner's default. */
+  timeoutMs?: number;
 }
 /** Invoke a Lunora function (query/mutation/action) by reference. The shape of `ctx.run`. */
 type DispatchRunFunction = <F extends FunctionReference>(function_: F, args?: ArgsOf<F>, options?: RunFunctionOptions) => Promise<unknown>;
@@ -24,62 +63,8 @@ interface DispatchLogger {
   info: (message: unknown, ...rest: unknown[]) => void;
   warn: (message: unknown, ...rest: unknown[]) => void;
 }
-/** How a queue message body is serialized on the wire (Cloudflare default `"json"`). */
-type QueueContentType = "bytes" | "json" | "text" | "v8";
-/** Options for a single `producer.send(body, options?)`. */
-interface QueueSendOptions {
-  /** Wire serialization for this message (defaults to the queue's content type). */
-  contentType?: QueueContentType;
-  /** Per-message delivery delay in seconds (0–43200, i.e. up to 12 hours). */
-  delaySeconds?: number;
-}
-/** Options for a `producer.sendBatch(messages, options?)`. */
-interface QueueSendBatchOptions {
-  /** Delivery delay applied to the whole batch, in seconds. */
-  delaySeconds?: number;
-}
-/** One entry in a `sendBatch` call — a body plus optional per-message overrides. */
-interface MessageSendRequestLike<Body = unknown> {
-  body: Body;
-  contentType?: QueueContentType;
-  delaySeconds?: number;
-}
-/**
- * Minimal structural projection of workers-types' `Queue&lt;Body>` (the producer
- * binding). The real binding's `send`/`sendBatch` resolve to a metadata object;
- * we widen the return to `Promise&lt;unknown>` so a plain-object fake satisfies it.
- */
-interface QueueBindingLike<Body = unknown> {
-  send: (message: Body, options?: QueueSendOptions) => Promise<unknown>;
-  sendBatch: (messages: Iterable<MessageSendRequestLike<Body>>, options?: QueueSendBatchOptions) => Promise<unknown>;
-}
-/** Options for retrying a message / batch (`message.retry({ delaySeconds })`). */
-interface QueueRetryOptions {
-  delaySeconds?: number;
-}
-/** Structural mirror of workers-types' `Message&lt;Body>` (one delivered message). */
-interface MessageLike<Body = unknown> {
-  /** Acknowledge this message so it is not redelivered. */
-  ack: () => void;
-  readonly attempts: number;
-  readonly body: Body;
-  readonly id: string;
-  /** Explicitly retry this message (optionally after a delay). */
-  retry: (options?: QueueRetryOptions) => void;
-  readonly timestamp: Date;
-}
-/** Structural mirror of workers-types' `MessageBatch&lt;Body>` handed to a consumer. */
-interface MessageBatchLike<Body = unknown> {
-  /** Acknowledge every message in the batch. */
-  ackAll: () => void;
-  readonly messages: ReadonlyArray<MessageLike<Body>>;
-  /** The queue name this batch was delivered from (`batch.queue`), used to route. */
-  readonly queue: string;
-  /** Retry every message in the batch (optionally after a delay). */
-  retryAll: (options?: QueueRetryOptions) => void;
-}
 /**
- * The typed producer bound to `ctx.queues.&lt;name>`. Sending is a side effect, so
+ * The typed producer bound to `ctx.queues.<name>`. Sending is a side effect, so
  * the generated context exposes this only on `MutationCtx` / `ActionCtx` (never
  * the deterministic `QueryCtx`), mirroring `ctx.scheduler` / `ctx.workflows`.
  */
@@ -113,13 +98,39 @@ interface QueueRunContext {
   readonly env: Record<string, unknown>;
   /** Queue-name-prefixed logger. */
   readonly log: DispatchLogger;
-  /** Invoke a Lunora function (query/mutation/action) by reference. */
+  /**
+   * Invoke a Lunora function (query/mutation/action) by reference.
+   *
+   * Batch-unaware: a failure it throws is attributed to nothing, so a
+   * deterministic failure retries the whole batch. Inside the `batch.messages`
+   * loop, prefer {@link QueueMessage.run}, which pins the call to its message.
+   */
+  readonly run: DispatchRunFunction;
+}
+/**
+ * One delivered message as the push handler sees it: the Cloudflare `Message`
+ * plus `run` — a {@link QueueRunContext.run} pinned to THIS message.
+ *
+ * Prefer `message.run(api.x.y, args)` over `ctx.run(...)` inside the batch
+ * loop. The pin is what lets the dispatcher attribute a deterministic dispatch
+ * failure (400/403/404/422) to the one message that caused it: that message is
+ * acked and every other one is retried, instead of the whole batch being
+ * re-delivered because of a single poison message. A plain `ctx.run` call
+ * carries no message id, so its failure stays unattributed and the whole batch
+ * retries.
+ */
+interface QueueMessage<Body = unknown> extends MessageLike<Body> {
+  /** {@link QueueRunContext.run}, pinned to this message for failure attribution. */
   readonly run: DispatchRunFunction;
 }
+/** The delivered batch as the push handler sees it — {@link QueueMessage}s rather than bare `Message`s. */
+interface QueueMessageBatch<Body = unknown> extends Omit<MessageBatchLike<Body>, "messages"> {
+  readonly messages: ReadonlyArray<QueueMessage<Body>>;
+}
 /** Whether a declared queue is consumed by this worker (push) or polled externally (pull). */
 type QueueConsumerMode = "pull" | "push";
 /** The handler body run for each delivered batch (push consumers only). */
-type QueueHandler<Body = unknown> = (context: QueueRunContext, batch: MessageBatchLike<Body>) => Promise<void> | void;
+type QueueHandler<Body = unknown> = (context: QueueRunContext, batch: QueueMessageBatch<Body>) => Promise<void> | void;
 /** Push-consumer batch/retry tuning, mirrored onto the wrangler `queues.consumers[]` entry. */
 interface QueueConsumerTuning {
   /** Name of the dead-letter queue messages land in after `maxRetries`. */
@@ -128,7 +139,7 @@ interface QueueConsumerTuning {
   maxBatchSize?: number;
   /** Max seconds to wait before delivering a partial batch (0–60, default 5). */
   maxBatchTimeout?: number;
-  /** Max delivery attempts before a message is dropped / dead-lettered (default 3). */
+  /** Retries **after** the initial delivery, before a message is dropped / dead-lettered. Default 3, so up to 4 deliveries in total. */
   maxRetries?: number;
   /** Delay in seconds before a failed batch is retried. */
   retryDelay?: number;
@@ -152,13 +163,71 @@ interface QueueConfig<Body = unknown> extends QueueConsumerTuning {
 interface QueueDefinition<Body = unknown> extends QueueConfig<Body> {
   /**
    * Phantom carrier for the message body type, so codegen can type the
-   * generated `ctx.queues.&lt;name>` producer as `QueueProducer&lt;Body>` from
-   * `typeof &lt;export>`. Never assigned at runtime (type-only).
+   * generated `ctx.queues.<name>` producer as `QueueProducer<Body>` from
+   * `typeof <export>`. Never assigned at runtime (type-only).
    */
   readonly __lunoraBody?: Body;
   /** Runtime brand identifying a `defineQueue` result. */
   isLunoraQueue: true;
 }
+/**
+ * The typed publisher bound to `ctx.topics.<name>`. A publish is one send to
+ * **each** subscription's queue, in parallel, so it is not atomic: when one send
+ * fails the call rejects, and a retry re-delivers to the subscriptions whose send
+ * already succeeded. Delivery is at-least-once per subscription — make handlers
+ * idempotent. A topic with no subscriptions publishes to nobody.
+ */
+interface TopicPublisher<Payload = unknown> {
+  /** Publish one message to every subscription. */
+  publish: (payload: Payload, options?: QueueSendOptions) => Promise<void>;
+  /** Publish a batch (at most 100) to every subscription in one send per subscription. */
+  publishBatch: (messages: Iterable<MessageSendRequestLike<Payload>>, options?: QueueSendBatchOptions) => Promise<void>;
+}
+/** `ctx.topics` — declared topic export names → typed publishers. Codegen narrows it to the exact names. */
+interface Topics {
+  [exportName: string]: TopicPublisher;
+}
+/** The branded result of `defineTopic`, discovered by codegen. Carries no deploy config of its own. */
+interface TopicDefinition<Payload = unknown> {
+  /**
+   * Phantom carrier for the payload type, so codegen can type `ctx.topics.<name>`.
+   * Named like {@link QueueDefinition}'s so one emitted helper reads both. Never
+   * assigned at runtime.
+   */
+  readonly __lunoraBody?: Payload;
+  /** Runtime brand identifying a `defineTopic` result. */
+  isLunoraTopic: true;
+}
+/** The config passed to `defineSubscription`: a push consumer's handler plus its own retry/DLQ tuning. */
+interface SubscriptionConfig<Payload = unknown> extends QueueConsumerTuning {
+  handler: QueueHandler<Payload>;
+  /**
+   * Stable wrangler queue name for this subscription. Defaults to the
+   * kebab-cased export name, exactly like a `defineQueue` export.
+   */
+  name?: string;
+}
+/**
+ * The branded result of `defineSubscription`: a push {@link QueueDefinition}
+ * (so dispatch, retries, the DLQ, wrangler reconcile and the studio treat it as
+ * the queue it is) tagged with the topic it consumes.
+ */
+interface SubscriptionDefinition<Payload = unknown> extends QueueDefinition<Payload> {
+  handler: QueueHandler<Payload>;
+  mode: "push";
+  /** The topic this subscription consumes. */
+  topic: TopicDefinition<Payload>;
+}
+/** Wiring info for one declared topic, emitted by codegen into the generated shard. */
+interface TopicBindingSpec {
+  /** The `lunora/queues.ts` topic export name, e.g. `signups`. */
+  exportName: string;
+  /** One entry per subscription: its export name and its `Queue` producer binding. */
+  subscriptions: ReadonlyArray<{
+    binding: string;
+    exportName: string;
+  }>;
+}
 /** Wiring info for one declared queue, emitted by codegen into the generated shard/handler. */
 interface QueueBindingSpec {
   /** The Cloudflare `Queue` producer binding name, e.g. `QUEUE_EMAIL`. */
@@ -170,11 +239,18 @@ interface QueueBindingSpec {
 }
 /** One declared queue, keyed for batch routing by its stable wrangler name. */
 interface QueueRegistryEntry {
+  /**
+   * The queue's own producer binding on `env` (`QUEUE_*`). A message whose
+   * dispatch is declined on its last delivery is re-enqueued through it (see
+   * {@link resolveDeclinedBatch}); without it that message is dead-lettered or
+   * dropped, and logged. Codegen always emits it.
+   */
+  binding?: string;
   /**
    * The `defineQueue` result (carries the push handler). The body type is
    * erased to `any` here because the registry is heterogeneous — different
    * queues carry different message bodies, and the handler param is
-   * contravariant, so a precise `QueueDefinition&lt;Body>` would not be assignable
+   * contravariant, so a precise `QueueDefinition<Body>` would not be assignable
    * to a shared `unknown`-bodied slot. Runtime dispatch passes the delivered
    * batch straight through, so the erasure is type-only.
    */
@@ -197,7 +273,28 @@ interface CapturedQueueMessage {
   attempts: number;
   /** The message body (JSON-encoded + capped by the catcher). */
   body: unknown;
-  /** `true` when this failed delivery was the message's last (its retries are exhausted — the broker dead-letters it). */
+  /**
+   * `true` when this failed delivery was the message's last (its retries are
+   * exhausted) AND the queue declares a `deadLetterQueue` for it to land in.
+   * Stays `false` for a queue with no DLQ, where the broker drops the
+   * exhausted message instead — `attempts > maxRetries` with
+   * `outcome !== "ack"` is what identifies that case.
+   *
+   * Read from the `defineQueue` DECLARATION, because a consumer has no
+   * runtime API that exposes its deployed `queues.consumers[]` settings. It is
+   * true of the deployed broker only as far as Lunora's binding reconcile (run
+   * by `lunora dev`, `deploy` and `prepare`) keeps the two in step: it writes
+   * every declared tuning field onto the consumer, including onto one that
+   * already exists, and takes a field back out once `defineQueue` drops it
+   * (it records what `defineQueue` declared in `package.json`
+   * `lunora.queueTuning`). The gaps that remain: a field changed by hand to
+   * another value than the declared one is
+   * kept when the declaration drops it, so a hand-set DLQ still reads
+   * `false` here; a `--env` deploy retunes the `env.<name>` consumers but
+   * never writes their `dead_letter_queue`, which that block names itself;
+   * and a bare `wrangler deploy` over a hand-edited consumer can disagree
+   * too. Nothing on this side can see any of it.
+   */
   deadLettered: boolean;
   /** Handler error message when `outcome` is `error`; absent otherwise. */
   error?: string;
@@ -221,16 +318,25 @@ interface CapturedQueueMessage {
 type QueueCaptureSink = (messages: CapturedQueueMessage[]) => Promise<void> | void;
 interface DispatchOptions {
   /**
-   * Optional capture sink. When set, the batch is instrumented and every
-   * message's final disposition is recorded and handed to this sink after the
-   * handler runs. Omitted in production unless queue capture is enabled, so a
-   * consumer pays no instrumentation cost by default.
+   * Optional capture sink. When set, every message's final disposition is
+   * turned into a record and handed to this sink after the handler runs.
+   * Omitted in production unless queue capture is enabled, so a consumer pays
+   * no record-building or sink cost by default. Delivery semantics — including
+   * poison-message isolation — do not depend on it.
    */
   capture?: QueueCaptureSink;
   /** Worker `env`, forwarded to the queue run context. */
   env: Record<string, unknown>;
   /** Injectable fetch for the `ctx.run` dispatcher (tests). */
   fetchImpl?: typeof fetch;
+  /**
+   * W3C `traceparent` of the consumer invocation's own trace, supplied by the
+   * runtime's `queue()` entry. Forwarded on every `ctx.run` dispatch so the
+   * functions a handler calls are CHILDREN of the queue span instead of a set of
+   * unrelated root traces. Absent (a hand-built dispatch, a unit test) keeps the
+   * prior behaviour: the callee mints its own trace.
+   */
+  traceparent?: string;
 }
 /**
  * Look up the handler for `batch.queue` and invoke it with a fresh
@@ -268,7 +374,7 @@ declare const createQueueCaptureSink: (env: QueueEnv, options?: QueueCaptureOpti
  * Build the `ctx.queues` map for a request: resolve every spec's `env[binding]`
  * into the `exportName → Queue binding` map and wrap it in {@link createQueues}.
  * A spec whose binding is absent from `env` is skipped here — the helpful "no
- * queue named …" error is raised lazily by `ctx.queues.&lt;name>.send(...)` when
+ * queue named …" error is raised lazily by `ctx.queues.<name>.send(...)` when
  * the missing queue is actually used.
  */
 declare const createQueueContext: (env: Record<string, unknown>, specs: ReadonlyArray<QueueBindingSpec>) => Queues;
@@ -282,7 +388,7 @@ declare const createQueues: (options: LunoraQueuesOptions) => Queues;
 /**
  * The wrangler producer binding name for a queue export: `emailQueue` →
  * `QUEUE_EMAIL_QUEUE`, `email` → `QUEUE_EMAIL`. The `QUEUE_` prefix namespaces
- * these away from `SHARD`/`SESSION`/`SCHEDULER`/`WORKFLOW_*`/`CONTAINER_*` so a
+ * these away from `SHARD`/`SESSION`/`SCHEDULER`/`CONTAINER_*` so a
  * queue export can never collide with the built-in bindings.
  */
 declare const queueBindingName: (exportName: string) => string;
@@ -294,7 +400,7 @@ declare const queueBindingName: (exportName: string) => string;
 declare const queueDefaultName: (exportName: string) => string;
 /**
  * Declare a Cloudflare Queue deployed alongside the app. Pure validation +
- * branding: codegen discovers the export, emits the typed `ctx.queues.&lt;name>`
+ * branding: codegen discovers the export, emits the typed `ctx.queues.<name>`
  * producer and (for push consumers) the worker `queue()` dispatch; the config
  * layer reconciles the wrangler `queues.producers[]` / `queues.consumers[]`
  * entries from the same definition.
@@ -304,10 +410,10 @@ declare const queueDefaultName: (exportName: string) => string;
  * import { defineQueue } from "@lunora/queue";
  * import { api } from "./_generated/api";
  *
- * export const emailQueue = defineQueue&lt;{ to: string }>({
+ * export const emailQueue = defineQueue<{ to: string }>({
  *     handler: async (ctx, batch) => {
  *         for (const message of batch.messages) {
- *             await ctx.run(api.email.send, { to: message.body.to });
+ *             await message.run(api.email.send, { to: message.body.to });
  *             message.ack();
  *         }
  *     },
@@ -316,6 +422,12 @@ declare const queueDefaultName: (exportName: string) => string;
  *
  * Enqueue from a mutation or action: `await ctx.queues.emailQueue.send({ to })`.
  *
+ * `message.run(...)` is `ctx.run(...)` pinned to that message — prefer it inside
+ * the batch loop. A deterministic failure (400/403/404/422) from a pinned call
+ * is attributed to its message: that one is acked and the rest are retried,
+ * instead of one poison message re-delivering (and eventually dead-lettering)
+ * the whole batch.
+ *
  * ⚠️ **Privileged dispatch.** A push handler's `ctx.run(...)` calls back into
  * Lunora functions over the admin-authenticated dispatch endpoint (the same
  * trusted path the scheduler and workflows use), so those calls run with the
@@ -331,7 +443,29 @@ interface RunContextOptions {
   env: Record<string, unknown>;
   exportName: string;
   fetchImpl?: typeof fetch;
+  /** The consumer invocation's `traceparent`, so `ctx.run` joins the queue's trace. */
+  traceparent?: string;
 }
 /** Assemble the {@link QueueRunContext} passed to a `defineQueue` handler. */
 declare const createQueueRunContext: (options: RunContextOptions) => QueueRunContext;
-export { type ArgsOf, type CapturedQueueMessage, type FunctionReference, type LunoraQueuesOptions, type MessageBatchLike, type MessageLike, type MessageSendRequestLike, type QueueBindingLike, type QueueBindingSpec, type QueueCaptureOptions, type QueueCaptureSink, type QueueConfig, type QueueConsumerMode, type QueueConsumerTuning, type QueueContentType, type QueueDefinition, type QueueEnv, type QueueHandler, type DispatchLogger as QueueLogger, type QueueProducer, type QueueRegistry, type QueueRegistryEntry, type QueueRetryOptions, type QueueRunContext, type DispatchRunFunction as QueueRunFunction, type QueueSendBatchOptions, type QueueSendOptions, type Queues, type RunFunctionOptions, createQueueCaptureSink, createQueueContext, createQueueRunContext, createQueues, defineQueue, dispatchQueueBatch, isQueueDefinition, queueBindingName, queueDefaultName, shouldCaptureQueue };
+/**
+ * Declare a topic in `lunora/queues.ts`. The payload type is the only thing a
+ * topic carries; delivery config lives on each subscription.
+ */
+declare const defineTopic: <Payload = unknown>() => TopicDefinition<Payload>;
+/**
+ * Subscribe to a topic. The result is a push queue definition — export it from
+ * `lunora/queues.ts` and it deploys, retries and dead-letters exactly like a
+ * `defineQueue` export of the same name.
+ *
+ * ⚠️ Same trust model as a queue handler: `message.run(...)` dispatches with the
+ * system identity, so validate `message.body` before acting on it.
+ */
+declare const defineSubscription: <Payload>(topic: TopicDefinition<Payload>, config: SubscriptionConfig<Payload>) => SubscriptionDefinition<Payload>;
+/**
+ * Build `ctx.topics` for a request from the Worker `env` and the codegen-emitted
+ * specs. A topic with no subscriptions publishes to nobody; a topic with an
+ * unbound subscription rejects every publish (see {@link unboundPublisher}).
+ */
+declare const createTopicContext: (env: Record<string, unknown>, specs: ReadonlyArray<TopicBindingSpec>) => Topics;
+export { type ArgsOf, type CapturedQueueMessage, type FunctionReference, type LunoraQueuesOptions, type QueueBindingSpec, type QueueCaptureOptions, type QueueCaptureSink, type QueueConfig, type QueueConsumerMode, type QueueConsumerTuning, type QueueDefinition, type QueueEnv, type QueueHandler, type DispatchLogger as QueueLogger, type QueueMessage, type QueueMessageBatch, type QueueProducer, type QueueRegistry, type QueueRegistryEntry, type QueueRunContext, type DispatchRunFunction as QueueRunFunction, type Queues, type RunFunctionOptions, type SubscriptionConfig, type SubscriptionDefinition, type TopicBindingSpec, type TopicDefinition, type TopicPublisher, type Topics, createQueueCaptureSink, createQueueContext, createQueueRunContext, createQueues, createTopicContext, defineQueue, defineSubscription, defineTopic, dispatchQueueBatch, isQueueDefinition, queueBindingName, queueDefaultName, shouldCaptureQueue };