@everfur/sdk 0.12.1 → 0.14.0

package/CHANGELOG.md

@@ -10,6 +10,298 @@ 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
+
+Measured against 0.12.1 and `origin/main` with the api-extractor reports: no export was removed or renamed. These
+are the changes a 0.12 integration can notice, with one migration line each.
+
+- **The v3 look is the default (presentation).** A partner that set nothing now gets the chat cards, the history
+  sheet, the focus card, the Health Plan focus layout and the records sheet. Migration: set the older value per field
+  (`chatAnswerStyle: 'bubbles'`, `chatHistoryStyle: 'drawer'`, `chatTopCard: 'none'`,
+  `healthPlanLayout: 'standard'`, `recordsTopRiskLine: false`) in the console or in `presentation`.
+- **`EverfurRecordsPage` draws the records sheet by default (web).** Migration: pass `sheet={false}` to keep the
+  classic page; pass `sheet={recordsSheet(options)}` from `@everfur/sdk/web/records-sheet` to configure it.
+- **Records sheet types live on `@everfur/sdk/web/records-sheet`.** `EverfurRecordsSheetOptions`,
+  `EverfurRecordsLabDetail` and the sheet's style exports (prerelease builds only; never in a published version).
+  Migration: import them from `@everfur/sdk/web/records-sheet`, and pass the built sheet, not the options, to `sheet`.
+- **`HealthPlanFocusIcon` has more names** (`box`, `cart`, `minus`, `plus`, `chev`, `pulse`, `file`, `kit`, `dna`,
+  `heart` and others). Migration: a `renderIcon` that switches over every name needs a `default` branch that
+  returns an icon of yours (null draws none).
+- **`HealthPlanFocusOverlay` has more screens** (`cart`, `cartCheckout`, `placed`, `orders`, `order`, `weight`).
+  Migration: an `onOverlayChange` that switches over every value needs a `default` branch (use `controls.title` and
+  `controls.back` for the header).
+- **`HealthPlanFocusPart` has more parts.** Migration: a `Record<HealthPlanFocusPart, string>` of your own becomes
+  `Partial<Record<HealthPlanFocusPart, string>>` (as `HealthPlanFocusClassNames` already is).
+- **The shop is on with Everfur checkout.** With `checkout: "everfur_stripe"` Buy becomes Add to cart. Migration:
+  `focus.shop: false` keeps Buy and Subscribe going straight to Stripe Checkout. On React Native the shop and the
+  Stripe trip also need a valid https `focus.checkoutReturnUrl`; without one Buy keeps your `onBuy` / `onCheckout`.
+- **`HEALTH_PLAN_COPY.emptyTitle` / `emptyBody` are empty strings** (were `[copy needed: ...]` markers), with a new
+  `emptyAsk`. Migration: pass your own words through `emptyCopy`, or hide your tab on `onAvailability(false)`.
+
+### Changed
+
+- **Everfur's v3 design is the default look for every partner (presentation defaults).** With nothing set, the chat
+  draws answers as cards, past chats in a bottom sheet, the compact composer with the pet's name in the placeholder,
+  the past-chats bar scrolling with the thread and the focus card over an empty chat; the Health Plan uses the focus
+  layout; Records shows the top risk line and the clear-results filter. Nothing extra draws without its data (no
+  focus, no card; no pet name, the generic placeholder). Set the older value per field to keep the older look
+  (`bubbles`, `drawer`, `none`, `standard`, `generic`, `pinned`, `false`).
+- **Focus card look (web).** The chat's top card draws Raph's v3 card inline (CSP safe) with the partner's primary,
+  link ink and brand wash (`v3Palette`), and Everfur's neutrals and risk colours; on a dark theme the theme's own
+  neutrals. A host class on a part still replaces that part's style. `healthPlanTopCard` keeps the close control when
+  the pet has neither a sex nor a name (named "Close"), and reads the sex in any case.
+- **Daily message cap.** A 429 `ThrottlingException` that carries `daily_limit` (the backend's daily cap) is now
+  `quotaExceeded` (not retried, "You have used today's messages") instead of `rateLimited`.
+- **Starter chips for other species.** A pet that is neither a dog nor a cat no longer gets a chip that calls it a dog;
+  the chips without a species word stay.
+- **The v3 records sheet is `EverfurRecordsPage`'s default look (web).** Without a `sheet` prop the page loads
+  `@everfur/sdk/web/records-sheet` on first mount (its loading state meanwhile, the classic page if the entry
+  cannot load); `sheet={false}` keeps the classic page. The records frame bundles the sheet. The sheet paints in
+  the partner's `primary` and `accent` (new option `palette`, `'raph'` keeps Raph's colours), takes the pronoun
+  from the pet's sex, says "your pet" for a pet with no name, shows a species-aware sample, the medications taken
+  now, the Health Plan top risk line (`topRiskLine`, `onOpenPlan`), lines for missing labs, visits and a single
+  weight, and a failed request's status. New page props `weightUnit` (`'lb'` default, `'kg'`) and `onOpenPlan`.
+- The vendored platform contract and error registry are regenerated from EFBackend main (contract-public digest
+  242b9d30).
+- Bundle budgets: `dist-cdn/frame.js` 178,400 and `dist-cdn/records-frame.js` 208,100 bytes; `@everfur/sdk/shop`
+  54,600 bytes gzip.
+
+### Added
+
+- **The Care shop over the Everfur OMS (`@everfur/sdk/web/shop` and `@everfur/sdk/shop`), two new subpaths.**
+  `EverfurShop` renders the package, shop, product, Rx product, plan, orders and tracking screens, plus minimal
+  address, card, buy and consent steps whose copy is still placeholder keys (`SHOP_COPY_PLACEHOLDERS`). The shop stays
+  hidden until shop-config answers 200; a 404 or a signed-out host renders nothing and calls `onUnavailable`. Also
+  exported: `createOmsClient` (consumer auth via `getToken` per request, idempotency keys kept across
+  network/timeout/5xx retries), `newIdempotencyKey`, `isOmsRefusal`, `isOmsRetryable`, `isOmsUnavailable`,
+  `createOmsPackageSource`, `UNAVAILABLE_PACKAGE_SOURCE`, `SHOP_COPY` and `shopCopy`. The web entry adds
+  `createStripeJsPayments` and the `EverfurShopProps.cardHandoff` (`ShopCardHandoff | null`) and
+  `EverfurShopProps.cardReturn` (`ShopCardReturn | null`, `{ step: 'card' | 'cardAction', outcome: 'done' |
+  'closed' | 'failed' }`) props, so the card setup and 3-D Secure steps can leave the page and come back. The React
+  Native entry adds `shopBackRoute`, `ShopSwitchCard`, `createInAppBrowserCardSetup`, `createInAppBrowserPayments`
+  and `createInAppBrowserCard` (EFBackend's hosted card pages in the host's in-app browser, https only, no secret in
+  the URL, no native dependency) through the new `payments` prop. Closing the browser settles as `{ ok: false,
+  closed: true }` (`payerActionClosed`), not a failure. A confirm or approval that returns an order goes to that
+  order's page, where Pay resumes the same order; it never drafts a second checkout.
+- **Texting opt-in (`@everfur/sdk/texting`, `@everfur/sdk/web/texting`), new subpaths.** `EverfurTextingOptIn`,
+  `TextingController`, the phone helpers (`isE164`, `toTextingE164`, `parseTextingProfile`, `formatTextingPhone`)
+  and `copy` / `brandCopy` overrides over `TEXTING_COPY` and `TEXTING_BRAND_COPY`.
+- **Health Plan (`@everfur/sdk/health-plan`, `@everfur/sdk/web/health-plan`), new subpaths.** `EverfurHealthPlan`,
+  `HealthPlanItemCard`, `HealthPlanCartBar`, `HealthPlanController`, the cart dock (`HealthPlanCartScope`,
+  `useHealthPlanCartDock`) and the `cartBar`, `planCard` and `planReasonLabel` slots, with slot keys matched to the
+  backend paint keys. Generic styling hooks; defaults unchanged.
+- **Server helpers on `@everfur/sdk/server`:** `sendMemberText`, `replaceCatalog` (opt-in `confirmEmpty` and
+  `confirmShrink`) and `mergeCatalog`. The catalog replace's `catalog_empty_refused` and `catalog_shrink_refused` 409s fold to
+  `validationFailed`.
+- Chat starter prompts, header and empty header slots; records page upcoming care and history tiles;
+  `useUpcomingTelevetVisit`. The `linked_account_read_only` 409 folds to `conflict`.
+- `EverfurChat` `initialAskKey` lets an initial ask repeat and survive a chat that is not ready yet. The televet frame
+  protocol carries optional `petName` and `ownerName`.
+- **Records sheet on its own entry (`@everfur/sdk/web/records-sheet`).** `recordsSheet(options)` builds the v3
+  records sheet and its lab result screen for `EverfurRecordsPage`'s `sheet` prop. The sheet code left
+  `@everfur/sdk/web/records`, so a records page without the sheet downloads none of it. The `sheet` prop now takes
+  the built sheet (`EverfurRecordsSheet`) instead of the options; `EverfurRecordsSheetOptions`,
+  `EverfurRecordsLabDetail` and the sheet's style exports moved to the new entry.
+- **Health Plan cart, quantities and order tracking (`@everfur/sdk/web/health-plan`).** With Everfur checkout the
+  shop's cart checks several products and boxes out in one session (`startCartCheckout`, items[] with quantity),
+  falls back to one product per checkout on `409 cart_disabled` (`healthPlanCheckoutRefusal`), and keeps a
+  subscription for its own checkout. The return lists every order (`HealthPlanCheckoutState.orders`, each with
+  `quantity` and `total`). Orders draw the partner's tracking (`HealthPlanOneBoxOrder.tracking`) and page through
+  `listOneBoxOrderPage`. New copy keys `cartSubscriptionApart`, `placedArrives`, `moreOrders`, `trackLink`.
+- **Chat send button (`chat_send_button` presentation field, web).** `always_dark` (the default) draws Send dark
+  even while the box is empty; `dim_when_empty` keeps the earlier dim look.
+- **Health Plan focus layout shows the whole plan (`@everfur/sdk/web/health-plan`).** After the pick, the pet's other
+  plan items follow in plan order as product cards, each with its own Buy one box: the partner's handoff (`onBuy`, else
+  `onCheckout([item])`), or a one-box Stripe Checkout for that item when the plan page says
+  `checkout: "everfur_stripe"`; each press sends `health_plan.checkout_started`. New `HealthPlanFocusProps.others`
+  and the `others` and `other` parts in `HealthPlanFocusClassNames`; the cards reuse the pick's parts. A host
+  `design` with a pick shows the others too.
+- **Health Plan page and Everfur checkout (`@everfur/sdk/web/health-plan`), opt-in.** `EverfurHealthPlan` with
+  `focus` options and no `design` reads the pet's plan page (`GET .../plan/page`) and draws the focus layout from it;
+  `focus`, `routine` and `signs` are now optional in `HealthPlanFocusDesign`. When the page says
+  `checkout: "everfur_stripe"`, Buy one box and Subscribe redirect to Stripe Checkout and the return polls the
+  checkout into the started screen. New `focus.copy`, `focus.navigate`, `focus.pageRepository`,
+  `useHealthPlanPage`, `createHealthPlanPageRepository` and the page wire mappers (also on
+  `@everfur/sdk/health-plan`). A host `design` and `checkout: "partner"` behave as before.
+- **Health Plan subscriptions on the web (`@everfur/sdk/web/health-plan`), all opt-in.** `EverfurHealthPlan`
+  takes a `focus` design (one recommended product, the host's words) and, with `subscriptions`, reads the quote:
+  every 60, 90 or 120 days, first box vs regular price, buy one box, a confirm sheet with the renewal terms, and
+  manage (change interval, skip, cancel, restart). A 404 quote hides all of it and keeps the one-time checkout
+  handoff. Writes carry an Idempotency-Key per tap. Follows EFBackend PR #2131 (switch
+  `partner.shop_subscriptions_enabled`, off by default).
+- **Layout settings from the console (`render_hints.branding.presentation`), all opt-in.** Eleven fields (answer
+  style, history style, top card, follow-up count and televet exclusion, composer mic and upload, disclaimer
+  placement, Health Plan layout, two records options) resolved per field: an explicit prop wins, a field locked as
+  `presentation` or `presentation.<field>` stays with the console. Absent means today's behavior. New
+  `EverfurChat` props `presentation`, `answerCards` (answer cards with sources and feedback), `topCard` and
+  `historySheet` (a bottom sheet with previews), `EverfurHealthPlan` `presentation`, and
+  `useEverfurPresentation`. The `focus` design now draws only while `health_plan_layout` is `focus_plan`.
+- Layout settings, round 2 (EFBackend #2132): `chatComposerStyle` (`compact`), `chatComposerPlaceholder`
+  (`pet_name`), `chatHistoryBar` (`scroll`) and `chatGeneralBanner` (`false` hides only the general banner), same
+  precedence and defaults (no change unless set). An answer card can carry `render` (the host card slot).
+- `ChatConversation.preview` (the conversation list's last answer, up to 140 characters) when the server sends it.
+- `HealthPlanTopRisk` and `NotificationStack` (web) for a host's own risk card and push list.
+- `EverfurChat` `renderEmptyHeader`, `emptyState` (title and part classNames for the empty start), `followUpPolicy`, `historyBar` and `initialAskCard`.
+- Server events: `health_plan.box_due` and `health_plan.one_box_ordered`, webhook only, with typed payloads.
+- **Health Plan funnel events on your `telemetry` port.** `health_plan.opened`, `health_plan.product_clicked` and
+  `health_plan.checkout_started`, with pet and product ids, counts and the cart total only. Nothing is sent without
+  a `telemetry` sink. Documented in chapter 18.
+
+### Fixed
+
+- A `409 records_consent_required` on the request documents read no longer shows the generic conflict line with a
+  retry; the list renders nothing, as when empty.
+- The Health Plan kicker and price line no longer read "Ships every 0 days" without a subscription quote; they use the
+  existing ships-once copy.
+- The Health Plan focus layout's buy button sends `health_plan.checkout_started`.
+- Partner tabs audit fixes: cards-mode chat answers keep line breaks and lists; the web thread refreshes on return
+  under the default browser lifecycle; the history bar count waits for the full list; the televet follow-up filter
+  matches only visit phrases; the records consent grant has a busy state and shows errors; documents sort newest
+  first; the marker carousel puts the featured marker first; the texting resend keeps the code step; the Health Plan
+  revalidates quietly on return.
+- **A Health Plan partner with no plan page keeps its plan.** In the focus layout, a plan with products whose plan
+  page is missing (404), null or refused draws the standard product list with its cart and the host's `onCheckout`
+  (web and React Native), and says available. Only a plan with no products is no plan.
+- **One plan page read per pet.** The chat's focus card, the records sheet and the Health Plan share one in-flight
+  `GET .../plan/page` and its answer for 5 seconds; a retry or a re-read after a write is fresh. The chat (web and
+  React Native) and the React Native records sheet read it only with the `healthPlan` capability.
+- **React Native Everfur checkout without a return URL.** Buy keeps the partner's handoff instead of drawing nothing.
+- **v3 colours on any partner palette.** The link ink, the badge ink and the labels on primary and accent read at
+  4.5:1 on Raph's card, paper and tile for every partner palette; Everfur's own values are unchanged.
+- **Consent required is no longer a dead end on `EverfurRecordsPage` and `EverfurRecordsDashboard`.** The grant
+  gates reading record content only, so with the read answering consent required the page keeps its header
+  (`Request records`, the upload action) and its requests section with the upload prompt, and the dashboard keeps
+  the first-record prompt or the in-progress card with their ways to add records. `Allow` with the consent text is
+  drawn under them only when a `consentVersion` was passed. Before, both drew only "Consent required".
+
 ## [0.12.1] - 2026-10-08
 
 ### Changed

package/README.md

@@ -10,7 +10,7 @@ features without shipping an app update.
   a blank screen, and cannot be force-enabled client-side.
 - The app never holds a secret. See [The security model](#the-security-model).
 
-> `0.12.1`, MIT licensed, public on npm. Requires React Native `>=0.74` (or React `>=18` with `react-dom`
+> `0.13.0`, MIT licensed, public on npm. Requires React Native `>=0.74` (or React `>=18` with `react-dom`
 > for the web entry), and Node `>=18` on the backend that mints sessions.
 
 <!-- DRAFT COPY slot PD1-2 (owner): the README's invitation to get started (self-serve sandbox sign-up), in the owner's words. The factual paragraph below stands without it. -->
@@ -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,15 +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` | 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;
@@ -214,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-CgYQdfqi.d.ts → Chat.d-aycmX1CA.d.cts}

@@ -1,16 +1,143 @@
 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-CVi3n0re.js';
-import { W as WidgetPet, P as PetProfileInput } from './petsRepository-CoRa3C_U.js';
-import { U as UrgencyDisplayLevel, L as LifecyclePort, E as EverfurChatDraftStore } from './attachments-DkMrKCIU.js';
+import { P as PetRef, C as ConversationId } from './ids.d-B2GAAifq.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. */
 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 };