@everfur/sdk 0.13.0 → 0.14.0

package/CHANGELOG.md

@@ -10,6 +10,132 @@ changes that has not been earned by any production integration yet.
 
 ## [Unreleased]
 
+## [0.14.0] - 2026-10-22
+
+### Added
+
+- **Three tabs with a first-open intro (web).** New `EverfurTabs` (`@everfur/sdk/web`): Ask, Health Plan and Records
+  as WAI-ARIA tabs over panes that stay mounted, with `EverfurChat`, `EverfurHealthPlan` and `EverfurRecordsPage`
+  inside (their own props pass through `chat`, `plan` and `records`). The host says how the member got here with
+  `opened`: a plain open lands on Health Plan (Ask when the pet has no plan, whose tab then hides), a link opens the
+  tab it names and can ask a question. On a phone-narrow page the first plain open plays the intro over Ask once per
+  member: the tabs, the records ask with the clinic search, the consent and the request, and Sent. "Seen" lives on the
+  account (`GET` / `PUT /widget/v1/me/intro`), this device keeps a copy once it closes, and a failed read never plays
+  it. The intro is its own lazily loaded entry, `@everfur/sdk/web/intro`. Also exported: `useEverfurTabs` and the
+  `tabsRef` prop (`open`, `ask`, `requestRecords`), `EVERFUR_TABS_COPY`, and the `everfur:records-requested` /
+  `everfur:records-landed` window events with `onRecordsRequested` / `onRecordsLanded` (the window's requested event
+  leaves out `clinicName`, which any script on the page would hear; the callback carries it).
+- **Ask home (web).** The compact composer sits 14px in from each side and 10px off the bar's foot, as Raph's
+  `.ph-askbar`; the Chats count is drawn only when there is at least one chat.
+- **Three tabs with a first-open intro (React Native).** New subpath `@everfur/sdk/tabs`, the web shell's twin:
+  `EverfurTabs` over `EverfurChat`, `EverfurHealthPlan` and `EverfurRecords` (reached through their own subpaths, not
+  bundled), the same `opened` rule, panes that stay mounted, `tabsRef` / `useEverfurTabs` (`open`, `ask`,
+  `requestRecords`), `onTabChange`, `onRecordsRequested`, `onRecordsLanded` and `onToast`. The intro plays once per
+  member on the first plain open on a phone-sized window (`intro.maxWidth`, default 600), in a modal sheet whose
+  title takes the screen reader's focus; reduced motion fades it over 150ms. "Seen" is the same account read and
+  device copy as the web, and a failed read never plays it. Records' "Request from her clinic" opens the intro's
+  records sheet (`requestRecords`), the SDK consent screen kept between Request and Sent. Also exported:
+  `EverfurIntro`, `EverfurRecordsLandedBanner`, `useEverfurIntroSeen`, `EVERFUR_TABS_COPY`, `EVERFUR_INTRO_COPY` and
+  the intro's pure text helpers. The React Native compact Ask composer takes Raph's `.ph-askbar` insets (10, 14, 10).
+- **Ask (React Native).** `EverfurChat` takes `header={false}`, the web prop's twin, for a screen that already has a
+  header over chat (the tab shell's host passes it). Inside `EverfurTabs` the chat takes no status-bar inset of its own.
+  Fixed: a staggered fade (the starter chips) could stay invisible when the OS reduced-motion setting arrived after
+  mount; it now comes to rest.
+- **Ask home inside the tabs (React Native).** Inside `EverfurTabs` the chat draws Raph's round 5 Ask home from
+  generated rules (`scripts/gen-ask-home-rn.mjs`): his Chats row, focus card, and centred start with a balanced title
+  (his `16ch` measure, measured by layout) and chips. There, presentation `safetyDisclaimerPlacement: "answer_footer"`
+  moves the safety footnote to the foot of the thread, as on the web. The look rides in the tabs entry; a standalone
+  `EverfurChat` keeps its look and its size. New `EverfurPoweredBy` and `useHostPoweredBy` (`@everfur/sdk/chat`), the
+  web's twins: a host that shows "powered by everfur" in its own header wraps that lockup, and the chat leaves out its
+  own line. The tab shell passes the records sheet `onRequestFromClinic({ petRef })` and `noVet`.
+
+- **The texting ask, in chat and as a pop-up (web and React Native).** `EverfurChat` now asks a member to turn on
+  texting by itself: after a completed answer (never a failed or stopped turn, a check-in or an urgent answer),
+  with nothing streaming, one Everfur line in the answer look with "Turn on SMS
+  Chat" / "Not now". Accepting turns the composer into the opt-in's number, consent and code steps, and a verified
+  number shows a closing line. New presentation field `chat_texting_ask` (`chatTextingAsk`, boolean, default `true`)
+  turns it off. New `EverfurTextingPrompt` (`@everfur/sdk/web/texting`, `@everfur/sdk/texting`) is the same ask as a
+  sheet for app open; whether to mount it is the partner's call. Both share one schedule, kept per member in the
+  provider's `storage`: at most three asks two days apart, never again once the member has an identity, and at most
+  one ask per session. Unreadable storage shows nothing, so a React Native host with no `storage` is never asked.
+  Also exported: `useTextingAsk`, `resolveTextingAskDue`, `textingAskThreadReady`, `isTextingAskEligible` and the
+  `TEXTING_ASK_*` constants. On the web the chat loads `@everfur/sdk/web/texting` lazily, only when the ask can show.
+  The hosted frame has no texting, so its chat never asks.
+- **`EverfurTextingPrompt` is a centred card, and closing it hands the ask to the chat.** The pop-up now sits in the
+  middle of the screen with every corner rounded (it fades in on React Native), clear of a host's bottom navigation,
+  instead of a sheet from the bottom edge. Closing it ("Not now", Escape, the back gesture or a press outside) still
+  counts one ask, and the chat then shows its line once after the member's next completed answer in that session, as
+  the same ask. The chat's "Not now" restarts the two days without counting another ask.
+
+- **Health Plan, Raph's round 5 (web and React Native).** The vet is one setting, drawn from the plan page's byline.
+  A plan that is missing records shows her three blanks card with its records facts, then "Asked" once the records
+  request is out and a one-time flash when they land. The tabs share two plan signals across entries
+  (`setHealthPlanNoVet` / `onHealthPlanNoVet`, `notifyHealthPlanRecordsLanded` / `onHealthPlanRecordsLanded`), so the
+  intro's no-vet choice and a landed request reach the plan. A pick whose pet has no weight yet keeps an empty dose
+  blank from the page's new `doseLabel`. The Manage sheet links to her orders. React Native draws Raph's plan icons
+  from a generated set (`RAPH_RN_PLAN_ICONS`), which the shop reuses.
+- **Records follow our health tab (web and React Native).** On the web the records sheet follows our web app's health
+  tab at every width, phone and tablet tiers included: none, requested, processing and full, with the care rows, the
+  timeline count, the weight model and the sample peek. On React Native the sheet draws as our mobile app's Health
+  tab (`HubSections`): the pet hero and stage line, the request prompt and on-the-way tracker, weight, upcoming care,
+  record tiles and add-records card. A partial read failure shows a retry card, and the labs tile reads "--" while it
+  loads or fails. `RecordForwardItem` gains `careItemKey` and `dueDateSource`.
+- **One first-open pop-up at a time.** While the tabs read "seen" and while the intro is up, `EverfurTextingPrompt`
+  waits; it may show after the intro closes.
+- **`onRequestFromClinic` and `noVet` on the records surfaces.** New `EverfurRecordsPage` props (web) and
+  `EverfurRecordsSheetOptions` fields (React Native): `onRequestFromClinic` runs your own clinic request in place of
+  the records flow's clinic picker (on React Native it is told `{ petRef }`; a rejected promise is not reported), and
+  `noVet` gives the no-records title its no-vet words. `EverfurRecordsSheetOptions.active` (React Native, default
+  true) is for a host that keeps the sheet mounted while hidden: while false it takes no Android back. The tab shells
+  pass all three.
+
+### Changed
+
+- The React Native records sheet's `copy` option is deprecated and ignored: its one field, `undatedPill`, is no longer
+  drawn.
+- `HealthPlanFocusCopy` (web and React Native) gained required members for round 5 (`builtWith`, `fromVet`,
+  `callAVet`, `callYourVet`, `saveForCheckup`, `savedForCheckup`, `recordsLanded`, `noPick`, `signalsFit`,
+  `signalsValue`, `waitVetTips`, `blankEmpty` and the `blanks*` lines). A type-level change only for a host that
+  builds a whole `HealthPlanFocusCopy` object; a `Partial` override, as `copy` takes it, is unaffected.
+- Default-on looks: `EverfurRecordsPage` (web) draws the sheet as our web app's health tab, and `EverfurRecords`
+  (React Native) as our mobile app's Health tab, with no new prop; the compact `EverfurChat` composer takes Raph's
+  `.ph-askbar` insets on both hosts. `sheet={false}` keeps the classic records page.
+- The intro's "Upload a PDF or a photo instead" closes the intro and then runs the upload; inside the tabs with no
+  host upload it opens Records.
+- Health Plan sheets close on Escape one layer at a time and move focus to their title; pushed screens (cart,
+  orders, order, placed) focus their own section on open.
+- Bundle budgets: `@everfur/sdk/records` 145,900, `@everfur/sdk/health-plan` 72,200, `@everfur/sdk/shop` 79,800,
+  `@everfur/sdk/tabs` 47,200; web `index.js` 121,400, `web/records-sheet` 63,100, `web/health-plan` 69,800,
+  `web/intro` 33,500; `dist-cdn/records-frame.js` 257,300 bytes.
+
+### Fixed
+
+- The texting pop-up also waits while the host is still reading who is signed in or its pets (at most 5 seconds,
+  phone-sized pages only), and one that opened before the intro steps aside while the intro plays.
+- Records landing by any path, including `notifyHealthPlanRecordsLanded` from the host, clear the pet's no-vet state.
+- Health Plan styles (web) are kept under React StrictMode: nodes mounted after the simulated unmount were unstyled.
+- The intro (web) no longer mixes a `transition` shorthand with its longhands, which made React warn on close.
+- The tabs (web and React Native) no longer hold the first-open pop-up for ever: a failed plan read, a probe or intro
+  chunk that does not load, or reads that take more than 5 seconds let the intro go for that open. On the web, when
+  the intro's chunk does not load, Records' "Request from her clinic" runs the records page's own clinic flow.
+- No vet yet is set only when the member closes the intro from its no-vet frame, is kept per pet, and clears once a
+  clinic request is sent or her records are in.
+- The intro (web) gives focus back once it is down: to the tab it closed onto inside `EverfurTabs`, else to where it
+  was.
+- A Health Plan or records pane chunk that fails to download (web tabs) draws an empty pane instead of throwing up
+  the host's tree; while loading it is marked busy for assistive tech.
+- A hidden Records tab (React Native) no longer takes the Android back from the screen the member is on.
+- The records sheet (web and React Native) and the plan's three blanks catch their clock up when shown again and
+  hourly, instead of keeping the time of their first render.
+- The tabs' toast (web) is announced: one live region stays mounted and the toast's words are written into it.
+- A clinic picked again after Back in the intro reuses its idempotency key, so a send still on its way is not made
+  twice.
+- The plan and intro signals shared on `globalThis` are checked for their shape and replaced when another script left
+  something else under the key.
+- Health Plan: a vet-reviewed page whose backend sends no byline keeps 0.13.0's byline (web); a host passing
+  `recordsMissing` or `recordsBlanks` again reads no records, 0.13.0's rule (web and React Native); the vet's note
+  keeps a `kicker` from the wire for older hosts.
+
 ## [0.13.0] - 2026-10-21
 
 ### BREAKING

package/README.md

@@ -59,11 +59,11 @@ shipping the minter to a device. Import it from your server only.
 ### On the web
 
 Two ways, one wire contract, documented in
-[docs/partner-integration/13-WEB-INTEGRATION.md](https://sdk.everfur.com/v1/docs/index.html#sec-web):
+[docs/partner-integration/13-WEB-INTEGRATION.md](https://docs.everfur.com/web/):
 
 - **In-page**, for a page whose React tree you own: `import { EverfurProvider, EverfurChat } from
   '@everfur/sdk/web'` (peers: `react`, `react-dom`). The copy-paste shape is
-  [`examples/minimal-web.tsx`](https://sdk.everfur.com/v1/docs/index.html#web--1-in-page-everfur-sdk-web). Take the `/web` entry, not the package root: the
+  [`examples/minimal-web.tsx`](https://docs.everfur.com/web/#web--1-in-page-everfur-sdk-web). Take the `/web` entry, not the package root: the
   root is the React Native entry and imports `react-native` and `react-native-safe-area-context`, so in a
   browser project it fails to resolve them rather than rendering. The `/web` entries need `react`,
   `react/jsx-runtime` and `zod` and nothing native, which `npm run verify:pack` proves on every CI run by
@@ -71,7 +71,7 @@ Two ways, one wire contract, documented in
 - **Frame mode**, for a page you do not fully control (a storefront theme, a CMS page): one `<script
   src="https://sdk.everfur.com/v1/everfur.js">` puts the surface in an iframe on `sdk.everfur.com`, and
   the frame refuses to initialise on any page origin your tenant has not registered. The copy-paste shape
-  is [`examples/frame-embed.html`](https://sdk.everfur.com/v1/docs/index.html#web--the-snippet).
+  is [`examples/frame-embed.html`](https://docs.everfur.com/web/#web--the-snippet).
 
 Chat and records are the web surfaces (records on its own subpath and its own frame document, available
 when Everfur enables records for your account); photo and video remain React Native for now. Vet visits (available when Everfur enables them for your
@@ -83,7 +83,7 @@ and the call (`@everfur/sdk/televet/call`, `@everfur/sdk/web/televet/call`) are
 are loaded on demand, so a page where nobody opens a visit downloads neither and a page where nobody joins takes
 no WebRTC dependency; on React Native both are static imports in the same bundle (the WebRTC stack is the native
 module your app registers with `registerEverfurDaily`).
-[docs/partner-integration/16-TELEVET-VISITS.md](https://sdk.everfur.com/v1/docs/index.html#sec-televet).
+[docs/partner-integration/16-TELEVET-VISITS.md](https://docs.everfur.com/vet-visits/).
 
 ## Quickstart
 
@@ -197,16 +197,17 @@ off-state, never a blank region.
 | --- | --- |
 | `@everfur/sdk` | `EverfurProvider`, `CapabilityGate`, `EverfurChat`, `useEverfurChat`, `CapabilityName`, error/result types, branded id helpers (`petRef`, `userRef`, `conversationId`) |
 | `@everfur/sdk/records` | `EverfurRecords` (the Everfur app's records flow), the named screens (`EverfurRecordsUpload`, `EverfurRecordsRequests`, `EverfurRecordsRequest`, `EverfurRecordDetail`, ...), `EverfurClinicRequest`, `EverfurClinicRequestBatch`, `SignaturePad`, records hooks + types |
-| `@everfur/sdk/records/depth`, `@everfur/sdk/web/records/depth` | record depth (the timeline, the withheld record sections, per-document contributions) on their own entries, dark until Everfur enables it per deployment; see [chapter 9](https://sdk.everfur.com/v1/docs/index.html#records--record-depth-behind-a-separate-switch) |
+| `@everfur/sdk/records/depth`, `@everfur/sdk/web/records/depth` | record depth (the timeline, the withheld record sections, per-document contributions) on their own entries, dark until Everfur enables it per deployment; see [chapter 9](https://docs.everfur.com/records/#records--record-depth-behind-a-separate-switch) |
 | `@everfur/sdk/video` | gait / live-scan surface |
 | `@everfur/sdk/photo` | photo checkup surface |
 | `@everfur/sdk/animations` | server-driven pet-state media surface |
-| `@everfur/sdk/web` | the browser entry: `EverfurProvider`, `CapabilityGate`, `EverfurChat`, `useEverfurChat`, the theme hook, rendered with `react-dom`; withheld from React Native bundles the way `./server` is |
-| `@everfur/sdk/web/records` | records for a browser host: `EverfurRecordsPage` (the Everfur web app's records page, complete on its own: request from a clinic, upload, request status, the full record with vaccinations, all inside your page), the named screens, `EverfurRecords` (the React Native-shaped flow), `useEverfurRecords`, `createWebRecordsUploadTransport`, `fileToHandle`; its own entry, withheld from React Native like `./web`; available when Everfur enables records for the account. Frame mode serves it with `surface: 'records'` (see [chapter 13](https://sdk.everfur.com/v1/docs/index.html#web--2-frame-mode-the-loader-and-the-frame)) |
-| `@everfur/sdk/web/records-sheet` | `recordsSheet()`: the v3 records sheet and its lab result screen, `EverfurRecordsPage`'s default look (loaded on first mount; `sheet={false}` keeps the classic page, which downloads none of it), or built with options and passed to its `sheet` prop; withheld from React Native like `./web`; see [chapter 13](https://sdk.everfur.com/v1/docs/index.html#web--records-everfur-sdk-web-records) |
+| `@everfur/sdk/web` | the browser entry: `EverfurProvider`, `CapabilityGate`, `EverfurChat`, `useEverfurChat`, `EverfurTabs` (Ask, Health Plan and Records in one shell, with the first-open intro), the theme hook, rendered with `react-dom`; withheld from React Native bundles the way `./server` is |
+| `@everfur/sdk/web/records` | records for a browser host: `EverfurRecordsPage` (the Everfur web app's records page, complete on its own: request from a clinic, upload, request status, the full record with vaccinations, all inside your page), the named screens, `EverfurRecords` (the React Native-shaped flow), `useEverfurRecords`, `createWebRecordsUploadTransport`, `fileToHandle`; its own entry, withheld from React Native like `./web`; available when Everfur enables records for the account. Frame mode serves it with `surface: 'records'` (see [chapter 13](https://docs.everfur.com/web/#web--2-frame-mode-the-loader-and-the-frame)) |
+| `@everfur/sdk/web/records-sheet` | `recordsSheet()`: the v3 records sheet and its lab result screen, `EverfurRecordsPage`'s default look (loaded on first mount; `sheet={false}` keeps the classic page, which downloads none of it), or built with options and passed to its `sheet` prop; withheld from React Native like `./web`; see [chapter 13](https://docs.everfur.com/web/#web--records-everfur-sdk-web-records) |
+| `@everfur/sdk/web/intro` | the first-open intro `EverfurTabs` plays on a phone-narrow page (`EverfurIntro`, its clinic request frames, `EverfurRecordsLandedBanner`, `useEverfurIntroSeen`), downloaded only when it plays; withheld from React Native like `./web`; see [chapter 13](https://docs.everfur.com/web/#web--three-tabs-everfurtabs) |
 | `@everfur/sdk/web/records/upload` | `createWebRecordsUploadTransport` alone, for the `uploadTransport` on the provider config at your app root; the same function `@everfur/sdk/web/records` exports, without the records entry |
 | `@everfur/sdk/server` | **server-only** `mintPartnerSession`, `revokePartnerMemberSessions` (end one member's sessions now) and the partner pet helpers (no React Native resolution; never bundled on-device) |
-| `@everfur/sdk/server/events` | **server-only, Node only** partner events (preview): `constructEvent` to verify webhooks, `sendPartnerEvent`; see [chapter 15](https://sdk.everfur.com/v1/docs/index.html#sec-events) |
+| `@everfur/sdk/server/events` | **server-only, Node only** partner events (preview): `constructEvent` to verify webhooks, `sendPartnerEvent`; see [chapter 15](https://docs.everfur.com/webhooks/) |
 | `@everfur/sdk/testing`, `@everfur/sdk/testing/rn`, `@everfur/sdk/testing/web` | test seams (`MockTransport`, `useEverfurTestEntitlements`, ...) for your own tests |
 
 `@everfur/sdk/client` and `@everfur/sdk/core` expose the framework-free layers for advanced integrators;
@@ -215,7 +216,7 @@ most apps only need the root entry plus the capability subpaths.
 ## Reference app
 
 A full, runnable integration (a fictional "Pawtrail" app plus a minimal mint backend that holds the secret)
-lives at [`examples/minimal-integration.tsx`](https://sdk.everfur.com/v1/docs/index.html#sec-quickstart) in this repository; it is
+lives at [`examples/minimal-integration.tsx`](https://docs.everfur.com/quickstart/) in this repository; it is
 type-checked by `npm run docs:check`, so it cannot rot. It shows anonymous mode, the two-credential session
 mint, pet registration and sign-out. (A separate `everfur-integration-example-rn` app exists internally but
 is not published anywhere a partner can reach, so do not rely on references to it.) It gates every

package/dist/{Chat.d-Dts8u_1a.d.cts → Chat.d-aycmX1CA.d.cts}

@@ -1,11 +1,12 @@
 import { ReactNode } from 'react';
 import { StyleProp, ViewStyle } from 'react-native';
 import { P as PetRef, C as ConversationId } from './ids.d-B2GAAifq.cjs';
-import { i as EverfurPresentationInput } from './presentation.d-DMbdad7G.cjs';
-import { a as ChatCheckinTarget } from './ports.d-CEROoqnA.cjs';
-import { W as WidgetPet, P as PetProfileInput } from './petsRepository.d-lp1BHRqM.cjs';
-import { U as UrgencyDisplayLevel, E as EverfurChatDraftStore, c as EverfurStarterPrompt } from './attachments.d-Bp2qbHxn.cjs';
+import { i as EverfurPresentationInput } from './presentation.d-vy8kTGfR.cjs';
+import { a as ChatCheckinTarget } from './ports.d-DBA_gsq5.cjs';
+import { W as WidgetPet, P as PetProfileInput } from './petsRepository.d-B2TpRE7r.cjs';
+import { E as EverfurStarterPrompt } from './quickPrompts.d-NM_81Jc1.cjs';
 import { L as LifecyclePort } from './LifecyclePort.d-Cr1p33a7.cjs';
+import { U as UrgencyDisplayLevel, E as EverfurChatDraftStore } from './attachments.d-DNUCiyy5.cjs';
 import { F as FileHandle } from './ports.d-BX4f4UsB.cjs';
 
 /** Where a picked image comes from: the host's photo library, or its camera. */
@@ -311,6 +312,13 @@ interface EverfurChatProps {
     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;

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

@@ -1,11 +1,12 @@
 import { ReactNode } from 'react';
 import { StyleProp, ViewStyle } from 'react-native';
 import { P as PetRef, C as ConversationId } from './ids.d-B2GAAifq.js';
-import { i as EverfurPresentationInput } from './presentation.d-DMbdad7G.js';
-import { a as ChatCheckinTarget } from './ports.d-COIyN624.js';
-import { W as WidgetPet, P as PetProfileInput } from './petsRepository.d-BuGHymNx.js';
-import { U as UrgencyDisplayLevel, E as EverfurChatDraftStore, c as EverfurStarterPrompt } from './attachments.d-Djy9z_0Z.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. */
@@ -311,6 +312,13 @@ interface EverfurChatProps {
     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;

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

@@ -1,6 +1,6 @@
 import { ReactNode } from 'react';
 import { StyleProp, ViewStyle } from 'react-native';
-import { d as RecordsScreenBaseProps } from './useRecordsDepth.d-DFcCfiXm.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.d-Ce2Zhnrb.d.ts → DepthViews.d-DIvxzLDf.d.ts}

@@ -1,5 +1,5 @@
 import { CSSProperties, ReactNode } from 'react';
-import { d as RecordsScreenBaseProps } from './useRecordsDepth.d-DFcCfiXm.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.d-BMU2jFPw.d.cts → DepthViews.d-Dy0Zl-s-.d.ts}

@@ -1,6 +1,6 @@
 import { ReactNode } from 'react';
 import { StyleProp, ViewStyle } from 'react-native';
-import { d as RecordsScreenBaseProps } from './useRecordsDepth.d-sAq2Qkhr.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.d-BIp599lz.d.cts → DepthViews.d-wLNkzk9f.d.cts}

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

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 };

package/dist/animations/index.d.cts

@@ -1,8 +1,8 @@
 import { ReactNode } from 'react';
 import { StyleProp, ViewStyle } from 'react-native';
 import { E as EverfurResult } from '../EverfurResult.d-BFH-3s6E.cjs';
-import { A as AuthContext } from '../identity.d-60LeJt_s.cjs';
-export { I as IdentityProvider, n as newSessionId } from '../identity.d-60LeJt_s.cjs';
+import { A as AuthContext } from '../identity.d-CJfnWOdH.cjs';
+export { I as IdentityProvider, n as newSessionId } from '../identity.d-CJfnWOdH.cjs';
 import { P as PetRef } from '../ids.d-B2GAAifq.cjs';
 export { B as Brand, U as UserRef, _ as __brand } from '../ids.d-B2GAAifq.cjs';
 import { z } from 'zod';
@@ -11,9 +11,9 @@ export { a as CACHE_EPOCH_STORAGE_KEY, c as createCacheEpochGuard } from '../cac
 import { T as TelemetryPort } from '../TelemetryPort.d-BDNr00hu.cjs';
 import { E as EverfurError } from '../EverfurError.d-8NHtlgzA.cjs';
 export { a as EverfurErrorCategory, b as EverfurErrorCode } from '../EverfurError.d-8NHtlgzA.cjs';
-import { D as DisabledLevel, C as CapabilityDecision } from '../resolve.d-jI8FmBj3.cjs';
-export { b as CapabilityDisabled, a as CapabilityName } from '../resolve.d-jI8FmBj3.cjs';
-export { A as AcceptedFrame, a as AnalysisCompleteFrame, b as AnalysisStartedFrame, D as DeltaFrame, c as DoneFrame, E as ErrorFrame, d as EverfurRequest, e as EverfurRequestBase, F as Frame, f as FrameBase, g as FrameKind, H as HeartbeatFrame, h as HttpMethod, M as MultipartBody, T as TransportPort, U as UnknownFrame, i as UrgencyLevel } from '../config.d-BR3DT9ho.cjs';
+import { D as DisabledLevel, a as CapabilityDecision } from '../resolve.d-CoQWUy1Y.cjs';
+export { b as CapabilityDisabled, C as CapabilityName } from '../resolve.d-CoQWUy1Y.cjs';
+export { A as AcceptedFrame, a as AnalysisCompleteFrame, b as AnalysisStartedFrame, D as DeltaFrame, c as DoneFrame, E as ErrorFrame, d as EverfurRequest, e as EverfurRequestBase, F as Frame, f as FrameBase, g as FrameKind, H as HeartbeatFrame, h as HttpMethod, M as MultipartBody, T as TransportPort, U as UnknownFrame, i as UrgencyLevel } from '../config.d-DJ4mvf_w.cjs';
 
 /**
  * The full /state payload. `degraded` + `cache_epoch` + `cache_key` are additive fields an older backend

package/dist/animations/index.d.ts

@@ -1,8 +1,8 @@
 import { ReactNode } from 'react';
 import { StyleProp, ViewStyle } from 'react-native';
 import { E as EverfurResult } from '../EverfurResult.d-D_-254ZY.js';
-import { A as AuthContext } from '../identity.d-DzTijonw.js';
-export { I as IdentityProvider, n as newSessionId } from '../identity.d-DzTijonw.js';
+import { A as AuthContext } from '../identity.d-BePPZ7Uv.js';
+export { I as IdentityProvider, n as newSessionId } from '../identity.d-BePPZ7Uv.js';
 import { P as PetRef } from '../ids.d-B2GAAifq.js';
 export { B as Brand, U as UserRef, _ as __brand } from '../ids.d-B2GAAifq.js';
 import { z } from 'zod';
@@ -11,9 +11,9 @@ export { a as CACHE_EPOCH_STORAGE_KEY, c as createCacheEpochGuard } from '../cac
 import { T as TelemetryPort } from '../TelemetryPort.d-BDNr00hu.js';
 import { E as EverfurError } from '../EverfurError.d-8NHtlgzA.js';
 export { a as EverfurErrorCategory, b as EverfurErrorCode } from '../EverfurError.d-8NHtlgzA.js';
-import { D as DisabledLevel, C as CapabilityDecision } from '../resolve.d-jI8FmBj3.js';
-export { b as CapabilityDisabled, a as CapabilityName } from '../resolve.d-jI8FmBj3.js';
-export { A as AcceptedFrame, a as AnalysisCompleteFrame, b as AnalysisStartedFrame, D as DeltaFrame, c as DoneFrame, E as ErrorFrame, d as EverfurRequest, e as EverfurRequestBase, F as Frame, f as FrameBase, g as FrameKind, H as HeartbeatFrame, h as HttpMethod, M as MultipartBody, T as TransportPort, U as UnknownFrame, i as UrgencyLevel } from '../config.d-Dy6igYlH.js';
+import { D as DisabledLevel, a as CapabilityDecision } from '../resolve.d-CoQWUy1Y.js';
+export { b as CapabilityDisabled, C as CapabilityName } from '../resolve.d-CoQWUy1Y.js';
+export { A as AcceptedFrame, a as AnalysisCompleteFrame, b as AnalysisStartedFrame, D as DeltaFrame, c as DoneFrame, E as ErrorFrame, d as EverfurRequest, e as EverfurRequestBase, F as Frame, f as FrameBase, g as FrameKind, H as HeartbeatFrame, h as HttpMethod, M as MultipartBody, T as TransportPort, U as UnknownFrame, i as UrgencyLevel } from '../config.d-MX7IKP2f.js';
 
 /**
  * The full /state payload. `degraded` + `cache_epoch` + `cache_key` are additive fields an older backend

package/dist/{attachments.d-D1yhJjcZ.d.ts → attachments.d--sIsfk6e.d.ts}

@@ -1,7 +1,7 @@
 import { E as EverfurError } from './EverfurError.d-8NHtlgzA.js';
-import { R as RequestFunnel } from './requestFunnel.d-CXUMPw1K.js';
+import { R as RequestFunnel } from './requestFunnel.d-D9edIEjZ.js';
 import { F as FileHandle, U as UploadTransport, a as UploadPolicyWire } from './ports.d-BX4f4UsB.js';
-import { R as ReadableStore, T as Timers } from './ports.d-COIyN624.js';
+import { R as ReadableStore, T as Timers } from './ports.d-D2n4HRUy.js';
 
 /** The image MIME types the chat accepts (the server's `CHAT_ATTACHMENT` rule, plus the `image/jpg` alias). */
 declare const ATTACHMENT_MIME_TYPES: readonly string[];

package/dist/{attachments.d-Bp2qbHxn.d.cts → attachments.d-DNUCiyy5.d.cts}

@@ -1,12 +1,12 @@
 import { E as EverfurError } from './EverfurError.d-8NHtlgzA.cjs';
 import { E as EverfurResult } from './EverfurResult.d-BFH-3s6E.cjs';
 import { C as ConversationId, P as PetRef, b as ResponseId } from './ids.d-B2GAAifq.cjs';
-import { f as ChatFeedbackType, l as ChatStatus, i as ChatMessage, c as ChatConversationListOptions, d as ChatConversationPage, g as ChatHistoryOptions, h as ChatMessagePage, a as ChatCheckinTarget, e as ChatFeedbackReceipt } from './ports.d-CEROoqnA.cjs';
-import { C as CheckinAnswer, a as CheckinOutcome } from './casesRepository.d-CT2LTicS.cjs';
-import { i as UrgencyLevel } from './config.d-BR3DT9ho.cjs';
-import { W as WidgetPet } from './petsRepository.d-lp1BHRqM.cjs';
+import { f as ChatFeedbackType, l as ChatStatus, i as ChatMessage, c as ChatConversationListOptions, d as ChatConversationPage, g as ChatHistoryOptions, h as ChatMessagePage, a as ChatCheckinTarget, e as ChatFeedbackReceipt } from './ports.d-DBA_gsq5.cjs';
+import { C as CheckinAnswer, a as CheckinOutcome } from './casesRepository.d-DCnix2pT.cjs';
+import { i as UrgencyLevel } from './config.d-DJ4mvf_w.cjs';
+import { W as WidgetPet } from './petsRepository.d-B2TpRE7r.cjs';
 import { U as UploadTransport, F as FileHandle } from './ports.d-BX4f4UsB.cjs';
-import { c as AttachmentQueue, d as AttachmentState, A as AttachmentError, b as AttachmentOutcome } from './attachments.d-DisnvB9R.cjs';
+import { c as AttachmentQueue, d as AttachmentState, A as AttachmentError, b as AttachmentOutcome } from './attachments.d-ZEpTUeWN.cjs';
 
 /** The three thumbs. `'neutral'` is the app's rotated thumbs-down glyph. */
 type ChatSentiment = 'up' | 'neutral' | 'down';
@@ -146,24 +146,6 @@ declare function useEverfurChat(opts?: {
     readonly conversationId?: ConversationId;
 }): UseEverfurChatState;
 
-/**
- * One partner-supplied starter chip for the empty thread (`EverfurChat`'s `starterPrompts`). The words are the
- * partner's own: Everfur shows `label` and sends `prompt` (the label when absent) as the member's next message.
- */
-interface EverfurStarterPrompt {
-    /** What the chip reads. A blank label drops the chip. */
-    readonly label: string;
-    /** The text sent when the chip is tapped. Defaults to `label`. */
-    readonly prompt?: string;
-    /**
-     * The chip's own fill, any CSS colour (for example `'#FFE7A1'`). Absent, the chip takes the theme's
-     * `highlight` under `onHighlight`, as the built-in chips do on a partner theme.
-     */
-    readonly tint?: string;
-    /** The chip's text colour on its `tint`. Absent, the theme's primary text colour. Ignored without `tint`. */
-    readonly ink?: string;
-}
-
 /**
  * CRN-16. The host's own storage for an unsent draft. The SDK ships NO persistence of its own: a draft is
  * memory-only unless a host passes this, because a question half-typed on a health surface is the reader's
@@ -251,4 +233,4 @@ interface UseChatAttachmentsOptions {
  */
 declare function useChatAttachments(options?: UseChatAttachmentsOptions): UseChatAttachmentsState;
 
-export { type ChatFeedbackReason as C, type EverfurChatDraftStore as E, type UrgencyDisplayLevel as U, type ChatFeedbackReasonOption as a, type ChatSentiment as b, type EverfurStarterPrompt as c, type UseChatAttachmentsOptions as d, type UseChatAttachmentsState as e, type UseEverfurChatState as f, type UseEverfurPetsState as g, useEverfurChat as h, useEverfurPets as i, useChatAttachments as u };
+export { type ChatFeedbackReason as C, type EverfurChatDraftStore as E, type UrgencyDisplayLevel as U, type ChatFeedbackReasonOption as a, type ChatSentiment as b, type UseChatAttachmentsOptions as c, type UseChatAttachmentsState as d, type UseEverfurChatState as e, type UseEverfurPetsState as f, useEverfurChat as g, useEverfurPets as h, useChatAttachments as u };

package/dist/{attachments.d-DisnvB9R.d.cts → attachments.d-ZEpTUeWN.d.cts}

@@ -1,7 +1,7 @@
 import { E as EverfurError } from './EverfurError.d-8NHtlgzA.cjs';
-import { R as RequestFunnel } from './requestFunnel.d-DWQQpjFR.cjs';
+import { R as RequestFunnel } from './requestFunnel.d-RZex94XX.cjs';
 import { F as FileHandle, U as UploadTransport, a as UploadPolicyWire } from './ports.d-BX4f4UsB.cjs';
-import { R as ReadableStore, T as Timers } from './ports.d-CEROoqnA.cjs';
+import { R as ReadableStore, T as Timers } from './ports.d-DBA_gsq5.cjs';
 
 /** The image MIME types the chat accepts (the server's `CHAT_ATTACHMENT` rule, plus the `image/jpg` alias). */
 declare const ATTACHMENT_MIME_TYPES: readonly string[];