@everfur/sdk 0.12.0 → 0.13.0

package/dist/parse.d-C8CXyS58.d.ts

@@ -0,0 +1,210 @@
+import { E as EverfurError } from './EverfurError.d-8NHtlgzA.js';
+import { E as EverfurResult } from './EverfurResult.d-D_-254ZY.js';
+import { E as ErrorPolicyPort } from './ErrorPolicyPort.d-68yrE3BE.js';
+import { A as AuthContext } from './identity.d-DzTijonw.js';
+import { U as UserRef, R as RecordsRequestId, P as PetRef, C as ConversationId } from './ids.d-B2GAAifq.js';
+import { V as VetVisitIntent } from './visitIntent.d-D7_yVp1I.js';
+
+/** The push providers the registration route accepts. `apns` is refused with `provider_unsupported` until APNs direct lands. */
+type PushProvider = 'expo' | 'fcm' | 'apns';
+/** The device platforms the registration route accepts. There is no web push in this version. */
+type DevicePlatform = 'ios' | 'android';
+/** What to register: the token your notification library obtained, which provider minted it, and which OS it is for. */
+interface RegisterDeviceInput {
+    /**
+     * The push token as your library printed it: `ExponentPushToken[...]` from expo-notifications, or the FCM
+     * registration token from Firebase Messaging. Never an APNs device token in this version.
+     */
+    readonly token: string;
+    readonly provider: PushProvider;
+    readonly platform: DevicePlatform;
+    /** Your own stable id for this install, if you keep one (1 to 128 characters). Echoed back, never interpreted. */
+    readonly installationId?: string;
+}
+/** The device row as Everfur stored it. The token itself is never echoed. */
+interface RegisteredDevice {
+    /** Everfur's id for this device: pass it to `unregisterDevice` on sign-out. */
+    readonly deviceId: string;
+    readonly provider: PushProvider;
+    readonly platform: DevicePlatform;
+    readonly installationId: string | null;
+    /** ISO 8601. */
+    readonly registeredAt: string;
+    /** ISO 8601; refreshed by every registration of the same token. */
+    readonly lastSeenAt: string;
+}
+/** Both switches, always: the route is a replacement, not a patch. */
+interface NotificationPreferencesInput {
+    readonly pushEnabled: boolean;
+    readonly emailEnabled: boolean;
+}
+/** The member's switches as Everfur stored them. */
+interface NotificationPreferences {
+    readonly pushEnabled: boolean;
+    readonly emailEnabled: boolean;
+    /** ISO 8601. */
+    readonly updatedAt: string;
+}
+interface NotificationsClient {
+    /**
+     * `POST /widget/v1/me/devices`. Idempotent: the same token is the same device (its `lastSeenAt` moves), and a token
+     * another member of your tenant registered rebinds to the calling member. Settles `ok(RegisteredDevice)`;
+     * `validationFailed` with `reasonCode` `provider_unsupported` or `token_invalid`; `serviceUnavailable` with
+     * `reasonCode` `device_cipher_unavailable` (retry later); `rateLimited` above ten registrations a minute; the
+     * not-found error while notifications are not enabled for your tenant; `sessionRequired` for a publishable-key caller.
+     */
+    registerDevice(input: RegisterDeviceInput, opts?: {
+        readonly signal?: AbortSignal;
+    }): Promise<EverfurResult<RegisteredDevice>>;
+    /**
+     * `DELETE /widget/v1/me/devices/{device_id}`. Settles `ok(undefined)` on 204; an unknown id and another member's
+     * device are the same not-found error.
+     */
+    unregisterDevice(deviceId: string, opts?: {
+        readonly signal?: AbortSignal;
+    }): Promise<EverfurResult<void>>;
+    /** `PUT /widget/v1/me/notification-preferences`. Settles `ok(NotificationPreferences)`. */
+    setPreferences(input: NotificationPreferencesInput, opts?: {
+        readonly signal?: AbortSignal;
+    }): Promise<EverfurResult<NotificationPreferences>>;
+}
+/**
+ * The part of the runtime this client needs: the current auth at call time, the partner's error policy, and whether
+ * the runtime is gone. `useEverfurContext().runtime` (any `EverfurRuntime`) satisfies it; the narrow shape keeps this
+ * subpath's public types to what it reads.
+ */
+interface NotificationsRuntime {
+    readonly isDisposed: boolean;
+    readonly registry: {
+        readonly services: {
+            authFor(userRef: UserRef | null): AuthContext;
+            readonly errorPolicy: ErrorPolicyPort | undefined;
+        };
+    };
+}
+/** The sub-reasons a notifications call, or a delivery, can carry as `EverfurError.reasonCode`. */
+type NotificationsReasonCode = 'provider_unsupported' | 'token_invalid' | 'device_cipher_unavailable' | 'credentials_missing';
+/**
+ * DEVELOPER-FACING explanations, one per reason. Log them, show them on a developer screen, never render them to a
+ * member: `displayMessage` is the copy a person sees. `credentials_missing` is not a route answer but the reason a
+ * delivery is skipped on Everfur's side (visible on the events API and in the partner console); it is here so one
+ * table explains every reason this surface can name.
+ */
+declare const NOTIFICATIONS_REASON_MESSAGES: Readonly<Record<NotificationsReasonCode, string>>;
+/** The developer-facing sentence for an error's `reasonCode`, or null when it carries none this surface knows. */
+declare function explainNotificationsReason(error: EverfurError): string | null;
+/**
+ * The client over the runtime under your provider (`useEverfurContext().runtime`). Auth is read at call time, so the
+ * client can be built once and reused across sign-ins; a disposed runtime settles every verb without a request.
+ */
+declare function createNotificationsClient(runtime: NotificationsRuntime): NotificationsClient;
+
+/** What the hook needs from you: the token your notification library obtained, or null until you have one. */
+interface EverfurNotificationsOptions {
+    /**
+     * The push token as your library printed it (`ExponentPushToken[...]`, or an FCM registration token), or null
+     * while you do not have one (permission not asked, not granted, or the token not yet fetched). Nothing is
+     * registered without it; pass it as soon as you have it and the hook registers.
+     */
+    readonly token: string | null;
+    /** `expo` for a token from expo-notifications, `fcm` for a Firebase registration token. */
+    readonly provider: PushProvider;
+    readonly platform: DevicePlatform;
+    /** Your own stable id for this install, if you keep one. */
+    readonly installationId?: string;
+}
+/**
+ * `signed_out`: no signed-in user on the provider (nothing to register). `no_token`: a user, no token yet.
+ * `registering` / `registered` / `failed` / `unavailable`: the registration of the current token.
+ * `unavailable` is the dark tenant: notifications are not enabled for your client (the routes answer 404).
+ * `unregistered`: `unregister()` was called; `register()` registers again.
+ */
+type EverfurNotificationsStatus = 'signed_out' | 'no_token' | 'registering' | 'registered' | 'unavailable' | 'failed' | 'unregistered';
+interface EverfurNotificationsState {
+    readonly status: EverfurNotificationsStatus;
+    /** The device Everfur registered for this install and user, or null. */
+    readonly device: RegisteredDevice | null;
+    /** The settled failure of the last registration, or null. `error.displayMessage` is safe to show. */
+    readonly error: EverfurError | null;
+    /** Register the current token now (a retry after `failed`, or after `unregister()`). Settles, never throws. */
+    register(): Promise<EverfurResult<RegisteredDevice>>;
+    /** Unregister this install's device for the signed-in user. Settles, never throws. */
+    unregister(): Promise<EverfurResult<void>>;
+    /** The member's push and email switches, both at once (`PUT /widget/v1/me/notification-preferences`). */
+    setPreferences(input: NotificationPreferencesInput): Promise<EverfurResult<NotificationPreferences>>;
+}
+/**
+ * The notifications client bound to the runtime under your provider, for the imperative calls (`setPreferences`
+ * from a settings screen, say). Auth is read at call time, so one client serves every sign-in.
+ */
+declare function useEverfurNotificationsClient(): NotificationsClient;
+/**
+ * Register this install's push token for the signed-in member, keep it registered as the token and the user
+ * change, and unregister it before sign-out. Call it once, high in the tree under `EverfurProvider`.
+ */
+declare function useEverfurNotifications(options: EverfurNotificationsOptions): EverfurNotificationsState;
+
+/** The version of the routing block this release reads. */
+declare const EVERFUR_NOTIFICATION_VERSION = 1;
+/** The closed target kinds, in the backend's order (`partner_target.py` TARGET_KINDS). */
+declare const EVERFUR_NOTIFICATION_TARGET_KINDS: readonly ["record_request", "pet", "visit", "case"];
+/** One target kind. */
+type EverfurNotificationTargetKind = (typeof EVERFUR_NOTIFICATION_TARGET_KINDS)[number];
+/**
+ * The event types Everfur builds a push target for (`partner_target.py` TARGET_BUILDERS), in its order. The member
+ * events, the urgency verdict and the endpoint test event reach the partner's webhook only and never a device, and
+ * `visit.completed`, `visit.rescheduled` and `visit.ended` carry no consumer copy, so they are never pushed either;
+ * they are listed because the platform builds their target.
+ */
+declare const EVERFUR_NOTIFICATION_EVENT_TYPES: readonly ["record_request.updated", "record.ready", "pet.vaccination.due", "visit.booked", "visit.cancelled", "visit.completed", "visit.no_show", "visit.rescheduled", "visit.reminder", "visit.followup_sent", "visit.message_received", "visit.ended", "chat.follow_up_due", "chat.reminder_due", "record.activation"];
+/** One pushed event type. */
+type EverfurNotificationEventType = (typeof EVERFUR_NOTIFICATION_EVENT_TYPES)[number];
+/** What a tapped notification is about, keyed on `kind`. The optional references are null when the push carried none. */
+type EverfurNotificationTarget = {
+    /**
+     * A records request (`record_request.updated`, `record.ready`, and `record.activation`, which says what the
+     * request's parse found): open that request.
+     */
+    readonly kind: 'record_request';
+    readonly requestId: RecordsRequestId;
+    readonly petRef: PetRef | null;
+} | {
+    /** A pet: `pet.vaccination.due` opens that pet's records, `chat.reminder_due` that pet's chat. */
+    readonly kind: 'pet';
+    readonly petRef: PetRef;
+} | {
+    /**
+     * A vet visit (`visit.*`): open that visit. `visitRef` is the partner visit reference the visit events carry.
+     * `intent` is what to open for it, derived from the event type with the consumer app's routing (the push
+     * itself carries none): `visit` for a booking or a change to it, `join` for a reminder, `messages` for the
+     * vet's reply or the follow-up, `summary` for a completed visit. Pass both to `useVetVisit().openVisit`.
+     * `null` for a cancelled or missed visit: there is nothing left to open, so route to a new booking.
+     */
+    readonly kind: 'visit';
+    readonly visitRef: string;
+    readonly petRef: PetRef | null;
+    readonly intent: VetVisitIntent | null;
+} | {
+    /** A follow-up case (`chat.follow_up_due`): open the conversation the check-in landed in. */
+    readonly kind: 'case';
+    readonly caseRef: string;
+    readonly conversationId: ConversationId | null;
+    readonly petRef: PetRef | null;
+};
+/** A parsed push: the event it announces and the thing to open. Frozen. */
+interface EverfurNotification {
+    /** `evt_` plus the public event id, the same id the webhook envelope for this event carries. */
+    readonly eventId: string;
+    readonly eventType: EverfurNotificationEventType;
+    readonly target: EverfurNotificationTarget;
+}
+/**
+ * Read the Everfur routing block out of a received push, or null when there is none or it is not one Everfur would
+ * send. Pure and total: it never throws, whatever it is handed.
+ *
+ * Pass the object your notification library gave you: an expo-notifications `Notification` or `NotificationResponse`,
+ * an FCM `RemoteMessage`, or its `data` map. Route on `target.kind`; `eventType` says why the push was sent.
+ */
+declare function parseEverfurNotification(payload: unknown): EverfurNotification | null;
+
+export { type DevicePlatform as D, type EverfurNotificationsOptions as E, NOTIFICATIONS_REASON_MESSAGES as N, type PushProvider as P, type RegisterDeviceInput as R, type EverfurNotificationsState as a, EVERFUR_NOTIFICATION_EVENT_TYPES as b, EVERFUR_NOTIFICATION_TARGET_KINDS as c, EVERFUR_NOTIFICATION_VERSION as d, type EverfurNotification as e, type EverfurNotificationEventType as f, type EverfurNotificationTarget as g, type EverfurNotificationTargetKind as h, type EverfurNotificationsStatus as i, type NotificationPreferences as j, type NotificationPreferencesInput as k, type NotificationsClient as l, type NotificationsReasonCode as m, type NotificationsRuntime as n, type RegisteredDevice as o, createNotificationsClient as p, explainNotificationsReason as q, parseEverfurNotification as r, useEverfurNotifications as s, useEverfurNotificationsClient as u };

package/dist/parse.d-tEzufgJX.d.cts

@@ -0,0 +1,210 @@
+import { E as EverfurError } from './EverfurError.d-8NHtlgzA.cjs';
+import { E as EverfurResult } from './EverfurResult.d-BFH-3s6E.cjs';
+import { E as ErrorPolicyPort } from './ErrorPolicyPort.d-DirW9hgO.cjs';
+import { A as AuthContext } from './identity.d-60LeJt_s.cjs';
+import { U as UserRef, R as RecordsRequestId, P as PetRef, C as ConversationId } from './ids.d-B2GAAifq.cjs';
+import { V as VetVisitIntent } from './visitIntent.d-D7_yVp1I.cjs';
+
+/** The push providers the registration route accepts. `apns` is refused with `provider_unsupported` until APNs direct lands. */
+type PushProvider = 'expo' | 'fcm' | 'apns';
+/** The device platforms the registration route accepts. There is no web push in this version. */
+type DevicePlatform = 'ios' | 'android';
+/** What to register: the token your notification library obtained, which provider minted it, and which OS it is for. */
+interface RegisterDeviceInput {
+    /**
+     * The push token as your library printed it: `ExponentPushToken[...]` from expo-notifications, or the FCM
+     * registration token from Firebase Messaging. Never an APNs device token in this version.
+     */
+    readonly token: string;
+    readonly provider: PushProvider;
+    readonly platform: DevicePlatform;
+    /** Your own stable id for this install, if you keep one (1 to 128 characters). Echoed back, never interpreted. */
+    readonly installationId?: string;
+}
+/** The device row as Everfur stored it. The token itself is never echoed. */
+interface RegisteredDevice {
+    /** Everfur's id for this device: pass it to `unregisterDevice` on sign-out. */
+    readonly deviceId: string;
+    readonly provider: PushProvider;
+    readonly platform: DevicePlatform;
+    readonly installationId: string | null;
+    /** ISO 8601. */
+    readonly registeredAt: string;
+    /** ISO 8601; refreshed by every registration of the same token. */
+    readonly lastSeenAt: string;
+}
+/** Both switches, always: the route is a replacement, not a patch. */
+interface NotificationPreferencesInput {
+    readonly pushEnabled: boolean;
+    readonly emailEnabled: boolean;
+}
+/** The member's switches as Everfur stored them. */
+interface NotificationPreferences {
+    readonly pushEnabled: boolean;
+    readonly emailEnabled: boolean;
+    /** ISO 8601. */
+    readonly updatedAt: string;
+}
+interface NotificationsClient {
+    /**
+     * `POST /widget/v1/me/devices`. Idempotent: the same token is the same device (its `lastSeenAt` moves), and a token
+     * another member of your tenant registered rebinds to the calling member. Settles `ok(RegisteredDevice)`;
+     * `validationFailed` with `reasonCode` `provider_unsupported` or `token_invalid`; `serviceUnavailable` with
+     * `reasonCode` `device_cipher_unavailable` (retry later); `rateLimited` above ten registrations a minute; the
+     * not-found error while notifications are not enabled for your tenant; `sessionRequired` for a publishable-key caller.
+     */
+    registerDevice(input: RegisterDeviceInput, opts?: {
+        readonly signal?: AbortSignal;
+    }): Promise<EverfurResult<RegisteredDevice>>;
+    /**
+     * `DELETE /widget/v1/me/devices/{device_id}`. Settles `ok(undefined)` on 204; an unknown id and another member's
+     * device are the same not-found error.
+     */
+    unregisterDevice(deviceId: string, opts?: {
+        readonly signal?: AbortSignal;
+    }): Promise<EverfurResult<void>>;
+    /** `PUT /widget/v1/me/notification-preferences`. Settles `ok(NotificationPreferences)`. */
+    setPreferences(input: NotificationPreferencesInput, opts?: {
+        readonly signal?: AbortSignal;
+    }): Promise<EverfurResult<NotificationPreferences>>;
+}
+/**
+ * The part of the runtime this client needs: the current auth at call time, the partner's error policy, and whether
+ * the runtime is gone. `useEverfurContext().runtime` (any `EverfurRuntime`) satisfies it; the narrow shape keeps this
+ * subpath's public types to what it reads.
+ */
+interface NotificationsRuntime {
+    readonly isDisposed: boolean;
+    readonly registry: {
+        readonly services: {
+            authFor(userRef: UserRef | null): AuthContext;
+            readonly errorPolicy: ErrorPolicyPort | undefined;
+        };
+    };
+}
+/** The sub-reasons a notifications call, or a delivery, can carry as `EverfurError.reasonCode`. */
+type NotificationsReasonCode = 'provider_unsupported' | 'token_invalid' | 'device_cipher_unavailable' | 'credentials_missing';
+/**
+ * DEVELOPER-FACING explanations, one per reason. Log them, show them on a developer screen, never render them to a
+ * member: `displayMessage` is the copy a person sees. `credentials_missing` is not a route answer but the reason a
+ * delivery is skipped on Everfur's side (visible on the events API and in the partner console); it is here so one
+ * table explains every reason this surface can name.
+ */
+declare const NOTIFICATIONS_REASON_MESSAGES: Readonly<Record<NotificationsReasonCode, string>>;
+/** The developer-facing sentence for an error's `reasonCode`, or null when it carries none this surface knows. */
+declare function explainNotificationsReason(error: EverfurError): string | null;
+/**
+ * The client over the runtime under your provider (`useEverfurContext().runtime`). Auth is read at call time, so the
+ * client can be built once and reused across sign-ins; a disposed runtime settles every verb without a request.
+ */
+declare function createNotificationsClient(runtime: NotificationsRuntime): NotificationsClient;
+
+/** What the hook needs from you: the token your notification library obtained, or null until you have one. */
+interface EverfurNotificationsOptions {
+    /**
+     * The push token as your library printed it (`ExponentPushToken[...]`, or an FCM registration token), or null
+     * while you do not have one (permission not asked, not granted, or the token not yet fetched). Nothing is
+     * registered without it; pass it as soon as you have it and the hook registers.
+     */
+    readonly token: string | null;
+    /** `expo` for a token from expo-notifications, `fcm` for a Firebase registration token. */
+    readonly provider: PushProvider;
+    readonly platform: DevicePlatform;
+    /** Your own stable id for this install, if you keep one. */
+    readonly installationId?: string;
+}
+/**
+ * `signed_out`: no signed-in user on the provider (nothing to register). `no_token`: a user, no token yet.
+ * `registering` / `registered` / `failed` / `unavailable`: the registration of the current token.
+ * `unavailable` is the dark tenant: notifications are not enabled for your client (the routes answer 404).
+ * `unregistered`: `unregister()` was called; `register()` registers again.
+ */
+type EverfurNotificationsStatus = 'signed_out' | 'no_token' | 'registering' | 'registered' | 'unavailable' | 'failed' | 'unregistered';
+interface EverfurNotificationsState {
+    readonly status: EverfurNotificationsStatus;
+    /** The device Everfur registered for this install and user, or null. */
+    readonly device: RegisteredDevice | null;
+    /** The settled failure of the last registration, or null. `error.displayMessage` is safe to show. */
+    readonly error: EverfurError | null;
+    /** Register the current token now (a retry after `failed`, or after `unregister()`). Settles, never throws. */
+    register(): Promise<EverfurResult<RegisteredDevice>>;
+    /** Unregister this install's device for the signed-in user. Settles, never throws. */
+    unregister(): Promise<EverfurResult<void>>;
+    /** The member's push and email switches, both at once (`PUT /widget/v1/me/notification-preferences`). */
+    setPreferences(input: NotificationPreferencesInput): Promise<EverfurResult<NotificationPreferences>>;
+}
+/**
+ * The notifications client bound to the runtime under your provider, for the imperative calls (`setPreferences`
+ * from a settings screen, say). Auth is read at call time, so one client serves every sign-in.
+ */
+declare function useEverfurNotificationsClient(): NotificationsClient;
+/**
+ * Register this install's push token for the signed-in member, keep it registered as the token and the user
+ * change, and unregister it before sign-out. Call it once, high in the tree under `EverfurProvider`.
+ */
+declare function useEverfurNotifications(options: EverfurNotificationsOptions): EverfurNotificationsState;
+
+/** The version of the routing block this release reads. */
+declare const EVERFUR_NOTIFICATION_VERSION = 1;
+/** The closed target kinds, in the backend's order (`partner_target.py` TARGET_KINDS). */
+declare const EVERFUR_NOTIFICATION_TARGET_KINDS: readonly ["record_request", "pet", "visit", "case"];
+/** One target kind. */
+type EverfurNotificationTargetKind = (typeof EVERFUR_NOTIFICATION_TARGET_KINDS)[number];
+/**
+ * The event types Everfur builds a push target for (`partner_target.py` TARGET_BUILDERS), in its order. The member
+ * events, the urgency verdict and the endpoint test event reach the partner's webhook only and never a device, and
+ * `visit.completed`, `visit.rescheduled` and `visit.ended` carry no consumer copy, so they are never pushed either;
+ * they are listed because the platform builds their target.
+ */
+declare const EVERFUR_NOTIFICATION_EVENT_TYPES: readonly ["record_request.updated", "record.ready", "pet.vaccination.due", "visit.booked", "visit.cancelled", "visit.completed", "visit.no_show", "visit.rescheduled", "visit.reminder", "visit.followup_sent", "visit.message_received", "visit.ended", "chat.follow_up_due", "chat.reminder_due", "record.activation"];
+/** One pushed event type. */
+type EverfurNotificationEventType = (typeof EVERFUR_NOTIFICATION_EVENT_TYPES)[number];
+/** What a tapped notification is about, keyed on `kind`. The optional references are null when the push carried none. */
+type EverfurNotificationTarget = {
+    /**
+     * A records request (`record_request.updated`, `record.ready`, and `record.activation`, which says what the
+     * request's parse found): open that request.
+     */
+    readonly kind: 'record_request';
+    readonly requestId: RecordsRequestId;
+    readonly petRef: PetRef | null;
+} | {
+    /** A pet: `pet.vaccination.due` opens that pet's records, `chat.reminder_due` that pet's chat. */
+    readonly kind: 'pet';
+    readonly petRef: PetRef;
+} | {
+    /**
+     * A vet visit (`visit.*`): open that visit. `visitRef` is the partner visit reference the visit events carry.
+     * `intent` is what to open for it, derived from the event type with the consumer app's routing (the push
+     * itself carries none): `visit` for a booking or a change to it, `join` for a reminder, `messages` for the
+     * vet's reply or the follow-up, `summary` for a completed visit. Pass both to `useVetVisit().openVisit`.
+     * `null` for a cancelled or missed visit: there is nothing left to open, so route to a new booking.
+     */
+    readonly kind: 'visit';
+    readonly visitRef: string;
+    readonly petRef: PetRef | null;
+    readonly intent: VetVisitIntent | null;
+} | {
+    /** A follow-up case (`chat.follow_up_due`): open the conversation the check-in landed in. */
+    readonly kind: 'case';
+    readonly caseRef: string;
+    readonly conversationId: ConversationId | null;
+    readonly petRef: PetRef | null;
+};
+/** A parsed push: the event it announces and the thing to open. Frozen. */
+interface EverfurNotification {
+    /** `evt_` plus the public event id, the same id the webhook envelope for this event carries. */
+    readonly eventId: string;
+    readonly eventType: EverfurNotificationEventType;
+    readonly target: EverfurNotificationTarget;
+}
+/**
+ * Read the Everfur routing block out of a received push, or null when there is none or it is not one Everfur would
+ * send. Pure and total: it never throws, whatever it is handed.
+ *
+ * Pass the object your notification library gave you: an expo-notifications `Notification` or `NotificationResponse`,
+ * an FCM `RemoteMessage`, or its `data` map. Route on `target.kind`; `eventType` says why the push was sent.
+ */
+declare function parseEverfurNotification(payload: unknown): EverfurNotification | null;
+
+export { type DevicePlatform as D, type EverfurNotificationsOptions as E, NOTIFICATIONS_REASON_MESSAGES as N, type PushProvider as P, type RegisterDeviceInput as R, type EverfurNotificationsState as a, EVERFUR_NOTIFICATION_EVENT_TYPES as b, EVERFUR_NOTIFICATION_TARGET_KINDS as c, EVERFUR_NOTIFICATION_VERSION as d, type EverfurNotification as e, type EverfurNotificationEventType as f, type EverfurNotificationTarget as g, type EverfurNotificationTargetKind as h, type EverfurNotificationsStatus as i, type NotificationPreferences as j, type NotificationPreferencesInput as k, type NotificationsClient as l, type NotificationsReasonCode as m, type NotificationsRuntime as n, type RegisteredDevice as o, createNotificationsClient as p, explainNotificationsReason as q, parseEverfurNotification as r, useEverfurNotifications as s, useEverfurNotificationsClient as u };

package/dist/{pets-BYALZTSu.d.ts → pets.d-C_53_fzo.d.ts}

@@ -1,6 +1,6 @@
-import { E as EverfurResult } from './EverfurResult-ClPTS0P2.js';
-import { j as FetchLike } from './config-DmFAZJOx.js';
-import { P as PetHealthProfileInput, a as PetHealthProfile } from './profile-CSs1wlXT.js';
+import { E as EverfurResult } from './EverfurResult.d-D_-254ZY.js';
+import { j as FetchLike } from './config.d-Dy6igYlH.js';
+import { P as PetHealthProfileInput, a as PetHealthProfile } from './profile.d-CSs1wlXT.js';
 
 /** How your backend reaches Everfur for pet writes. Build it once and reuse it. */
 interface PartnerServerClient {

package/dist/{pets-CcyPQS-H.d.cts → pets.d-NbJvP_kh.d.cts}

@@ -1,6 +1,6 @@
-import { E as EverfurResult } from './EverfurResult-COlXj1wq.cjs';
-import { j as FetchLike } from './config-B0p6Lygh.cjs';
-import { P as PetHealthProfileInput, a as PetHealthProfile } from './profile-CSs1wlXT.cjs';
+import { E as EverfurResult } from './EverfurResult.d-BFH-3s6E.cjs';
+import { j as FetchLike } from './config.d-BR3DT9ho.cjs';
+import { P as PetHealthProfileInput, a as PetHealthProfile } from './profile.d-CSs1wlXT.cjs';
 
 /** How your backend reaches Everfur for pet writes. Build it once and reuse it. */
 interface PartnerServerClient {

package/dist/{petsRepository-B_Q1gFkE.d.cts → petsRepository.d-BuGHymNx.d.ts}

@@ -1,7 +1,7 @@
-import { E as EverfurResult } from './EverfurResult-COlXj1wq.cjs';
-import { A as AuthContext } from './identity-DFVGYn1o.cjs';
-import { P as PetRef } from './ids-B2GAAifq.cjs';
-import { P as PetHealthProfileInput, a as PetHealthProfile } from './profile-CSs1wlXT.cjs';
+import { E as EverfurResult } from './EverfurResult.d-D_-254ZY.js';
+import { A as AuthContext } from './identity.d-DzTijonw.js';
+import { P as PetRef } from './ids.d-B2GAAifq.js';
+import { P as PetHealthProfileInput, a as PetHealthProfile } from './profile.d-CSs1wlXT.js';
 
 /**
  * Server-declared bounds on `WidgetPetInput`, mirrored so a violation is refused before the wire rather

package/dist/{petsRepository-518QkPxH.d.ts → petsRepository.d-lp1BHRqM.d.cts}

@@ -1,7 +1,7 @@
-import { E as EverfurResult } from './EverfurResult-ClPTS0P2.js';
-import { A as AuthContext } from './identity-Cw07BKZp.js';
-import { P as PetRef } from './ids-B2GAAifq.js';
-import { P as PetHealthProfileInput, a as PetHealthProfile } from './profile-CSs1wlXT.js';
+import { E as EverfurResult } from './EverfurResult.d-BFH-3s6E.cjs';
+import { A as AuthContext } from './identity.d-60LeJt_s.cjs';
+import { P as PetRef } from './ids.d-B2GAAifq.cjs';
+import { P as PetHealthProfileInput, a as PetHealthProfile } from './profile.d-CSs1wlXT.cjs';
 
 /**
  * Server-declared bounds on `WidgetPetInput`, mirrored so a violation is refused before the wire rather