@lunora/notify 1.0.0-alpha.2 → 1.0.0-alpha.20

package/README.md

@@ -98,6 +98,35 @@ for (const message of batch.messages) await runPushBroadcastJob(ctx.push, messag
 
 `SubscriptionStore` implementations: `memorySubscriptionStore()` (non-durable default, tests/dev) and `d1SubscriptionStore(db)` (durable, edge-safe, lazy table creation). Lifecycle: register (upsert), list/filter (by kind or user), status marking, and automatic prune of gone subscriptions on send/broadcast.
 
+## Security
+
+`ctx.push.register(...)` and the browser `subscribeToPush` helper both accept
+client-supplied data, so the facade enforces two boundaries:
+
+- **Endpoint validation (anti-SSRF).** Every later `send`/`broadcast` POSTs to a
+  subscription's stored Web Push `endpoint`, so a hostile `endpoint` would turn the
+  worker into an SSRF / amplification primitive. `register()` validates the endpoint
+  **at storage time** (the durable boundary): it must be an absolute `https:` URL
+  with a non-private / non-loopback / non-link-local / non-CGNAT host. To hard-pin
+  the boundary to the push services you actually use, set `allowedPushOrigins` on
+  `defineNotify` — when present, an endpoint's origin must match one of the listed
+  origins **exactly** (no wildcards), which also closes DNS rebinding:
+
+    ```ts
+    export default defineNotify({
+        webPush: (env) => webPushFromEnv(env),
+        allowedPushOrigins: ["https://fcm.googleapis.com", "https://updates.push.services.mozilla.com"],
+        store: (env) => d1SubscriptionStore(env.DB),
+    });
+    ```
+
+- **No secrets on the app facade.** `ctx.push.list()`
+  returns the registered devices with the delivery **secrets stripped** — the Web
+  Push `keys` (`auth`/`p256dh`) and the FCM `token`, which together with the
+  endpoint are enough to deliver arbitrary push to a device. The raw rows are
+  reachable only through the internal `SubscriptionStore` (which handlers never
+  hold); the broadcast path uses the store directly.
+
 ## Delivery observability
 
 Every send is counted onto `ctx.metrics` and failures onto `ctx.log` for you — codegen threads the request's logger/metrics into `ctx.notify` (`createNotify(notifyConfig, env, { log, metrics })`), so there is nothing to wire. Two low-cardinality metric series feed the durable metric history + trend charts:

package/dist/index.d.mts

@@ -75,8 +75,58 @@ type RegisterInput = {
 };
 /** Filter narrowing which stored subscriptions a `list`/`broadcast` targets. */
 interface SubscriptionFilter {
+  /**
+   * Keyset pagination cursor: return only rows with `id` strictly GREATER
+   * than this value, ordered ascending by `id`. `id` is a stable,
+   * content-derived hash (see `webPushId`/`fcmId`), so ordering by it is
+   * immune to concurrent inserts/deletes elsewhere in the table — a page
+   * already walked never re-delivers or skips a row when another device
+   * registers mid-broadcast (the reviewer-flagged "stable under concurrent
+   * registers" property). `broadcastPage`/`broadcast` set this internally to
+   * walk pages; a direct `list()` caller may also page through results with
+   * it.
+   *
+   * OPTIONAL for a reason: `SubscriptionStore` is implementable outside this
+   * package. An external store that does not support cursoring may ignore
+   * `after` entirely and keep returning its (from-the-top) unpaged result —
+   * `broadcastPage` defensively re-filters whatever the store returns down
+   * to `id > after` itself, so a non-cursoring store can never cause a
+   * double-send or an infinite page-walk (each page's result only ever
+   * contains ids the previous page didn't already deliver), but it also
+   * cannot deliver the FULL matched audience beyond whatever the store's own
+   * (unpaged) response window happens to contain — implement `after`
+   * (ordered ascending by `id`, exclusive) to get real, complete pagination
+   * over a large audience.
+   */
+  after?: string;
   /** Restrict to a delivery kind. */
   kind?: SubscriptionKind;
+  /**
+   * Cap the number of rows returned (a `LIMIT`). Applied server-side by the
+   * store, so a large audience never materializes wholesale in the isolate.
+   * A non-positive/absent value means "no cap"; a fractional value is truncated.
+   *
+   * For `list`/admin reads this bounds the returned page as before. For
+   * `broadcast`, this is now an OVERALL cap on the total number of
+   * subscriptions reached across every internally-walked page (still
+   * deliberately left unset by default — it must reach every matched
+   * device); the PER-PAGE batch size is a separate, independent knob (see
+   * `CreateNotifyOptions`'s `broadcastPageSize`, default 250) so a caller
+   * that sets `limit` to bound the audience doesn't also have to reason
+   * about page sizing.
+   *
+   * The non-positive sentinel means something different at each layer: at
+   * the STORE layer (`list`, and the `d1-store`/`memory-store` fetch-size
+   * hint) a non-positive `limit` means "no cap" — fetch everything. At the
+   * `broadcast`/`broadcastPage` layer, where `limit` is an AUDIENCE cap, a
+   * non-positive value instead means "no deliveries" — `broadcast({ limit: 0
+   * })` reaches nobody, not everybody. This asymmetry is deliberate: the two
+   * layers answer different questions ("how many rows to fetch" vs. "how
+   * many recipients to reach"), and unifying them would either break `list`
+   * callers relying on "no cap" or reintroduce the over-delivery this
+   * distinction fixes (see `broadcastPage`'s doc comment).
+   */
+  limit?: number;
   /** Restrict to a single owning user. */
   userId?: string | null;
 }
@@ -90,7 +140,13 @@ interface SubscriptionStore {
   delete: (id: string) => Promise<void>;
   /** Read a subscription by id, or `undefined`. */
   get: (id: string) => Promise<StoredSubscription | undefined>;
-  /** List subscriptions, optionally filtered. */
+  /**
+   * List subscriptions, optionally filtered. When `filter.after` is set,
+   * results are keyset-paginated: only rows with `id` strictly greater than
+   * `filter.after` are returned, ordered ascending by `id`. Implementing
+   * `after` is OPTIONAL (see {@link SubscriptionFilter.after}) — a store
+   * that ignores it may keep returning its unpaged result.
+   */
   list: (filter?: SubscriptionFilter) => Promise<StoredSubscription[]>;
   /** Record the latest delivery outcome for a subscription (best-effort). */
   markStatus: (id: string, status: SubscriptionStatus, error?: string) => Promise<void>;
@@ -119,6 +175,18 @@ interface BroadcastResult {
   /** Total subscriptions attempted. */
   total: number;
 }
+/**
+ * Result of `broadcastPage` — one bounded page of a fan-out, plus the cursor
+ * to fetch the next page. `nextCursor` is `undefined` when this was the last
+ * page (or the store doesn't support cursoring — see
+ * {@link SubscriptionFilter.after}'s documented unpaged fallback).
+ */
+interface BroadcastPageResult {
+  /** Cursor for the next page (pass as `filter.after`), or `undefined` when done. */
+  nextCursor?: string;
+  /** The delivery outcome for just this page. */
+  result: BroadcastResult;
+}
 /**
  * The compact, stable delivery-status vocabulary emitted on notify observability
  * signals — the `status` dimension on the `notify.send` metric and the failure
@@ -173,10 +241,36 @@ interface LunoraPush {
    * Reuses the engine's retry/circuit-breaker middleware; prunes subscriptions
    * the push service reports as gone (HTTP 404/410, FCM `UNREGISTERED`). The `to`
    * target is derived from each subscription, so it is omitted from the payload.
+   *
+   * Internally walks the audience in bounded pages (via {@link LunoraPush.broadcastPage},
+   * keyset-paginated on the subscription `id`) so a huge audience is never
+   * materialized wholesale in the isolate — see `CreateNotifyOptions`'s
+   * `broadcastPageSize`. This call still processes the WHOLE matched
+   * audience in one request/queue message; use {@link LunoraPush.broadcastPage}
+   * directly (as `runPushBroadcastJob` does) to bound a single queue message
+   * to one page.
    */
   broadcast: (payload: PushContent, filter?: SubscriptionFilter) => Promise<BroadcastResult>;
-  /** List stored subscriptions (optionally filtered). */
-  list: (filter?: SubscriptionFilter) => Promise<StoredSubscription[]>;
+  /**
+   * Fan-out a push to ONE bounded page of stored subscriptions matching
+   * `filter` (page size: `CreateNotifyOptions`'s `broadcastPageSize`, default
+   * 250, capped by `filter.limit` when set). Same delivery semantics as
+   * {@link LunoraPush.broadcast} (retry/circuit-breaker, gone-pruning) but
+   * scoped to a single page; returns the page's own {@link BroadcastResult}
+   * plus a `nextCursor` to fetch the next page (`undefined` when done).
+   * Backs `runPushBroadcastJob` so one queue message does bounded work
+   * regardless of audience size — most app code should call
+   * {@link LunoraPush.broadcast} instead.
+   */
+  broadcastPage: (payload: PushContent, filter?: SubscriptionFilter) => Promise<BroadcastPageResult>;
+  /**
+   * List stored subscriptions (optionally filtered), with the delivery
+   * **secrets** stripped — the Web Push `keys` (RFC 8291 `auth`/`p256dh`) and the
+   * FCM `token`. Those, plus the endpoint, are enough to deliver arbitrary push to
+   * a device, so they never cross the app-facing facade; the raw rows are
+   * reachable only through the internal `SubscriptionStore`.
+   */
+  list: (filter?: SubscriptionFilter) => Promise<PushSubscriptionDevice[]>;
   /** Register (upsert) a device subscription and return the stored record. */
   register: (input: RegisterInput) => Promise<StoredSubscription>;
   /** Send a push to a single stored subscription (by id or record); `to` is derived from it. */
@@ -213,6 +307,22 @@ type WebPushConfigFactory = (env: NotifyEnv) => WebPushConfig | undefined;
 type FcmConfigFactory = (env: NotifyEnv) => FcmConfig | undefined;
 /** Options accepted by `defineNotify`. */
 interface NotifyConfig {
+  /**
+   * Exact origins (`https://host[:port]`) a client-supplied Web Push `endpoint`
+   * may register from. When set (non-empty), `register()` requires the endpoint's
+   * origin to be one of these — the strongest anti-SSRF posture, and the way to
+   * close DNS rebinding for a facade that accepts client-controlled endpoints.
+   *
+   * When unset, the default posture applies: an endpoint must be `https:` with a
+   * host a STRING classifier does not flag as private / loopback / link-local.
+   * That classifier does NOT resolve DNS, so a public hostname resolving to a
+   * private/internal IP (e.g. `https://127.0.0.1.nip.io/…`) is NOT blocked by it
+   * — `register()` also emits a one-shot dev warning in this case. Set this to the
+   * push services your app actually uses (e.g. `["https://fcm.googleapis.com",
+   * "https://updates.push.services.mozilla.com"]` — exact origins only, no
+   * wildcards) to hard-pin the boundary and close DNS rebinding.
+   */
+  allowedPushOrigins?: string[];
   /**
    * Optional chat provider factory (Slack/Discord/Teams/Telegram). Wire with a
    * provider from `@visulima/notification/providers/*`. Edge-safe (fetch-based).
@@ -303,6 +413,16 @@ declare const defineNotify: (config: NotifyConfig) => NotifyDefinition;
 declare const isNotifyDefinition: (value: unknown) => value is NotifyDefinition;
 /** Options for {@link createNotify}. */
 interface CreateNotifyOptions {
+  /**
+   * Page size for `push.broadcast`'s internal keyset pagination over the
+   * subscription store (default {@link DEFAULT_BROADCAST_PAGE_SIZE}, 250).
+   * Each page is fetched, delivered, and counted independently before the
+   * next page's store round trip, so a huge audience is never materialized
+   * wholesale in the isolate. Also the per-message bound `push.broadcastPage`
+   * (and so `runPushBroadcastJob`) uses. A test/tuning seam — most apps never
+   * need to set this.
+   */
+  broadcastPageSize?: number;
   /** Max concurrent sends during a `broadcast` (default 10). */
   concurrency?: number;
   /**
@@ -347,6 +467,11 @@ declare const createNotify: (definition: NotifyDefinition, env: NotifyEnv, optio
 };
 /** Options for {@link routingPushProvider}. */
 interface RoutingPushOptions {
+  /**
+   * The definition's exact-origin allowlist, when configured. Its presence
+   * disables the send-time rebinding re-check (see {@link assertPushTargetResolvable}).
+   */
+  allowedPushOrigins?: string[];
   fcm?: Provider<unknown, PushPayload>;
   webPush?: Provider<unknown, PushPayload>;
 }
@@ -360,6 +485,8 @@ interface RoutingPushOptions {
 declare const routingPushProvider: (options: RoutingPushOptions) => Provider<unknown, PushPayload>;
 /** A resolved, ready-to-wire set of channel configs (edge-safe channels only). */
 interface ResolvedProviders {
+  /** The definition's `allowedPushOrigins`, threaded to the push router's send-time SSRF guard. */
+  allowedPushOrigins?: string[];
   chat?: Provider;
   fcm?: FcmConfig;
   inApp?: Provider;
@@ -377,23 +504,26 @@ declare const buildEngine: (resolved: ResolvedProviders) => Notification;
  * A broadcast job body — the JSON-serialisable payload enqueued for off-request
  * fan-out. Shaped to travel through a `@lunora/queue` producer/consumer without
  * `@lunora/notify` depending on `@lunora/queue` (the seam stays structural).
+ * `filter.after`, when set, resumes a broadcast partway through (see
+ * {@link runPushBroadcastJob}'s continuation semantics).
  */
 interface PushBroadcastJob {
-  /** Subscription filter (which devices/users to target). */
+  /** Subscription filter (which devices/users to target; `filter.after` resumes a paged broadcast). */
   filter?: SubscriptionFilter;
   /** The push payload to deliver (the `to` target is derived per subscription). */
   payload: PushContent;
   /** Discriminator so a shared queue can multiplex message kinds. */
   type: "lunora.push.broadcast";
 }
-/** The structural slice of a `@lunora/queue` producer (`ctx.queues.&lt;name>`) used here. */
+/** The structural slice of a `@lunora/queue` producer (`ctx.queues.<name>`) used here. */
 interface QueueProducerLike {
   send: (body: PushBroadcastJob) => Promise<void>;
 }
 /**
  * Enqueue a fan-out broadcast for background delivery through a `@lunora/queue`
  * queue instead of blocking the request. Pair with {@link runPushBroadcastJob} in
- * the queue consumer.
+ * the queue consumer — see its doc comment for how a large audience continues
+ * across MULTIPLE messages (one bounded page per message), not one.
  *
  * ```ts
  * // in a mutation/action:
@@ -401,17 +531,59 @@ interface QueueProducerLike {
  *
  * // in lunora/queues.ts consumer:
  * export const push = defineQueue({ async handler(batch, ctx) {
- *     for (const message of batch.messages) await runPushBroadcastJob(ctx.push, message.body);
+ *     for (const message of batch.messages) {
+ *         const { nextCursor } = await runPushBroadcastJob(ctx.push, message.body);
+ *
+ *         if (nextCursor !== undefined) {
+ *             // More pages remain — enqueue the continuation. Each message still
+ *             // does only ONE bounded page of work.
+ *             await enqueuePushBroadcast(ctx.queues.push, {
+ *                 payload: message.body.payload,
+ *                 filter: { ...message.body.filter, after: nextCursor },
+ *             });
+ *         }
+ *     }
  * }});
  * ```
  */
 declare const enqueuePushBroadcast: (queue: QueueProducerLike, job: Omit<PushBroadcastJob, "type">) => Promise<void>;
 /**
- * Run an enqueued broadcast job on the consumer side, delivering through the push
- * facade (which reuses the engine's retry + circuit-breaker middleware and prunes
- * gone subscriptions).
+ * Run ONE bounded page of an enqueued broadcast job on the consumer side,
+ * delivering through the push facade's {@link LunoraPush.broadcastPage} (which
+ * reuses the engine's retry + circuit-breaker middleware and prunes gone
+ * subscriptions).
+ *
+ * RETRY / CONTINUATION SEMANTICS (rewritten for plan 222 / NOTIFY-01 — a
+ * broadcast job used to process the WHOLE audience in one message, which could
+ * exceed Worker CPU/wall limits for a large audience and made a retry re-run
+ * everything):
+ *
+ * - A job now processes exactly ONE bounded page (see `CreateNotifyOptions`'s
+ * page-size option, default 250, or `job.filter.limit` when smaller),
+ * keyset-paginated on the subscription `id` (see `SubscriptionFilter.after`)
+ * — so per-message work is bounded regardless of total audience size.
+ * - Retry is still gated on `result.failed` — the count of TRANSIENT delivery
+ * errors (a provider 5xx / network fault worth another attempt). When at
+ * least one recipient in THIS PAGE `failed`, the job is RE-THROWN so the
+ * queue does NOT ack it and its normal retry/backoff (and, on exhaustion,
+ * dead-letter) applies — to just this page, not the whole broadcast.
+ * - A page with zero `failed` resolves and is acked — this includes the
+ * all-`pruned` case (every device on the page had unsubscribed:
+ * `sent:0`, `failed:0`, `pruned:N`), which is a SUCCESSFUL prune, not a
+ * failure, so throwing on it would spuriously retry and pressure the DLQ;
+ * and the empty-page case (zero `total`), which has nothing to retry.
+ * - The returned `nextCursor` is set when more pages remain. `@lunora/notify`
+ * does NOT enqueue the continuation itself — it has no `@lunora/queue`
+ * dependency (the seam stays structural) and no reference to the producer
+ * that enqueued this message — so the CALLER (the `lunora/queues.ts`
+ * consumer) is responsible for re-enqueueing with `filter.after: nextCursor`
+ * when present. See the consumer example on {@link enqueuePushBroadcast}.
+ * - A retry of a page redelivers only that page's already-delivered recipients
+ * on a transient partial failure (a page is not individually idempotent) —
+ * the accepted cost of getting the transiently failed ones redelivered, now
+ * scoped to one page instead of the whole broadcast.
  */
-declare const runPushBroadcastJob: (push: LunoraPush, job: PushBroadcastJob) => Promise<unknown>;
+declare const runPushBroadcastJob: (push: LunoraPush, job: PushBroadcastJob) => Promise<BroadcastPageResult>;
 /**
  * The minimal structural slice of Cloudflare's `D1Database` this store uses. A
  * structural type (rather than importing `@cloudflare/workers-types`) keeps the
@@ -438,6 +610,15 @@ interface D1StoreOptions {
  * backing table is created lazily on first use (`CREATE TABLE IF NOT EXISTS`), so
  * no migration step is required for the subscription table itself.
  *
+ * ID SCHEME / LAZY MIGRATION: `id` (the `PRIMARY KEY`, upserted via `ON
+ * CONFLICT(id) DO UPDATE`) is a version-prefixed digest of the endpoint/token —
+ * currently `wp2_`/`fcm2_` (64-bit FNV-1a; see `normalize.ts`). No table migration
+ * runs when the id scheme is revised: a returning device re-registers under its new
+ * id and upserts a fresh row, while its old-prefix row (`wp_`/`fcm_`) ages out via
+ * the normal gone-pruning on the next failed send. So a table can transiently hold
+ * both an old- and new-prefix row for one device — expected, self-healing, and the
+ * reason a prefix must NEVER be reused for a different scheme.
+ *
  * ```ts
  * export default defineNotify({
  *     webPush: (env) => webPushFromEnv(env),
@@ -453,16 +634,43 @@ declare const d1SubscriptionStore: (database: D1Like, options?: D1StoreOptions)
  * (or another backing store) for production so subscriptions survive restarts.
  */
 declare const memorySubscriptionStore: () => SubscriptionStore;
-/** Stable store id for a web-push endpoint. */
+/**
+ * Stable store id for a web-push endpoint.
+ *
+ * The `wp2_` prefix is a version tag (see also {@link fcmId}'s `fcm2_`): it marks
+ * the 64-bit-id revision so the pre-existing 32-bit `wp_` rows stay readable and a
+ * returning device simply re-registers under the new id, its stale `wp_` row aging
+ * out via normal gone-pruning. A future third revision must mint `wp3_` and repeat
+ * the lazy migration — NEVER reuse a prefix.
+ */
 declare const webPushId: (endpoint: string) => string;
-/** Stable store id for an FCM device token. */
+/** Stable store id for an FCM device token. See {@link webPushId} for the `_2` version-prefix contract. */
 declare const fcmId: (token: string) => string;
+/** Options threaded into {@link normalizeRegisterInput} from the notify definition. */
+interface NormalizeOptions {
+  /**
+   * Exact origins (`https://host[:port]`) a web-push endpoint may register from.
+   * When set (non-empty), the endpoint's origin must be one of these — the
+   * strongest anti-SSRF posture, and the ONLY way to close DNS rebinding for a
+   * facade that accepts client-controlled endpoints.
+   *
+   * When unset, the default posture applies: `https:` scheme + a host the
+   * {@link assertPushEndpoint} STRING classifier does not flag as
+   * private/loopback, plus a resolved-address re-check at send time. Setting
+   * this allowlist replaces both with an exact-origin match — the hard
+   * guarantee, and the only one that also covers an internal push service you
+   * deliberately want to reach.
+   */
+  allowedPushOrigins?: string[];
+}
 /**
  * Normalise a `register(...)` input into a {@link StoredSubscription}. Validates
  * the shape (a web-push subscription needs `endpoint` + `keys.{p256dh,auth}`; an
- * FCM entry needs a non-empty `token`) and stamps `createdAt`/`lastSeenAt`.
+ * FCM entry needs a non-empty `token`), enforces the anti-SSRF endpoint boundary
+ * (see {@link assertPushEndpoint}), validates `metadata` (see
+ * {@link validateMetadata}), and stamps `createdAt`/`lastSeenAt`.
  */
-declare const normalizeRegisterInput: (input: RegisterInput, now?: number) => StoredSubscription;
+declare const normalizeRegisterInput: (input: RegisterInput, now?: number, options?: NormalizeOptions) => StoredSubscription;
 /**
  * The provider `to` target for a stored subscription: the W3C Push subscription
  * (JSON-stringified) for web-push, or the raw device token for FCM. Matches the
@@ -481,4 +689,80 @@ declare const targetOf: (subscription: StoredSubscription) => string;
  * (a cert/session expiry) can never permanently drop a valid subscription.
  */
 declare const isGoneError: (message: string | undefined) => boolean;
-export { type BroadcastOutcome, type BroadcastResult, type CreateNotifyOptions, type D1Like, type D1PreparedLike, type D1StoreOptions, FCM_ENV_KEYS, type FcmConfigFactory, type LunoraNotify, type LunoraPush, type NotifyConfig, type NotifyDefinition, type NotifyDeliveryStatus, type NotifyEnv, type NotifyLogger, type NotifyMetrics, type NotifySkipReason, type PushBroadcastJob, type PushSubscriptionDevice, type PushSubscriptionsResult, type QueueProducerLike, type RegisterInput, type ResolvedProviders, type RoutingPushOptions, type StoredSubscription, type SubscriptionFilter, type SubscriptionKind, type SubscriptionStatus, type SubscriptionStore, WEB_PUSH_ENV_KEYS, type WebPushConfigFactory, buildEngine, createNotify, d1SubscriptionStore, defineNotify, enqueuePushBroadcast, fcmFromEnv, fcmId, isGoneError, isNotifyDefinition, memorySubscriptionStore, normalizeRegisterInput, routingPushProvider, runPushBroadcastJob, targetOf, webPushFromEnv, webPushId };
+export { type BroadcastOutcome, type BroadcastResult, type CreateNotifyOptions, type D1Like, type D1PreparedLike, type D1StoreOptions,
+/**
+ * `@lunora/notify`
+ *
+ * Multi-channel notifications for Lunora, wrapping the `@visulima/notification`
+ * engine. `defineNotify` in `lunora/notify.ts` configures the edge-safe channels
+ * (Web Push + FCM, plus chat / in-app inbox / webhook); codegen wires `ctx.notify`
+ * and its `ctx.push` alias onto every handler ctx from it (mirroring `defineFlags`
+ * → `ctx.flags`).
+ *
+ * Edge-safety: Web Push (VAPID + RFC 8291) and FCM (HTTP v1) run on `fetch` + Web
+ * Crypto under workerd. APNs (`node:http2`) and SMS / Node-only queue adapters are
+ * deliberately **not** on the edge facade — route heavy fan-out through
+ * `@lunora/queue` (`enqueuePushBroadcast` / `runPushBroadcastJob`).
+ *
+ * - `@lunora/notify` — `defineNotify`, `createNotify`, config resolvers, subscription stores and types.
+ * - `@lunora/notify/web` — the browser `subscribeToPush` service-worker helper.
+ * @packageDocumentation
+ */
+FCM_ENV_KEYS, type FcmConfigFactory, type LunoraNotify, type LunoraPush, type NotifyConfig, type NotifyDefinition, type NotifyDeliveryStatus, type NotifyEnv, type NotifyLogger, type NotifyMetrics, type NotifySkipReason, type PushBroadcastJob, type PushSubscriptionDevice, type PushSubscriptionsResult, type QueueProducerLike, type RegisterInput, type ResolvedProviders, type RoutingPushOptions, type StoredSubscription, type SubscriptionFilter, type SubscriptionKind, type SubscriptionStatus, type SubscriptionStore,
+/**
+ * `@lunora/notify`
+ *
+ * Multi-channel notifications for Lunora, wrapping the `@visulima/notification`
+ * engine. `defineNotify` in `lunora/notify.ts` configures the edge-safe channels
+ * (Web Push + FCM, plus chat / in-app inbox / webhook); codegen wires `ctx.notify`
+ * and its `ctx.push` alias onto every handler ctx from it (mirroring `defineFlags`
+ * → `ctx.flags`).
+ *
+ * Edge-safety: Web Push (VAPID + RFC 8291) and FCM (HTTP v1) run on `fetch` + Web
+ * Crypto under workerd. APNs (`node:http2`) and SMS / Node-only queue adapters are
+ * deliberately **not** on the edge facade — route heavy fan-out through
+ * `@lunora/queue` (`enqueuePushBroadcast` / `runPushBroadcastJob`).
+ *
+ * - `@lunora/notify` — `defineNotify`, `createNotify`, config resolvers, subscription stores and types.
+ * - `@lunora/notify/web` — the browser `subscribeToPush` service-worker helper.
+ * @packageDocumentation
+ */
+WEB_PUSH_ENV_KEYS, type WebPushConfigFactory, buildEngine, createNotify, d1SubscriptionStore, defineNotify, enqueuePushBroadcast,
+/**
+ * `@lunora/notify`
+ *
+ * Multi-channel notifications for Lunora, wrapping the `@visulima/notification`
+ * engine. `defineNotify` in `lunora/notify.ts` configures the edge-safe channels
+ * (Web Push + FCM, plus chat / in-app inbox / webhook); codegen wires `ctx.notify`
+ * and its `ctx.push` alias onto every handler ctx from it (mirroring `defineFlags`
+ * → `ctx.flags`).
+ *
+ * Edge-safety: Web Push (VAPID + RFC 8291) and FCM (HTTP v1) run on `fetch` + Web
+ * Crypto under workerd. APNs (`node:http2`) and SMS / Node-only queue adapters are
+ * deliberately **not** on the edge facade — route heavy fan-out through
+ * `@lunora/queue` (`enqueuePushBroadcast` / `runPushBroadcastJob`).
+ *
+ * - `@lunora/notify` — `defineNotify`, `createNotify`, config resolvers, subscription stores and types.
+ * - `@lunora/notify/web` — the browser `subscribeToPush` service-worker helper.
+ * @packageDocumentation
+ */
+fcmFromEnv, fcmId, isGoneError, isNotifyDefinition, memorySubscriptionStore, normalizeRegisterInput, routingPushProvider, runPushBroadcastJob, targetOf,
+/**
+ * `@lunora/notify`
+ *
+ * Multi-channel notifications for Lunora, wrapping the `@visulima/notification`
+ * engine. `defineNotify` in `lunora/notify.ts` configures the edge-safe channels
+ * (Web Push + FCM, plus chat / in-app inbox / webhook); codegen wires `ctx.notify`
+ * and its `ctx.push` alias onto every handler ctx from it (mirroring `defineFlags`
+ * → `ctx.flags`).
+ *
+ * Edge-safety: Web Push (VAPID + RFC 8291) and FCM (HTTP v1) run on `fetch` + Web
+ * Crypto under workerd. APNs (`node:http2`) and SMS / Node-only queue adapters are
+ * deliberately **not** on the edge facade — route heavy fan-out through
+ * `@lunora/queue` (`enqueuePushBroadcast` / `runPushBroadcastJob`).
+ *
+ * - `@lunora/notify` — `defineNotify`, `createNotify`, config resolvers, subscription stores and types.
+ * - `@lunora/notify/web` — the browser `subscribeToPush` service-worker helper.
+ * @packageDocumentation
+ */
+webPushFromEnv, webPushId };