@everfur/sdk 0.6.0 → 0.7.1

package/CHANGELOG.md

@@ -10,6 +10,234 @@ changes that has not been earned by any production integration yet.
 
 ## [Unreleased]
 
+## [0.7.1] - 2026-10-01
+
+### Fixed
+
+- **`RecordShareAudience` is now exported (type-only) from `@everfur/sdk/records/depth` and
+  `@everfur/sdk/web/records/depth`**, the audience `RecordsDepthClient.createShare(petRef, { audience })` takes.
+  Before, both depth API reports carried an api-extractor warning pinned to a hashed build file
+  (`dist/depth-<hash>.d.ts`), so `npm run api:check` failed on every version bump until the reports were
+  regenerated.
+- **`EverfurTelevetHost` takes `onPickMedia` (web).** The intake step has had a picker seam since booking photos
+  shipped (`onPickMedia` on `EverfurTelevet`), but the default in-page visit never reached it: the host and
+  `EverfurTelevetDialog` rendered the flow without a picker, so a partner on the button, chat or its own host
+  could not offer photos even with booking media served. The host now passes it through, as it does
+  `onAddToCalendar`. Absent, the intake step has no attachment row, as before.
+
+## [0.7.0] - 2026-10-01
+
+### Added
+
+- **Records share: send a pet's record to a vet, groomer or kennel by email, and share it for an audience while
+  the server says so (web and React Native).** The share sheet gains the design's `Who it’s for` (`Vet` /
+  `Groomer` / `Boarding`), `Send to` (`vet@example.com…`) and `Send` / `Sending…`, over `POST
+  /widget/v1/records/pets/{pet_ref}/everfur_record/share/email`. The server mints the link and emails it; the
+  link is NEVER returned, so it never reaches `onOpenUrl`, the clipboard or the screen, and the new row under
+  `Active links` has no URL. The sheet says `Sent to {email}. The link works for 7 days.` (and `Add an email to
+  send {pet}’s record.` for an empty field). This works with EFBackend's `partner.records_share_audience_enabled`
+  off (default), where the pick only chooses the email's wording. ONLY while it is on, `GET
+  /widget/v1/records/features` serves `share_audiences` (parsed fail closed: malformed is no audiences, never
+  the upload types), the copy-link mint sends `{audience}`, and the sheet draws the lead (`Pick who it’s for; we
+  include the right pages.`, the web's `Share a snapshot of what {pet}’s vets recorded. ...`) and a `What’s
+  included` list derived from the served scope with the SDK's own section labels (a boarding list never
+  mentions a phone number). With it off neither is drawn, because the content is the same for everyone. New:
+  `RecordsDepthClient.emailShare`, `readFeatures?()`, `createShare(petRef, { audience })`,
+  `RecordsFeatures.shareAudiences`, `mapShareAudiences`, `mapRecordShareEmailReceipt`, `isShareRecipientEmail`,
+  `RecordShareAudience` and friends, `audience` on `RecordShare` and `RecordShareLink`, and `shareAudiences`,
+  `features`, `sending`, `sendEmail` on `useRecordShares`. The nameless `Add an email to send the record.` and
+  the mail failure `Could not send the email. Please try again.` are owner-approved (2026-10-01).
+- **Vet messages and the visit summary, in your app (preview, dark until Everfur turns it on).** The Everfur app's
+  vet thread and visit summary on both platforms, over the five partner routes of EFBackend #1809
+  (`/widget/v1/televet/messages/threads`, one pet's thread and its send, the read receipt, and
+  `/consults/{consult_id}/summary`), which sit behind `partner.televet_messages_enabled` (default OFF). While the
+  switch is off the thread list answers 404 and nothing below is drawn. While it is on: the visits screen gains the
+  design's "Messages" card (one row per pet, the newest message, "New" / web "New reply" while unread), the visit
+  before the call gains "Running late? Message {vet}", a finished visit opens its approved summary ("What {vet} saw",
+  "{pet}’s plan" word for word, "From this visit", the vet card, "Book a follow-up"), and the thread screen reads and
+  sends text with the design's composer and note. New exports from `@everfur/sdk/televet/booking` and
+  `@everfur/sdk/web/televet/booking`: `TelevetVetThreadScreen`, `TelevetVisitSummaryScreen`, `useVetThreads`,
+  `useVetThread`, `useVisitSummary`, `vetThreadPetRef`, `VET_MESSAGES_COPY`, the wire types (`VetThread`,
+  `VetMessage`, `VisitSummary`, ...), the path builders and `isVetMessagesDark` / `isVetThreadVetFirst`.
+  `TelevetBookingController` gains five optional methods (`listVetThreads`, `listVetMessages`, `sendVetMessage`,
+  `markVetThreadRead`, `visitSummary`); an injected controller without them gets no Messages card, as a dark tenant
+  does. `TelevetScreen` gains `thread` and `summary`. The 409 line (`Your vet will write first. You can reply once
+  they do.`) and a message's attachment count (`{n} attached`) are owner-approved (2026-10-01).
+
+- **Records: a photo of a paper record uploads, while Everfur says so (web and React Native).** The SDK now reads
+  `GET /widget/v1/records/features` (zod-parsed, fail closed: a failed or malformed answer is PDF only). While the
+  answer carries `upload_content_types` (EFBackend `partner.records_image_upload_enabled`, off by default), the
+  upload accepts JPEG, PNG and HEIC/HEIF as well as PDF: the controller's gate admits them and initiate declares
+  the photo's own type; the web picker names a photo from its first bytes, never `File.type`. The upload card
+  then reads the design's photo lines (`A PDF, or a photo of a paper record. Add them all; we sort them by date.`,
+  `Have more?` over `PDFs and photos of paper records both work. ...`, the web refusal `We can’t read this kind of
+  file. Upload a PDF or a photo of the record.`), and the dashboard's upload way carries `A PDF, or a photo of a
+  paper record.`. React Native adds `Take a photo` (`of a paper record`) when the host sets `camera` on the config
+  and `Choose from photos` when it passes the new `onPickPhotos` (on `EverfurRecords`, `EverfurRecordsUpload` and
+  `EverfurRecordsRequest`), with `Choose a file` over `PDF`. With the switch off, or with no photo path wired on
+  React Native, every surface is exactly as before. New API: `RecordsController.readFeatures?()`,
+  `useEverfurRecords({ readUploadFeatures })` and `uploadContentTypes` on its state, `acceptsPhotos`,
+  `RecordsFeatures`, `RecordsUploadContentType`, `RecordsPhotoContentType`, and on web `recordsDocumentAccept` plus
+  an optional `types` argument on `fileToHandle`, `isUploadableHandle` and `pickDocument`.
+
+### Changed
+
+- **The vet booking asks the emergency question itself, straight after Describe (web and React Native).** With no
+  `onTriageReason` seam, `EverfurTelevetBooking` now asks `TelevetBookingController.triage`, a new optional method
+  that posts the member's words to `POST /widget/v1/televet/consults/triage` (served dark on the partner plane
+  behind `partner.televet_early_triage_enabled`, the booking's own classifier). An emergency or fallback verdict
+  opens the existing approved emergency warning before the vet picker, instead of only at Confirm. Every failure
+  of the read (the dark 404, 403, 429, 5xx, an unreadable body) answers `null` and the flow goes on exactly as
+  before; one attempt, no retry. A host seam still wins. `TelevetTriageVerdict` now lives in the core booking
+  types and is re-exported unchanged; `KNOWN_PARTNER_ROUTES` gains the route and `KNOWN_ABSENT_ROUTES` loses it.
+- **Televet booking: photos, videos and documents reach the vet when the partner plane serves them.** A pick
+  from the host's `onPickMedia` is presigned when picked through the new `POST
+  /widget/v1/televet/attachments/initiate` (EFBackend #1806, dark behind `partner.televet_booking_media_enabled`)
+  and sent at Confirm, one at a time, through the chat attachment transport (the S3 POST, no bytes before Confirm);
+  its `s3_key` goes in `media_refs`. What did not go is counted into the existing attachment notice: a failed post
+  or presign, the server's own `FILE_TOO_LARGE` / `INVALID_CONTENT_TYPE`, the local type and size rules (the
+  server's list: JPEG, PNG, WebP, HEIC/HEIF, PDF, CSV, MP4, MOV; 25 MB, video 200 MB), and any key the booking
+  did not keep. DARK (the presign's 404, or an injected controller with no `initiateAttachment`), nothing is sent,
+  `media_refs` is `[]` and every pick is reported unsent, exactly as before. Two approved design lines render only
+  when true: `Optional. A close-up in good light helps.` under the row once the presign has answered, and `{pet}’s
+  records, your notes and the photo go to {vet} ahead of the call.` on the confirmation when the records were
+  shared and exactly one photo went and the consult kept it. New: `TelevetBookingController.initiateAttachment`,
+  `TelevetIntakeMedia`'s `meta` and `TelevetBookedScreen`'s `sentPhoto`. On the web the bytes are read back from
+  the host's `blob:` URL, so a host page's CSP needs `connect-src` for `blob:` and the upload bucket, and a web
+  upload in production also needs the televet media bucket's CORS for the partner origin (EFBackend #1825).
+- **Televet cancel: "What changed?" is optional on both platforms.** The question is marked `Optional`, as the
+  approved design marks it (web `cancel`, mobile `vet-cancel`, 30 Sep 2026). The web no longer refuses a cancel
+  with no answer picked (`Tell us why you are cancelling.` is gone); like React Native it sends the reviewed fixed
+  reason (`Cancelled by the pet parent in the app.`) instead, and a picked answer can be taken back. A picked
+  answer still sends its own words. The wire always carries a `reason` (never a `reason_code`), so the cancel is
+  valid whether or not the server's optional-reason flag is on.
+- **Records: clinic search results show their distance in miles.** The clinic picker draws `3.2 mi` (and says `3.2
+  miles away`) as the design does, converted locally from the wire's `distance_km`; it drew kilometres. Web and React
+  Native.
+- **Records: a source document reads its page count.** A row under `Sources on file` now reads `{n} pages · {date}`
+  (the design's `3 pages · Aug 14`; one page reads `1 page`) when the record wire counts the document's pages.
+  EFBackend serves `documents[].page_count` only while its `partner.records_document_page_count_enabled` switch is
+  armed (default off); until then, and for a document the record worker has not counted, the row keeps its date alone.
+  Web and React Native.
+- **Visual and copy change: chat reads and looks like the Everfur app design (web and React Native).** By owner
+  decision (30 Sep 2026) the design artifacts count as approved, so chat carries their wording verbatim (the web
+  surface the web design's, React Native the mobile design's where they differ) and their layout on the theme's
+  derived tokens, so partner palettes still apply. Copy: the composer asks `Ask anything about {pet}…` (web: `Ask a
+  follow-up…` once a reply is on screen, `Tell us what’s happening…` under an emergency banner) and is named
+  `Message`; the reply is headed `Everfur` (not drawn for a `hide_powered_by` tenant); the waiting line is `Reading
+  {pet}’s records…` and a settled reply is announced as `Everfur answered.` rather than read out; the emergency tier
+  is `Call a vet now`, with the ASPCA Animal Poison Control call (owner-approved) and `Nearest emergency vet` when
+  the host's `onFindVet` is the route; the history is `Chats` (`Search chats…`, `Chats and vet messages · {n}` once
+  every row is loaded, `New reply · {date}` on an unread row, `No chats match that.`); the pet sheet is `Your pets`
+  with `Add a pet`; the switch control is `{pet}. Switch pet`; the web vet-prep chip is `Book a video visit` and
+  the React Native one drops its full stop. The fixed clinical disclaimer band is replaced on chat by the design's
+  one-line footnote under the composer (compiled and frozen in the chat copy module; records keep the band).
+  Layout: 20 px bubbles with a 6 px tail (a vet's at the top left, still pink), the body size on every box, the
+  sender's name over a reply, a left-aligned hello with edge-less starter chips, the web's outline follow-up chips
+  and the mobile design's headed follow-up rows, a Dark Green send disc on the web composer, a white history panel
+  (the web rail was brand green), and the emergency banner painted from the theme's alert red. New bubbles pop from
+  their corner and starter chips rise, both off under reduced motion. The quick prompts stay the compiled templates:
+  the design's chips name one sample pet's records, and the SDK has no served source of record-personalised prompts.
+  The web chat's geometry guard now pins the design and records where it departs from the shipped web app.
+  `TypingIndicator` (`@everfur/sdk/testing/rn`) takes an optional `petName` for the reading line; called with no
+  props it reads `your pet`, as before it drew with none.
+
+- **Visual and copy change: the records surfaces read and look like the Everfur app designs (web and React Native,
+  medical records only).** By owner decision (30 Sep 2026) the records screens port the owner-approved design
+  artifacts' wording and layout. The clinical disclaimer band under every records screen is replaced by the
+  artifacts' one-line footnote, `Everfur summarizes what your vet recorded. It is informational, not
+  diagnostic.` (compiled, not overridable, `RECORDS_FOOTNOTE`); chat and televet keep the band. Titles follow the
+  pet (`Rex's Records` on the web, the pet's name on React Native, `Request Rex's records`, `Send Rex's record`,
+  `Rex's health record`; the nameless forms are unchanged), the full record is `Visits & records`, the clinic
+  release is `Check and send` with the artifact's checkbox wording around the drawn signature (kept), `What we ask
+  for`, `What happens next` and `Send request`, the clinic picker gains its lead and `How it works`, the request
+  screen gains `Request sent`, `Where it stands` and `Request details`, a clinic request's tracker reads `Request
+  sent`, `Clinic notified`, `Waiting for records…` with a `Now` pill, and the in-flight dashboard reads `Rex's
+  records are on the way` with `Another clinic` and `Upload a document` beside it. Cards take the artifacts'
+  radius 20 and neutral edge, buttons are 52 tall and press to 0.97, status pills are the artifacts' mono capitals,
+  sections rise in on the web, and the record tiles' tints are derived from the theme. Every motion rests under
+  reduced motion. Lines whose promise the partner wire cannot keep yet are held back and the truthful line stays:
+  photo upload, send-by-email and audiences, "We'll text you",
+  reminders, a follow-up date, clinic search by phone or fax, and the birth-date line of the release.
+  The share sheet states the link's terms (`Sent as a secure link that works for 7 days. You can stop sharing it
+  any time.`; by owner decision a new link lives 7 days) and, on React Native, `Link copied. It works for 7 days.`
+  and `Couldn't copy. The link is {url}`. The vendored platform contract is re-synced to EFBackend main (digests
+  only). `buildRequestTimeline` (a hook-based UI's rail) now reads the same words for a clinic request and takes an
+  optional `{ petName }` for its last step (`Added to Rex's records`); no other export changes.
+
+- **Visual and copy change: the vet visit surfaces follow the owner-approved Everfur app designs of 30 Sep 2026
+  (web and React Native).** The booking is the designs' eight steps, "Step n of 8": who, where the pet will be
+  during the visit (new, asked on every booking and seeded with `usState`; what each place permits is read from
+  the served state policy), what's going on (now on React Native too, with the designs' twelve issues for every
+  pet), the description, an explicit emergency check (new: seven signs and a yes or no; "Yes" shows the exits and
+  holds the flow until "I’ve handled this, continue booking", which sends `emergency_acknowledged: true`), your
+  vet, the time (grouped Morning, Afternoon, Evening) and the review ("Book the visit", the attestation "{pet} and I
+  will be in {state} during the visit.", a Change on When; on the web a press with a box unticked says "Check both
+  boxes to book the visit."). The flow bar, option cards, chips, day and time chips, review rows, confirmation,
+  visits page ("Video visits", "Next video visit", "Past video visits", the vet footnote), cancel ("What changed?"
+  with four answers, sent as the reason) and reschedule (a "Move to ..." button; picking no longer moves the visit)
+  are restyled from theme tokens only, and the waiting room words follow ("Waiting room", "Before {vet} joins",
+  "15 minutes"). The ASPCA Animal Poison Control row is now drawn on both platforms (owner approval). The
+  `VetVisitButton` default label is "Vet" (was "Talk to a vet"). Not ported, because this plane cannot keep the
+  promise yet: text-message reminders, a photo reaching the vet, an optional cancel reason, vet messages, the visit
+  summary, the device checks and "joins in about 3 minutes". Public API: `TelevetBookingStep` and
+  `TELEVET_BOOKING_STEPS` gain `where` and `emergency`; `TELEVET_BOOKING_COPY` gains keys and changes values;
+  `televetIssueChips` no longer filters by species; the web `TelevetBookingChrome` takes `showBack`, the RN one
+  `triageOpen`; `TelevetBookedScreen` takes `sharedRecords`; `TelevetSlotPicker` takes `periodLabels`.
+
+- **Visual change: the default theme adopts the Everfur design tokens of 26 Sep 2026 (web and React Native).** By
+  owner decision (30 Sep 2026) the compiled light default follows the design tokens ahead of the Everfur apps. Body
+  text is solid black (`text.primary`, `onBubbleVet` `#111111` -> `#000000`). Off-White is retired: the card,
+  composer and popover grounds are white (`surfaceCream`, `composerFill` `#FDFBF8` -> `#FFFFFF`), so
+  `surface_style: 'cream'` now paints white on the light palette. The warm greys become the design tokens' neutral
+  ones: `text.muted` `#6E6660` -> `#6B6B6B`, `borderRingCream` `#D8D2C8` -> `#E4E4E4`, `surfaceSubtle`
+  `#EFE9E3` -> `#F1F5F2` (mist), `skeleton` -> `#E9F1E9`, `badgeBgNeutral` follows the new grey. The reds are the
+  one alert red: `danger` `#B91C1C` and `errorRed` `#CC1600` -> `#C03410`, `badgeBgCritical` -> that red at 6%.
+  The type scale moves to the design tokens': `caption` 12 -> 13, `bodyTight` 13 -> 15, `body` 14 -> 17,
+  `subtitle` 16 -> 20, `heading` 18 -> 22 (`nano` to `tiny` and `verdict` are unchanged), and the React Native chat
+  bubble and field line heights follow the body size. Every ink still passes the contrast guards on both palettes.
+  The dark palette's `text.muted` is the neutral `#9A9A9A` (was `#9A938C`); the rest of the dark palette, the vet
+  bubble's pink and the motion curves are unchanged. No font is bundled: the design tokens' Azeret reaches a surface
+  only when a branding supplies it (`fonts`, or `font_urls` on the web). Partner branding resolves exactly as before
+  (lock > partner code > console > this default); only the default moved. A partner `font_size_base` still sets the
+  body size, and the other sizes now scale from the new 17 px body rather than 14.
+
+### Fixed
+
+- **Televet booking: the step counter counts the steps the owner sees (web and React Native).** A one-pet household
+  never sees the pet step, but the bar still counted it, so the flow opened on `Step 2 of 8` and never showed a
+  first step (partner smoke test of 0.6.0). It now reads `Step 1 of 7` ... `Step 7 of 7` there (seven segments on
+  React Native) and keeps the design's eight for a household with a pet to choose. New optional
+  `TelevetBookingChromeProps.stepContext` (the reducer's `TelevetBookingContext`) for a host driving the chrome
+  itself; absent, the bar counts eight as before.
+- **Records: no empty heading on the upload screen (web and React Native).** Its header row passed an empty title
+  and still drew an `<h2>` (a Text with the header role on React Native) that a screen reader lists and reads as
+  nothing (partner smoke test of 0.6.0). The header row now draws a spacer for an empty title, and on the web the
+  screen's own title (`Upload a document`) is the heading focus moves to when the member arrives.
+- **Records: a date in the record's Identity section reads as a date.** The server sends identity values raw, so the
+  date of birth showed as `2022-07-27`; a bare calendar date now uses the records date format (`Jul 27, 2022`) on
+  web and React Native. Species and sex still show as sent (`dog`, `female`): the SDK has no vocabulary for them,
+  so display labels for those are a server item.
+- **Records clinic request forms (`EverfurClinicRequest`, `EverfurClinicRequestBatch`, web and React Native): search
+  results no longer fill the page.** The forms asked for 100 clinics and drew every one inline (about 6,750 px on
+  the partner smoke test of 0.6.0). They now ask for one page of 25 (the clinic picker's page size), draw the first
+  five, and add five more per `Load more` (the SDK's existing label); a member who still has not found the clinic
+  refines the search.
+- **"Please add your signature before submitting." no longer greets a form just opened.** It was an alert from the
+  first render. It now appears only once everything else is filled in, when the missing signature is what keeps
+  Send closed.
+- **The signature pad's `Draw your signature in the box above.` is gone in typed mode (web),** where there is
+  nothing to draw. No typed-mode hint exists in the consumer apps or the designs, so the line stays empty.
+- **Chat: opening chat no longer creates an empty conversation (web and React Native).** The bootstrap prime
+  POSTed `/widget/v1/conversations` on every mount (twice under React StrictMode's double mount), so the member's
+  history filled with empty `New conversation` rows (partner smoke test of 0.6.0). The prime still reads the head
+  of the list (resuming a thread with an unread reply, which is also what delivers an owed check-in) and prefetches
+  the suggested prompts; the conversation is now created by the first send, which pays that one round trip before
+  it streams. `runtime.prepare()` no longer creates one either. `ChatController.primeConversation()` now settles to
+  `ConversationId | null` (null: no thread opened yet), and a failed head read is the prime's reported failure
+  (except a 403, since a key without history read can still chat). The web `Everfur answered.` announcement now
+  also fires for the first reply of a new thread, as it already did on React Native.
+
 ## [0.6.0] - 2026-09-29
 
 ### Added

package/dist/{Chat-CHqcgMyw.d.ts → Chat-CFi5cNUF.d.ts}

@@ -2,9 +2,9 @@ import { ReactNode } from 'react';
 import { StyleProp, ViewStyle } from 'react-native';
 import { P as PetRef, C as ConversationId } from './ids-B2GAAifq.js';
 import { F as FileHandle } from './ports-BN6RHF9W.js';
-import { a as ChatCheckinTarget } from './ports-iXPWd7Vt.js';
-import { W as WidgetPet, P as PetProfileInput } from './petsRepository-0oBVydl6.js';
-import { U as UrgencyDisplayLevel, L as LifecyclePort, E as EverfurChatDraftStore } from './attachments-CThFsH4b.js';
+import { a as ChatCheckinTarget } from './ports-Di9rdLO9.js';
+import { W as WidgetPet, P as PetProfileInput } from './petsRepository-BwxmfX_s.js';
+import { U as UrgencyDisplayLevel, L as LifecyclePort, E as EverfurChatDraftStore } from './attachments-SF88N654.js';
 
 /** Where a picked image comes from: the host's photo library, or its camera. */
 type AttachmentSource = 'photo' | 'camera';
@@ -48,7 +48,7 @@ interface EverfurChatProps {
     /** Called after the user picked another pet in the header switcher and the provider re-scoped to it. */
     readonly onPetChange?: (petRef: PetRef) => void;
     /**
-     * Your vet-visit preparation screen. Given, the empty thread's `Help me prep for {pet}'s vet visit.` chip
+     * Your vet-visit preparation screen. Given, the empty thread's `Help me prep for {pet}’s vet visit` chip
      * routes to it with the pet; absent, that chip is the Everfur vet visit entry inside Chat, shown only
      * while Everfur has it switched on for your tenant, else not shown at all.
      */

package/dist/{Chat-BoAvCWhI.d.cts → Chat-DQOsAumH.d.cts}

@@ -2,9 +2,9 @@ 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-ChnzSy4E.cjs';
-import { W as WidgetPet, P as PetProfileInput } from './petsRepository-SqIvEMiT.cjs';
-import { U as UrgencyDisplayLevel, L as LifecyclePort, E as EverfurChatDraftStore } from './attachments-rkox0ewd.cjs';
+import { a as ChatCheckinTarget } from './ports-BPKxFOSe.cjs';
+import { W as WidgetPet, P as PetProfileInput } from './petsRepository-BnVre3q7.cjs';
+import { U as UrgencyDisplayLevel, L as LifecyclePort, E as EverfurChatDraftStore } from './attachments-DI710no4.cjs';
 
 /** Where a picked image comes from: the host's photo library, or its camera. */
 type AttachmentSource = 'photo' | 'camera';
@@ -48,7 +48,7 @@ interface EverfurChatProps {
     /** Called after the user picked another pet in the header switcher and the provider re-scoped to it. */
     readonly onPetChange?: (petRef: PetRef) => void;
     /**
-     * Your vet-visit preparation screen. Given, the empty thread's `Help me prep for {pet}'s vet visit.` chip
+     * Your vet-visit preparation screen. Given, the empty thread's `Help me prep for {pet}’s vet visit` chip
      * routes to it with the pet; absent, that chip is the Everfur vet visit entry inside Chat, shown only
      * while Everfur has it switched on for your tenant, else not shown at all.
      */

package/dist/{DepthViews-B0g83e_N.d.cts → DepthViews-C409ubw-.d.cts}

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

package/dist/{DepthViews-7Y8Ur058.d.ts → DepthViews-D81c95Ra.d.cts}

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

package/dist/{DepthViews-Dg2bIon_.d.ts → DepthViews-es8mIK0w.d.ts}

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

package/dist/{DepthViews-CT5mQld9.d.cts → DepthViews-uilL1NJZ.d.ts}

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

package/dist/IntakeMedia-BcjjUizr.d.ts

@@ -0,0 +1,103 @@
+import { ReactNode } from 'react';
+import { T as TelevetConsult } from './bookingTypes-D4pD3tHs.js';
+
+/** The calendar entry a booked visit asks the host to write. */
+interface TelevetCalendarEvent {
+    /**
+     * A stable key for THIS consult's entry.
+     *
+     * Keyed on the CONSULT so a re-press updates the same entry rather than writing a second event for one
+     * visit, and so a later cancel or reschedule can address the SAME row. A host that ignores the key writes
+     * duplicates the owner has to clean up by hand.
+     */
+    readonly key: string;
+    readonly title: string;
+    readonly startDate: Date;
+    readonly endDate: Date;
+    /** The reminder offset in minutes, negative for "before". The platform queues its own at the same offset. */
+    readonly alarmOffsetMinutes: number;
+}
+/**
+ * Writes the entry. Resolves true when it landed in a calendar; false when the host has no calendar to write to
+ * or the entry could not be written; `'handed-off'` when the entry was handed to the member to add themselves (a
+ * file download, as `downloadTelevetCalendarFile` does), which puts nothing in a calendar yet. On true the
+ * confirmation says the visit was added; on `'handed-off'` it keeps Add to Calendar, enabled, so the member can
+ * press it again, as the consumer web app's link can be.
+ */
+type TelevetCalendarWriter = (event: TelevetCalendarEvent) => Promise<boolean | 'handed-off'>;
+/** The calendar key for a consult. One definition, so a cancel and a reschedule address the booked row. */
+declare function televetConsultCalendarKey(consultId: string): string;
+interface TelevetBookedScreenProps {
+    readonly consult: TelevetConsult;
+    readonly petName: string | null;
+    readonly onDone: () => void;
+    /** Absent, there is no Add to calendar control. */
+    readonly onAddToCalendar?: TelevetCalendarWriter | undefined;
+    /**
+     * Has the host PROVEN it can host the call in place? Defaults to false.
+     *
+     * Fail closed: a host that has not said so is assumed not to have mounted the call surface, and the in-place
+     * join promise is withheld rather than printed on a hope.
+     */
+    readonly canJoinInApp?: boolean;
+    /**
+     * How long the visit is, in minutes: the booked slot's served length (`televetSlotMinutes`), which is the
+     * length the platform runs the visit for. The calendar entry ends this long after the start.
+     *
+     * Absent, or not a positive number, the entry falls back to `CONSULT_MINUTES`, the same fallback the review's
+     * length row uses for a slot that does not say. The prebuilt flow always passes the slot's length.
+     */
+    readonly lengthMinutes?: number | undefined;
+    /**
+     * Did the owner share the pet's records with the vet on the review? Only then may step 02 say the records go
+     * to the vet ahead of the call; otherwise it keeps the deck's own summary line.
+     */
+    readonly sharedRecords?: boolean | undefined;
+    /**
+     * Did exactly one PHOTO go with this booking, and did the consult keep it? Only then may step 02 say the photo
+     * goes to the vet (the artifact's photo form). Defaults to false.
+     */
+    readonly sentPhoto?: boolean | undefined;
+}
+declare function TelevetBookedScreen({ consult, petName, onDone, onAddToCalendar, canJoinInApp, lengthMinutes, sharedRecords, sentPhoto, }: TelevetBookedScreenProps): ReactNode;
+
+/** A picked-but-not-yet-uploaded attachment, in the host's own terms. */
+interface TelevetIntakeMediaItem {
+    readonly uri: string;
+    readonly filename: string;
+    readonly mimeType: string;
+    readonly fileSize: number;
+}
+/**
+ * The host's media picker.
+ *
+ * Resolves the picks, or null when the owner cancelled. The SDK takes no picker dependency and opens no file
+ * dialog of its own; a partner supplies whichever picker its site already has, typically an `<input
+ * type="file">` whose `File` objects it turns into object URLs.
+ *
+ * `limit` is the remaining headroom, so the host can cap its own selection rather than returning picks this
+ * row has to silently discard.
+ */
+type TelevetMediaPicker = (limit: number) => Promise<readonly TelevetIntakeMediaItem[] | null>;
+interface TelevetIntakeMediaProps {
+    readonly media: readonly TelevetIntakeMediaItem[];
+    readonly onChange: (next: readonly TelevetIntakeMediaItem[]) => void;
+    /** Absent, the row renders nothing at all. There is no disabled Add control. */
+    readonly onPickMedia?: TelevetMediaPicker | undefined;
+    /**
+     * The list's accessible name.
+     *
+     * Required, with no default string here: naming the group is what makes the tiles announce as a set, and
+     * the name is user-facing copy this SDK does not author. The intake step passes a ported key down.
+     */
+    readonly listLabel: string;
+    /**
+     * A line under the row, or nothing. The booking passes the artifact's "Optional. A close-up in good light
+     * helps." only once the televet presign has answered, because the advice is true only when a photo can reach
+     * the vet. Absent, nothing is drawn.
+     */
+    readonly meta?: string | null | undefined;
+}
+declare function TelevetIntakeMedia({ media, onChange, onPickMedia, listLabel, meta }: TelevetIntakeMediaProps): ReactNode;
+
+export { type TelevetCalendarWriter as T, type TelevetMediaPicker as a, type TelevetCalendarEvent as b, type TelevetIntakeMediaItem as c, TelevetBookedScreen as d, type TelevetBookedScreenProps as e, TelevetIntakeMedia as f, type TelevetIntakeMediaProps as g, televetConsultCalendarKey as t };

package/dist/IntakeMedia-CL_S2tZE.d.cts

@@ -0,0 +1,103 @@
+import { ReactNode } from 'react';
+import { T as TelevetConsult } from './bookingTypes-D4pD3tHs.cjs';
+
+/** The calendar entry a booked visit asks the host to write. */
+interface TelevetCalendarEvent {
+    /**
+     * A stable key for THIS consult's entry.
+     *
+     * Keyed on the CONSULT so a re-press updates the same entry rather than writing a second event for one
+     * visit, and so a later cancel or reschedule can address the SAME row. A host that ignores the key writes
+     * duplicates the owner has to clean up by hand.
+     */
+    readonly key: string;
+    readonly title: string;
+    readonly startDate: Date;
+    readonly endDate: Date;
+    /** The reminder offset in minutes, negative for "before". The platform queues its own at the same offset. */
+    readonly alarmOffsetMinutes: number;
+}
+/**
+ * Writes the entry. Resolves true when it landed in a calendar; false when the host has no calendar to write to
+ * or the entry could not be written; `'handed-off'` when the entry was handed to the member to add themselves (a
+ * file download, as `downloadTelevetCalendarFile` does), which puts nothing in a calendar yet. On true the
+ * confirmation says the visit was added; on `'handed-off'` it keeps Add to Calendar, enabled, so the member can
+ * press it again, as the consumer web app's link can be.
+ */
+type TelevetCalendarWriter = (event: TelevetCalendarEvent) => Promise<boolean | 'handed-off'>;
+/** The calendar key for a consult. One definition, so a cancel and a reschedule address the booked row. */
+declare function televetConsultCalendarKey(consultId: string): string;
+interface TelevetBookedScreenProps {
+    readonly consult: TelevetConsult;
+    readonly petName: string | null;
+    readonly onDone: () => void;
+    /** Absent, there is no Add to calendar control. */
+    readonly onAddToCalendar?: TelevetCalendarWriter | undefined;
+    /**
+     * Has the host PROVEN it can host the call in place? Defaults to false.
+     *
+     * Fail closed: a host that has not said so is assumed not to have mounted the call surface, and the in-place
+     * join promise is withheld rather than printed on a hope.
+     */
+    readonly canJoinInApp?: boolean;
+    /**
+     * How long the visit is, in minutes: the booked slot's served length (`televetSlotMinutes`), which is the
+     * length the platform runs the visit for. The calendar entry ends this long after the start.
+     *
+     * Absent, or not a positive number, the entry falls back to `CONSULT_MINUTES`, the same fallback the review's
+     * length row uses for a slot that does not say. The prebuilt flow always passes the slot's length.
+     */
+    readonly lengthMinutes?: number | undefined;
+    /**
+     * Did the owner share the pet's records with the vet on the review? Only then may step 02 say the records go
+     * to the vet ahead of the call; otherwise it keeps the deck's own summary line.
+     */
+    readonly sharedRecords?: boolean | undefined;
+    /**
+     * Did exactly one PHOTO go with this booking, and did the consult keep it? Only then may step 02 say the photo
+     * goes to the vet (the artifact's photo form). Defaults to false.
+     */
+    readonly sentPhoto?: boolean | undefined;
+}
+declare function TelevetBookedScreen({ consult, petName, onDone, onAddToCalendar, canJoinInApp, lengthMinutes, sharedRecords, sentPhoto, }: TelevetBookedScreenProps): ReactNode;
+
+/** A picked-but-not-yet-uploaded attachment, in the host's own terms. */
+interface TelevetIntakeMediaItem {
+    readonly uri: string;
+    readonly filename: string;
+    readonly mimeType: string;
+    readonly fileSize: number;
+}
+/**
+ * The host's media picker.
+ *
+ * Resolves the picks, or null when the owner cancelled. The SDK takes no picker dependency and opens no file
+ * dialog of its own; a partner supplies whichever picker its site already has, typically an `<input
+ * type="file">` whose `File` objects it turns into object URLs.
+ *
+ * `limit` is the remaining headroom, so the host can cap its own selection rather than returning picks this
+ * row has to silently discard.
+ */
+type TelevetMediaPicker = (limit: number) => Promise<readonly TelevetIntakeMediaItem[] | null>;
+interface TelevetIntakeMediaProps {
+    readonly media: readonly TelevetIntakeMediaItem[];
+    readonly onChange: (next: readonly TelevetIntakeMediaItem[]) => void;
+    /** Absent, the row renders nothing at all. There is no disabled Add control. */
+    readonly onPickMedia?: TelevetMediaPicker | undefined;
+    /**
+     * The list's accessible name.
+     *
+     * Required, with no default string here: naming the group is what makes the tiles announce as a set, and
+     * the name is user-facing copy this SDK does not author. The intake step passes a ported key down.
+     */
+    readonly listLabel: string;
+    /**
+     * A line under the row, or nothing. The booking passes the artifact's "Optional. A close-up in good light
+     * helps." only once the televet presign has answered, because the advice is true only when a photo can reach
+     * the vet. Absent, nothing is drawn.
+     */
+    readonly meta?: string | null | undefined;
+}
+declare function TelevetIntakeMedia({ media, onChange, onPickMedia, listLabel, meta }: TelevetIntakeMediaProps): ReactNode;
+
+export { type TelevetCalendarWriter as T, type TelevetMediaPicker as a, type TelevetCalendarEvent as b, type TelevetIntakeMediaItem as c, TelevetBookedScreen as d, type TelevetBookedScreenProps as e, TelevetIntakeMedia as f, type TelevetIntakeMediaProps as g, televetConsultCalendarKey as t };