@everfur/sdk 0.12.1 → 0.14.0

package/dist/{Chat-CbyZ1vAX.d.cts → Chat.d-puminpyi.d.ts}

@@ -1,16 +1,143 @@
 import { ReactNode } from 'react';
 import { StyleProp, ViewStyle } from 'react-native';
-import { P as PetRef, C as ConversationId } from './ids-B2GAAifq.cjs';
-import { F as FileHandle } from './ports-BN6RHF9W.cjs';
-import { a as ChatCheckinTarget } from './ports-gJ3faaWz.cjs';
-import { W as WidgetPet, P as PetProfileInput } from './petsRepository-Cqpd3hLU.cjs';
-import { U as UrgencyDisplayLevel, L as LifecyclePort, E as EverfurChatDraftStore } from './attachments-BOk3hEAM.cjs';
+import { P as PetRef, C as ConversationId } from './ids.d-B2GAAifq.js';
+import { i as EverfurPresentationInput } from './presentation.d-vy8kTGfR.js';
+import { a as ChatCheckinTarget } from './ports.d-D2n4HRUy.js';
+import { W as WidgetPet, P as PetProfileInput } from './petsRepository.d-RGwSZcYl.js';
+import { E as EverfurStarterPrompt } from './quickPrompts.d-NM_81Jc1.js';
+import { L as LifecyclePort } from './LifecyclePort.d-Cr1p33a7.js';
+import { U as UrgencyDisplayLevel, E as EverfurChatDraftStore } from './attachments.d-rp3xs-Q3.js';
+import { F as FileHandle } from './ports.d-BX4f4UsB.js';
 
 /** Where a picked image comes from: the host's photo library, or its camera. */
 type AttachmentSource = 'photo' | 'camera';
 
-/** The host's own action for the two vet-care tiers, in place of Everfur's pill. */
-type RenderVetAction = (level: UrgencyDisplayLevel) => ReactNode;
+/**
+ * The history bar: a "Chats" control with the member's thread count that opens the history, and a "New chat"
+ * control. For a surface that hides the SDK header and still wants the member's past chats.
+ */
+interface EverfurChatHistoryBar {
+    /** The history control's words ("Chats"). */
+    readonly chats: string;
+    /** The new-chat control's words ("New chat"). */
+    readonly newChat: string;
+    /** Draw the two icons your way. */
+    readonly renderIcon?: (icon: 'history' | 'edit') => ReactNode;
+    /** Your own control after "Chats". Absent, nothing is drawn. */
+    readonly extra?: ReactNode;
+}
+/** The empty thread's own title and chip fills. Absent, the empty state is Everfur's own. */
+interface EverfurChatEmptyState {
+    /** The title over the starter chips, in place of "What can we help {pet} with today?". */
+    readonly title?: string;
+    /**
+     * Fills for the chips that bring none of their own, taken in turn (the first chip the first fill, and round
+     * again). Each is a fill and its ink. Absent, Raph's v3 cycle on a light theme; empty, the theme's paint.
+     */
+    readonly chipTints?: readonly {
+        readonly tint: string;
+        readonly ink?: string;
+    }[];
+}
+/** One card under an answer in the cards answer style: a record, a stat, or a link to one of your screens. */
+interface EverfurChatAnswerCard {
+    /** Stable key within the answer. */
+    readonly key: string;
+    readonly title: string;
+    /** The small line under the title. */
+    readonly meta?: string;
+    /** A status pill. */
+    readonly pill?: {
+        readonly label: string;
+        readonly tone?: string;
+    };
+    /** A stat card's value: drawn in place of the pill and the chevron. */
+    readonly value?: {
+        readonly amount: string;
+        readonly unit?: string;
+    };
+    /** The tile at the start: an icon of yours, or an https image. */
+    readonly tile?: {
+        readonly icon?: ReactNode;
+        readonly imageUrl?: string;
+        readonly tone?: string;
+    };
+    readonly variant?: string;
+    /** Given, the card is a button that calls this. Absent, a static card. */
+    readonly onPress?: () => void;
+    /** A card of your own, drawn in the card's place. If it throws, the slot draws nothing. */
+    readonly render?: () => ReactNode;
+}
+/** What `answerCards.cards` receives: the settled answer's text and the question it answered. */
+interface EverfurChatAnswerContext {
+    readonly answer: string;
+    readonly question: string | null;
+    /** The answer's message id, stable for the life of the thread. */
+    readonly messageId: string;
+}
+/** The cards answer style's content (used while presentation `chatAnswerStyle` is `cards`). The words are yours. */
+interface EverfurChatAnswerCards {
+    /** The line over each answer (an icon and your words). Absent, the assistant's name line. */
+    readonly byline?: {
+        readonly label: string;
+        readonly icon?: ReactNode;
+    };
+    /** Your cards under a settled answer. A throw draws none. */
+    readonly cards?: (context: EverfurChatAnswerContext) => readonly EverfurChatAnswerCard[];
+    /** Two feedback chips in place of the footer's thumbs, mapped to thumbs up and thumbs down. */
+    readonly feedback?: {
+        readonly helpful: string;
+        readonly notHelpful: string;
+    };
+    /** Your own rows at the top of the follow-ups, for the answer it receives. */
+    readonly followUpActions?: (context: EverfurChatAnswerContext) => readonly EverfurChatFollowUpAction[];
+    /** Draw the chevron your way. Absent, Everfur's glyph. */
+    readonly renderIcon?: (icon: 'chevron') => ReactNode;
+}
+/** A row of yours at the top of the follow-ups under an answer. */
+interface EverfurChatFollowUpAction {
+    readonly key: string;
+    readonly label: string;
+    readonly icon?: ReactNode;
+    readonly onPress: () => void;
+}
+/**
+ * The card at the top of the empty thread (presentation `chatTopCard: "focus"`): one finding, in your words, with
+ * an action of yours and a question it can ask in the thread. Its close control folds it into a pill.
+ */
+interface EverfurChatTopCard {
+    /** The small heading ("Her focus"). */
+    readonly kicker: string;
+    /** A source badge ("<your brand> results"). */
+    readonly badge?: string;
+    readonly title: string;
+    /** The finding: a bold lead and the rest of the sentence. */
+    readonly lead?: string;
+    readonly body?: string;
+    /** Your action ("See her Health Plan"). */
+    readonly action?: {
+        readonly label: string;
+        readonly onPress: () => void;
+    };
+    /** A question the card asks in this thread. */
+    readonly ask?: {
+        readonly label: string;
+        readonly prompt: string;
+    };
+    /** The close control's accessible name. Absent, the shared `Close`. */
+    readonly closeLabel?: string;
+    /** The pill's words while the card is closed (defaults to `kicker`). */
+    readonly pill?: string;
+    /** Draw the close glyph your way. */
+    readonly renderIcon?: (icon: 'close') => ReactNode;
+}
+/** The history bottom sheet (presentation `chatHistoryStyle: "sheet"`). */
+interface EverfurChatHistorySheet {
+    /** The sheet's small title ("Chats with Ask <your brand>"). Absent, Everfur's history heading. */
+    readonly title?: string;
+    /** Draw the icons your way. */
+    readonly renderIcon?: (icon: 'close' | 'chat' | 'edit') => ReactNode;
+}
 
 /**
  * The host's image picker for chat attachments. The SDK depends on no picker or camera module: open your own
@@ -30,6 +157,10 @@ interface EverfurChatAttachments {
     /** Images per message; default 1 (the app's composer), at most 5 (the server's cap). */
     readonly maxPerMessage?: number;
 }
+
+/** The host's own action for the two vet-care tiers, in place of Everfur's pill. */
+type RenderVetAction = (level: UrgencyDisplayLevel) => ReactNode;
+
 interface EverfurChatProps {
     readonly petRef?: PetRef;
     readonly conversationId?: ConversationId;
@@ -88,6 +219,12 @@ interface EverfurChatProps {
      * conversation. Pass `composerSeed` instead when the user should decide whether to send it.
      */
     readonly initialAsk?: string;
+    /**
+     * The identity of this `initialAsk`, when the same words can be asked again: your own id for each tap of an
+     * "Ask Everfur" pill or each push opened. A new key asks again even with the same words. Absent, the
+     * question's own words are the key, so the same question twice in a row is asked once.
+     */
+    readonly initialAskKey?: string | number;
     /**
      * Text to put in the composer on arrival. It is never sent for the user: they edit it, send it or clear
      * it. Only an empty composer is seeded, so nothing they typed is ever replaced.
@@ -149,6 +286,39 @@ interface EverfurChatProps {
      *   mount is about 15 pt short. Pass the hook's value from every render, never a copy taken at mount.
      */
     readonly keyboardVerticalOffset?: number;
+    /**
+     * The layout settings (Raph v3): the answer style, the history style, the top card, the composer style and
+     * placeholder, the history bar's place, the general banner, the send button, the follow-up count and the upload
+     * control. Each also comes from your console (render_hints.branding.presentation); a field you set here wins
+     * unless the console locks it. `attachments` counts as your explicit `chatComposerUpload: true`. The microphone
+     * setting (`chatComposerMic`) has no control on this surface. `topCard`, `answerCards` and `historySheet` are
+     * content only and never switch a layout on by themselves.
+     */
+    readonly presentation?: EverfurPresentationInput;
+    /**
+     * The focus card's content (drawn while `chatTopCard` resolves to `focus`). Absent, the card is built from the
+     * pet's Health Plan page focus; no page, no focus, a refused read or a page still loading draws no card.
+     */
+    readonly topCard?: EverfurChatTopCard;
+    /** Opens the pet's Health Plan (your tab or screen): the plan-built focus card's `See her Health Plan` button. */
+    readonly onOpenHealthPlan?: () => void;
+    /** The cards answer style's content (used while `chatAnswerStyle` resolves to `cards`). */
+    readonly answerCards?: EverfurChatAnswerCards;
+    /** The history sheet's title and icons (used while `chatHistoryStyle` resolves to `sheet`). */
+    readonly historySheet?: EverfurChatHistorySheet;
+    /** The history bar ("Chats" and "New chat"); `chatHistoryBar: "scroll"` puts it at the top of the thread. */
+    readonly historyBar?: EverfurChatHistoryBar;
+    /** Your own starter chips, in place of the built-in four. */
+    readonly starterPrompts?: readonly EverfurStarterPrompt[];
+    /** The empty thread's title and chip fills. */
+    readonly emptyState?: EverfurChatEmptyState;
+    /**
+     * Whether the surface draws its own header bar (the history control, the pet and its switcher, the vet entry).
+     * Default `true`. Pass `false` when your own screen already has a header over chat (the web surface's `header`):
+     * the thread, the urgency banner and the composer are unchanged. Without the header, the history bar
+     * (`historyBar`) is the way into past chats.
+     */
+    readonly header?: boolean;
 }
 /**
  * Entitlement-gated, four-state chat surface. Entitlement-OFF renders the CapabilityGate OffState;
@@ -156,4 +326,4 @@ interface EverfurChatProps {
  */
 declare function EverfurChat(props: EverfurChatProps): ReactNode;
 
-export { type AttachmentSource as A, EverfurChat as E, type RenderVetAction as R, type EverfurChatAttachments as a, type EverfurChatProps as b };
+export { type AttachmentSource as A, EverfurChat as E, type RenderVetAction as R, type EverfurChatAnswerCard as a, type EverfurChatAnswerCards as b, type EverfurChatAnswerContext as c, type EverfurChatAttachments as d, type EverfurChatEmptyState as e, type EverfurChatFollowUpAction as f, type EverfurChatHistoryBar as g, type EverfurChatHistorySheet as h, type EverfurChatProps as i, type EverfurChatTopCard as j };

package/dist/{DepthViews-CCz4ig0u.d.ts → DepthViews.d-BdvFZgPs.d.cts}

@@ -1,6 +1,6 @@
 import { ReactNode } from 'react';
 import { StyleProp, ViewStyle } from 'react-native';
-import { f as RecordsScreenBaseProps } from './useRecordsDepth-hR94debv.js';
+import { c as RecordsScreenBaseProps } from './screenProps.d-CQ0qZJkr.cjs';
 
 interface EverfurRecordsDepthProps extends Pick<RecordsScreenBaseProps, 'petRef' | 'petName' | 'onNavigate' | 'onBack'> {
     readonly style?: StyleProp<ViewStyle>;

package/dist/{DepthViews-CaQUyCHK.d.ts → DepthViews.d-DIvxzLDf.d.ts}

@@ -1,5 +1,5 @@
 import { CSSProperties, ReactNode } from 'react';
-import { f as RecordsScreenBaseProps } from './useRecordsDepth-hR94debv.js';
+import { c as RecordsScreenBaseProps } from './screenProps.d-BVzRzowC.js';
 
 interface EverfurRecordsDepthProps extends Pick<RecordsScreenBaseProps, 'petRef' | 'petName' | 'onNavigate' | 'onBack'> {
     readonly style?: CSSProperties;

package/dist/{DepthViews-iGZi4_WK.d.cts → DepthViews.d-Dy0Zl-s-.d.ts}

@@ -1,6 +1,6 @@
 import { ReactNode } from 'react';
 import { StyleProp, ViewStyle } from 'react-native';
-import { f as RecordsScreenBaseProps } from './useRecordsDepth-DRrJntjt.cjs';
+import { c as RecordsScreenBaseProps } from './screenProps.d-BVzRzowC.js';
 
 interface EverfurRecordsDepthProps extends Pick<RecordsScreenBaseProps, 'petRef' | 'petName' | 'onNavigate' | 'onBack'> {
     readonly style?: StyleProp<ViewStyle>;

package/dist/{DepthViews-D3OiIK_x.d.cts → DepthViews.d-wLNkzk9f.d.cts}

@@ -1,5 +1,5 @@
 import { CSSProperties, ReactNode } from 'react';
-import { f as RecordsScreenBaseProps } from './useRecordsDepth-DRrJntjt.cjs';
+import { c as RecordsScreenBaseProps } from './screenProps.d-CQ0qZJkr.cjs';
 
 interface EverfurRecordsDepthProps extends Pick<RecordsScreenBaseProps, 'petRef' | 'petName' | 'onNavigate' | 'onBack'> {
     readonly style?: CSSProperties;

package/dist/{ErrorPolicyPort-10s3HJCt.d.cts → ErrorPolicyPort.d-68yrE3BE.d.ts}

@@ -1,4 +1,4 @@
-import { b as EverfurErrorCode, E as EverfurError } from './EverfurError-DeBqRpQV.cjs';
+import { b as EverfurErrorCode, E as EverfurError } from './EverfurError.d-8NHtlgzA.js';
 
 /**
  * Recovery policy. A host may narrow retry ceilings (e.g. a metered plan) but can never widen the SDK's

package/dist/{ErrorPolicyPort-C3nNSS_j.d.ts → ErrorPolicyPort.d-DirW9hgO.d.cts}

@@ -1,4 +1,4 @@
-import { b as EverfurErrorCode, E as EverfurError } from './EverfurError-DeBqRpQV.js';
+import { b as EverfurErrorCode, E as EverfurError } from './EverfurError.d-8NHtlgzA.cjs';
 
 /**
  * Recovery policy. A host may narrow retry ceilings (e.g. a metered plan) but can never widen the SDK's

package/dist/{EverfurError-DeBqRpQV.d.cts → EverfurError.d-8NHtlgzA.d.cts}

@@ -150,6 +150,16 @@ interface EverfurError {
     /** SAFE localizable copy resolved from `code` via `userFacingError` (never the raw wireMessage). */
     readonly displayMessage: string;
 }
+/**
+ * The backend's `reason_code` on the 409 a write gets when the session belongs to a member whose Everfur account is
+ * linked to the partner read-only. The wire code is `ConflictException`, which folds to `conflict`, whose sentence
+ * ("That is already running...") is wrong here, and a retry never succeeds. The code stays `conflict` (an
+ * `accessDenied` would read as a consent or plan gate to the records repository), the copy becomes the existing
+ * access line, and the error is never retryable. See `isLinkedAccountReadOnly`.
+ */
+declare const LINKED_ACCOUNT_READ_ONLY = "linked_account_read_only";
+/** True when a write was refused because the member's Everfur account is linked to this partner read-only. */
+declare function isLinkedAccountReadOnly(error: Pick<EverfurError, 'code' | 'reasonCode'> | null | undefined): boolean;
 /**
  * The ONLY function the UI may call to render an error. Returns SAFE, code-derived copy; it never returns
  * the untrusted `wireMessage`. Total over the taxonomy (an unmapped code cannot occur at the type level).
@@ -180,4 +190,4 @@ interface MakeEverfurErrorOptions {
 }
 declare function makeEverfurError(code: EverfurErrorCode, opts?: MakeEverfurErrorOptions): EverfurError;
 
-export { AUTO_RETRYABLE_CODES as A, BACKOFF_BASE_MS as B, type EverfurError as E, MAX_RETRY_ATTEMPTS as M, RETRYABLE_CONTRACT_CODES as R, type EverfurErrorCategory as a, type EverfurErrorCode as b, categoryFor as c, BACKOFF_CAP_MS as d, EVERFUR_ERROR_CATEGORIES as e, EVERFUR_ERROR_CODES as f, type MakeEverfurErrorOptions as g, backoffDelayMs as h, isRetryableCode as i, canRecreateOnNotFound as j, fromHttpStatus as k, fromWire as l, isAutoRetryable as m, makeEverfurError as n, shouldRetry as s, userFacingError as u };
+export { AUTO_RETRYABLE_CODES as A, BACKOFF_BASE_MS as B, type EverfurError as E, LINKED_ACCOUNT_READ_ONLY as L, MAX_RETRY_ATTEMPTS as M, RETRYABLE_CONTRACT_CODES as R, type EverfurErrorCategory as a, type EverfurErrorCode as b, categoryFor as c, BACKOFF_CAP_MS as d, EVERFUR_ERROR_CATEGORIES as e, EVERFUR_ERROR_CODES as f, type MakeEverfurErrorOptions as g, backoffDelayMs as h, isRetryableCode as i, canRecreateOnNotFound as j, fromHttpStatus as k, fromWire as l, isAutoRetryable as m, isLinkedAccountReadOnly as n, makeEverfurError as o, shouldRetry as s, userFacingError as u };

package/dist/{EverfurError-DeBqRpQV.d.ts → EverfurError.d-8NHtlgzA.d.ts}

@@ -150,6 +150,16 @@ interface EverfurError {
     /** SAFE localizable copy resolved from `code` via `userFacingError` (never the raw wireMessage). */
     readonly displayMessage: string;
 }
+/**
+ * The backend's `reason_code` on the 409 a write gets when the session belongs to a member whose Everfur account is
+ * linked to the partner read-only. The wire code is `ConflictException`, which folds to `conflict`, whose sentence
+ * ("That is already running...") is wrong here, and a retry never succeeds. The code stays `conflict` (an
+ * `accessDenied` would read as a consent or plan gate to the records repository), the copy becomes the existing
+ * access line, and the error is never retryable. See `isLinkedAccountReadOnly`.
+ */
+declare const LINKED_ACCOUNT_READ_ONLY = "linked_account_read_only";
+/** True when a write was refused because the member's Everfur account is linked to this partner read-only. */
+declare function isLinkedAccountReadOnly(error: Pick<EverfurError, 'code' | 'reasonCode'> | null | undefined): boolean;
 /**
  * The ONLY function the UI may call to render an error. Returns SAFE, code-derived copy; it never returns
  * the untrusted `wireMessage`. Total over the taxonomy (an unmapped code cannot occur at the type level).
@@ -180,4 +190,4 @@ interface MakeEverfurErrorOptions {
 }
 declare function makeEverfurError(code: EverfurErrorCode, opts?: MakeEverfurErrorOptions): EverfurError;
 
-export { AUTO_RETRYABLE_CODES as A, BACKOFF_BASE_MS as B, type EverfurError as E, MAX_RETRY_ATTEMPTS as M, RETRYABLE_CONTRACT_CODES as R, type EverfurErrorCategory as a, type EverfurErrorCode as b, categoryFor as c, BACKOFF_CAP_MS as d, EVERFUR_ERROR_CATEGORIES as e, EVERFUR_ERROR_CODES as f, type MakeEverfurErrorOptions as g, backoffDelayMs as h, isRetryableCode as i, canRecreateOnNotFound as j, fromHttpStatus as k, fromWire as l, isAutoRetryable as m, makeEverfurError as n, shouldRetry as s, userFacingError as u };
+export { AUTO_RETRYABLE_CODES as A, BACKOFF_BASE_MS as B, type EverfurError as E, LINKED_ACCOUNT_READ_ONLY as L, MAX_RETRY_ATTEMPTS as M, RETRYABLE_CONTRACT_CODES as R, type EverfurErrorCategory as a, type EverfurErrorCode as b, categoryFor as c, BACKOFF_CAP_MS as d, EVERFUR_ERROR_CATEGORIES as e, EVERFUR_ERROR_CODES as f, type MakeEverfurErrorOptions as g, backoffDelayMs as h, isRetryableCode as i, canRecreateOnNotFound as j, fromHttpStatus as k, fromWire as l, isAutoRetryable as m, isLinkedAccountReadOnly as n, makeEverfurError as o, shouldRetry as s, userFacingError as u };

package/dist/{EverfurResult-ClPTS0P2.d.ts → EverfurResult.d-BFH-3s6E.d.cts}

@@ -1,4 +1,4 @@
-import { E as EverfurError } from './EverfurError-DeBqRpQV.js';
+import { E as EverfurError } from './EverfurError.d-8NHtlgzA.cjs';
 
 /**
  * The settle type. An async public operation returns this instead of throwing for an EXPECTED failure.

package/dist/{EverfurResult-COlXj1wq.d.cts → EverfurResult.d-D_-254ZY.d.ts}

@@ -1,4 +1,4 @@
-import { E as EverfurError } from './EverfurError-DeBqRpQV.cjs';
+import { E as EverfurError } from './EverfurError.d-8NHtlgzA.js';
 
 /**
  * The settle type. An async public operation returns this instead of throwing for an EXPECTED failure.

package/dist/{IntakeMedia-BH0fYDT2.d.cts → IntakeMedia.d-4a89XrP7.d.ts}

@@ -1,5 +1,5 @@
 import { ReactNode } from 'react';
-import { T as TelevetConsult } from './televetGlobal-C5dTUACe.cjs';
+import { T as TelevetConsult } from './televetGlobal.d-CC-DrqkQ.js';
 
 /** The calendar entry a booked visit asks the host to write. */
 interface TelevetCalendarEvent {

package/dist/{IntakeMedia-B-_vA9ZB.d.cts → IntakeMedia.d-DGxrhgIW.d.ts}

@@ -1,5 +1,5 @@
 import { ReactNode } from 'react';
-import { T as TelevetConsult } from './televetGlobal-C5dTUACe.cjs';
+import { T as TelevetConsult } from './televetGlobal.d-CC-DrqkQ.js';
 
 /**
  * The pet's own clinic, when the HOST holds it.

package/dist/{IntakeMedia-CIoTXAWs.d.ts → IntakeMedia.d-DUPR4lVM.d.cts}

@@ -1,5 +1,5 @@
 import { ReactNode } from 'react';
-import { T as TelevetConsult } from './televetGlobal-CnjrfhT4.js';
+import { T as TelevetConsult } from './televetGlobal.d-CKwDCbmN.cjs';
 
 /**
  * The pet's own clinic, when the HOST holds it.

package/dist/{IntakeMedia-Bavl7E4Z.d.ts → IntakeMedia.d-JJCUvQu7.d.cts}

@@ -1,5 +1,5 @@
 import { ReactNode } from 'react';
-import { T as TelevetConsult } from './televetGlobal-CnjrfhT4.js';
+import { T as TelevetConsult } from './televetGlobal.d-CKwDCbmN.cjs';
 
 /** The calendar entry a booked visit asks the host to write. */
 interface TelevetCalendarEvent {

package/dist/LifecyclePort.d-Cr1p33a7.d.cts

@@ -0,0 +1,23 @@
+/**
+ * The host's lifecycle and connectivity signals. Each subscribe returns its own unsubscribe, which the SDK
+ * calls on unmount; a listener that throws is contained by the caller, never by the host.
+ */
+interface LifecyclePort {
+    /**
+     * The host came back to the foreground. Only the real blur-to-focus edge, please: a platform that flips
+     * through an inactive state constantly (iOS control centre, a call banner) would otherwise turn a
+     * notification-shade pull into a request.
+     */
+    onForeground(listener: () => void): () => void;
+    /** Connectivity returned. Omit it and a deferred refresh waits for the next foreground instead. */
+    onOnline?(listener: () => void): () => void;
+    /**
+     * Something told the host THIS member's thread changed: the push that carried the message. Announced
+     * triggers are never coalesced, because that is the one case where the reader is waiting on new content.
+     */
+    onAnnounced?(listener: () => void): () => void;
+    /** Is the host unambiguously offline? Absent reads as online, which is exactly today's behaviour. */
+    isOffline?(): boolean;
+}
+
+export type { LifecyclePort as L };

package/dist/LifecyclePort.d-Cr1p33a7.d.ts

@@ -0,0 +1,23 @@
+/**
+ * The host's lifecycle and connectivity signals. Each subscribe returns its own unsubscribe, which the SDK
+ * calls on unmount; a listener that throws is contained by the caller, never by the host.
+ */
+interface LifecyclePort {
+    /**
+     * The host came back to the foreground. Only the real blur-to-focus edge, please: a platform that flips
+     * through an inactive state constantly (iOS control centre, a call banner) would otherwise turn a
+     * notification-shade pull into a request.
+     */
+    onForeground(listener: () => void): () => void;
+    /** Connectivity returned. Omit it and a deferred refresh waits for the next foreground instead. */
+    onOnline?(listener: () => void): () => void;
+    /**
+     * Something told the host THIS member's thread changed: the push that carried the message. Announced
+     * triggers are never coalesced, because that is the one case where the reader is waiting on new content.
+     */
+    onAnnounced?(listener: () => void): () => void;
+    /** Is the host unambiguously offline? Absent reads as online, which is exactly today's behaviour. */
+    isOffline?(): boolean;
+}
+
+export type { LifecyclePort as L };

package/dist/{PhotoController-vzY5bfY_.d.ts → PhotoController.d-BzCJOE7e.d.cts}

@@ -1,5 +1,5 @@
-import { J as JobId } from './ids-B2GAAifq.js';
-import { I as Interpretation } from './projection-CeIUsbSk.js';
+import { J as JobId } from './ids.d-B2GAAifq.cjs';
+import { I as Interpretation } from './projection.d-CeIUsbSk.cjs';
 
 /** Deterministic + semantic precheck reason codes (ground truth `everfur_common/schemas/analysis.py`). */
 type PrecheckReasonCode = 'blurry' | 'too_dark' | 'too_bright' | 'too_far' | 'too_close' | 'bad_framing' | 'low_quality' | 'wrong_modality' | 'wrong_species' | 'not_an_animal' | string;

package/dist/{PhotoController-3l7MT9jA.d.cts → PhotoController.d-D0XiUUOl.d.ts}

@@ -1,5 +1,5 @@
-import { J as JobId } from './ids-B2GAAifq.cjs';
-import { I as Interpretation } from './projection-CeIUsbSk.cjs';
+import { J as JobId } from './ids.d-B2GAAifq.js';
+import { I as Interpretation } from './projection.d-CeIUsbSk.js';
 
 /** Deterministic + semantic precheck reason codes (ground truth `everfur_common/schemas/analysis.py`). */
 type PrecheckReasonCode = 'blurry' | 'too_dark' | 'too_bright' | 'too_far' | 'too_close' | 'bad_framing' | 'low_quality' | 'wrong_modality' | 'wrong_species' | 'not_an_animal' | string;

package/dist/RecordsPage.d-9Ank15PT.d.ts

@@ -0,0 +1,93 @@
+import { CSSProperties, ReactNode } from 'react';
+import { R as RecordsClinicController, C as CaptureRecordsSignature } from './clinicRequestProps.d-CjsMg_OD.js';
+import { R as RecordsController } from './useRecords.d-DWk61a4c.js';
+import { c as RecordForwardItem } from './models.d-DOwnr8fi.js';
+import { c as RecordsScreenBaseProps } from './screenProps.d-BVzRzowC.js';
+import { E as EverfurRecordsSheet } from './sheetSeam.d-B09jf4YC.js';
+
+interface EverfurRecordsPageProps extends RecordsScreenBaseProps {
+    readonly controller?: RecordsController;
+    /** Host/test seam over the clinic controller the `Request records` sheet uses. */
+    readonly clinicController?: RecordsClinicController;
+    readonly consentVersion?: string;
+    /** Your consent text, shown above `Allow` on the consent gate; pass it with its `consentVersion`. */
+    readonly consentText?: string;
+    /** The owner's name the clinic authorization is signed with (the owner can correct it before signing). */
+    readonly ownerName?: string;
+    /** A host signature component for the clinic authorization, instead of the built-in canvas. */
+    readonly onCaptureSignature?: CaptureRecordsSignature;
+    /**
+     * The heading level this page's title claims. Defaults to 2.
+     *
+     * THIS PAGE AND THE BOOKING FLOW USED TO DISAGREE, and that is why the prop exists. The page hardcoded
+     * `<h2>` and the televet booking chrome hardcoded `<h1>`, so a partner mounting both in one document got two
+     * competing top levels. A drop-in widget does not own the host page's `<h1>`: the shared default is 2 and a
+     * host whose page IS this surface passes 1. `src/web/headingLevel.ts` carries the full argument.
+     */
+    readonly headingLevel?: number;
+    readonly style?: CSSProperties;
+    readonly className?: string;
+    readonly renderPending?: () => ReactNode;
+    /**
+     * Show the record's upcoming care (rechecks, vaccinations due) as its own card on the page, under the header.
+     * Default `false`: upcoming care shows only inside the full record (`Visits & records`), as before.
+     */
+    readonly upcomingCare?: boolean;
+    /**
+     * Only with `upcomingCare`: your own control at the end of each upcoming-care row (for example your vet entry).
+     * Called once per row with that item; return null for a row without one. Absent, the rows have no action.
+     */
+    readonly renderUpcomingCareAction?: (item: RecordForwardItem) => ReactNode;
+    /**
+     * Draw the Records & history tiles under the header: `Labs & bloodwork` (opens the pet's lab markers on the page,
+     * drawn only while there are markers), `Screenings` (only with `onOpenScreenings`), `Visits & records` and
+     * `Timeline`. Default `false`: the header's two links, as before.
+     */
+    readonly historyTiles?: boolean;
+    /**
+     * Where the `Screenings` tile goes. The sheet always draws that tile, as the Everfur web app does: "All clear" or
+     * "N to review" over the pet's screening results (its lab markers with a result word), or "No screenings yet";
+     * absent, it opens the screening's marker on the page, and with none on file it is not a button. With
+     * `historyTiles`, absent means no tile.
+     */
+    readonly onOpenScreenings?: () => void;
+    /**
+     * The page's look. By default (absent) it is the records sheet, our web app's health tab: the pet's vitals, upcoming
+     * care, the Records & History tiles, weight, medications, the history timeline and the ways to add records, or its
+     * no-records screen.
+     * The page loads it from `@everfur/sdk/web/records-sheet` (its own subpath) while showing its loading state; pass
+     * `recordsSheet(options)` from that subpath to set options, or `false` for the classic page (which then downloads
+     * none of the sheet). The same flows sit behind every look (clinic request with its consent and signature, upload,
+     * the full record). With the sheet, `upcomingCare` and `historyTiles` are implied and `renderUpcomingCareAction`
+     * fills the overdue row.
+     */
+    readonly sheet?: EverfurRecordsSheet | false;
+    /** With the sheet: the unit a weight shows in first, `'lb'` (the default) or `'kg'`. */
+    readonly weightUnit?: 'lb' | 'kg';
+    /** With the sheet: opens the pet's Health Plan (your tab or screen), the top risk line's button. */
+    readonly onOpenPlan?: () => void;
+    /**
+     * Your own entry to a clinic request, run by "Request from her clinic" (the sheet) and `Request records` (the
+     * classic page) in place of the page's clinic flow (its picker, consent and signature, the default). Use it when
+     * your page already asks which clinic and confirms it was sent. Return a promise that settles once the request
+     * is sent and the page re-reads the member's requests, so its "on the way" line shows it. While a clinic request
+     * is out, the sheet's "Request from her clinic" only says it was requested there and calls neither.
+     */
+    readonly onRequestFromClinic?: () => void | Promise<unknown>;
+    /**
+     * With the sheet: the member told you the pet has no vet yet (for example in your intro). The no-records title
+     * then reads "When Georgia has a vet, start here."; the ways to add records stay as they are.
+     */
+    readonly noVet?: boolean;
+}
+/**
+ * The records surface as a PAGE, mirroring the consumer web app: the default web records surface.
+ *
+ * Complete on its own: request records from a clinic (consent and signature), upload records the
+ * member already has, every request with its status and documents, and the full record with its
+ * vaccinations, all without leaving your page. Pass `onNavigate` only if you route those screens
+ * yourself. `EverfurRecords` (the flow) is the React Native-shaped stack, kept for existing embeds.
+ */
+declare function EverfurRecordsPage(props: EverfurRecordsPageProps): ReactNode;
+
+export { type EverfurRecordsPageProps as E, EverfurRecordsPage as a };

package/dist/RecordsPage.d-DMKU0IKc.d.cts

@@ -0,0 +1,93 @@
+import { CSSProperties, ReactNode } from 'react';
+import { R as RecordsClinicController, C as CaptureRecordsSignature } from './clinicRequestProps.d-1dCtouGA.cjs';
+import { R as RecordsController } from './useRecords.d-BYNX01El.cjs';
+import { c as RecordForwardItem } from './models.d-BSqvbTE1.cjs';
+import { c as RecordsScreenBaseProps } from './screenProps.d-CQ0qZJkr.cjs';
+import { E as EverfurRecordsSheet } from './sheetSeam.d-BBuEIVsa.cjs';
+
+interface EverfurRecordsPageProps extends RecordsScreenBaseProps {
+    readonly controller?: RecordsController;
+    /** Host/test seam over the clinic controller the `Request records` sheet uses. */
+    readonly clinicController?: RecordsClinicController;
+    readonly consentVersion?: string;
+    /** Your consent text, shown above `Allow` on the consent gate; pass it with its `consentVersion`. */
+    readonly consentText?: string;
+    /** The owner's name the clinic authorization is signed with (the owner can correct it before signing). */
+    readonly ownerName?: string;
+    /** A host signature component for the clinic authorization, instead of the built-in canvas. */
+    readonly onCaptureSignature?: CaptureRecordsSignature;
+    /**
+     * The heading level this page's title claims. Defaults to 2.
+     *
+     * THIS PAGE AND THE BOOKING FLOW USED TO DISAGREE, and that is why the prop exists. The page hardcoded
+     * `<h2>` and the televet booking chrome hardcoded `<h1>`, so a partner mounting both in one document got two
+     * competing top levels. A drop-in widget does not own the host page's `<h1>`: the shared default is 2 and a
+     * host whose page IS this surface passes 1. `src/web/headingLevel.ts` carries the full argument.
+     */
+    readonly headingLevel?: number;
+    readonly style?: CSSProperties;
+    readonly className?: string;
+    readonly renderPending?: () => ReactNode;
+    /**
+     * Show the record's upcoming care (rechecks, vaccinations due) as its own card on the page, under the header.
+     * Default `false`: upcoming care shows only inside the full record (`Visits & records`), as before.
+     */
+    readonly upcomingCare?: boolean;
+    /**
+     * Only with `upcomingCare`: your own control at the end of each upcoming-care row (for example your vet entry).
+     * Called once per row with that item; return null for a row without one. Absent, the rows have no action.
+     */
+    readonly renderUpcomingCareAction?: (item: RecordForwardItem) => ReactNode;
+    /**
+     * Draw the Records & history tiles under the header: `Labs & bloodwork` (opens the pet's lab markers on the page,
+     * drawn only while there are markers), `Screenings` (only with `onOpenScreenings`), `Visits & records` and
+     * `Timeline`. Default `false`: the header's two links, as before.
+     */
+    readonly historyTiles?: boolean;
+    /**
+     * Where the `Screenings` tile goes. The sheet always draws that tile, as the Everfur web app does: "All clear" or
+     * "N to review" over the pet's screening results (its lab markers with a result word), or "No screenings yet";
+     * absent, it opens the screening's marker on the page, and with none on file it is not a button. With
+     * `historyTiles`, absent means no tile.
+     */
+    readonly onOpenScreenings?: () => void;
+    /**
+     * The page's look. By default (absent) it is the records sheet, our web app's health tab: the pet's vitals, upcoming
+     * care, the Records & History tiles, weight, medications, the history timeline and the ways to add records, or its
+     * no-records screen.
+     * The page loads it from `@everfur/sdk/web/records-sheet` (its own subpath) while showing its loading state; pass
+     * `recordsSheet(options)` from that subpath to set options, or `false` for the classic page (which then downloads
+     * none of the sheet). The same flows sit behind every look (clinic request with its consent and signature, upload,
+     * the full record). With the sheet, `upcomingCare` and `historyTiles` are implied and `renderUpcomingCareAction`
+     * fills the overdue row.
+     */
+    readonly sheet?: EverfurRecordsSheet | false;
+    /** With the sheet: the unit a weight shows in first, `'lb'` (the default) or `'kg'`. */
+    readonly weightUnit?: 'lb' | 'kg';
+    /** With the sheet: opens the pet's Health Plan (your tab or screen), the top risk line's button. */
+    readonly onOpenPlan?: () => void;
+    /**
+     * Your own entry to a clinic request, run by "Request from her clinic" (the sheet) and `Request records` (the
+     * classic page) in place of the page's clinic flow (its picker, consent and signature, the default). Use it when
+     * your page already asks which clinic and confirms it was sent. Return a promise that settles once the request
+     * is sent and the page re-reads the member's requests, so its "on the way" line shows it. While a clinic request
+     * is out, the sheet's "Request from her clinic" only says it was requested there and calls neither.
+     */
+    readonly onRequestFromClinic?: () => void | Promise<unknown>;
+    /**
+     * With the sheet: the member told you the pet has no vet yet (for example in your intro). The no-records title
+     * then reads "When Georgia has a vet, start here."; the ways to add records stay as they are.
+     */
+    readonly noVet?: boolean;
+}
+/**
+ * The records surface as a PAGE, mirroring the consumer web app: the default web records surface.
+ *
+ * Complete on its own: request records from a clinic (consent and signature), upload records the
+ * member already has, every request with its status and documents, and the full record with its
+ * vaccinations, all without leaving your page. Pass `onNavigate` only if you route those screens
+ * yourself. `EverfurRecords` (the flow) is the React Native-shaped stack, kept for existing embeds.
+ */
+declare function EverfurRecordsPage(props: EverfurRecordsPageProps): ReactNode;
+
+export { type EverfurRecordsPageProps as E, EverfurRecordsPage as a };