npm - sos-portal-components-react - Versions diffs - 0.3.4 → 0.4.0 - Mend

sos-portal-components-react 0.3.4 → 0.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (4) hide show

package/CHANGELOG.md +163 -145
package/README.md +233 -233
package/dist/encounter-journey.css +91 -91
package/package.json +111 -110

package/CHANGELOG.md CHANGED Viewed

@@ -1,145 +1,163 @@
-# Changelog
-## Unreleased
-## 0.3.4 - 2026-11-12
-- Render provider-supplied organization/service labels for authorized foreign history without exposing service-reference internals or mutation controls.
-- Keep other-organization Encounter history read-only in the shared journey action selector. Document consent-free professional encounter traceability, scoped history read grants and the full IPS permission catalog.
-## 0.3.3 - 2026-11-11
-- Add controlled, host-authorized Encounter journey and transfer components, including persisted response validation and read-only Personal presentation. Retain the UHC transfer console through a compatibility wrapper.
-- Recover the shared person/animal clinical-section, permission and US Core STU6 contract; distinguish existing views from the pending complete example lifecycle.
-## 0.3.2 - 2026-11-10
-- Add controlled `SubjectCardLocatorFields` for card-number or DID/QR entry.
-  Number entry distinguishes person/animal and animal taxonomy, including
-  species beyond the supplied presets. Hosts provide labels/options and own
-  resolution and authorization; the fields select no mode, storage or provider.
-## 0.3.1 - 2026-11-09
-- Add a persisted RTC completion signal for local/remote hangup and injected
-  canonical terminal-state observation. Release tracks, de-duplicate end
-  requests, preserve retryable history failures and cancel invitations after
-  connection failure. Load browser media capability before issuing a grant.
-- Add shared account-level push registration controls with explicit enable,
-  current-browser disable, other-device revocation and unavailable/denied
-  states. Permission requests, transports, identity and persistence remain in
-  the host adapters.
-- Add one controlled emergency-contact card directory with separate controller
-  context, primary-recipient presentation and injected add/remove/priority
-  operations. It owns no storage or authority and can render the same state
-  across execution modes; native rendering remains a separate adapter.
-- Specify the complete created-card emergency acceptance journey under the
-  existing Tuskr IDs: My card, dependent/controller/contact defaults, pasted
-  identifier/manual tuple/camera/image intake, linked-identifier discovery,
-  Encounter-scoped contact and RTC, recipient-card history, exceptional access
-  and ambulance/hospital handover. Distinguish requirements from executed
-  evidence and isolated media cases from full lifecycle acceptance.
-## 0.3.0 - 2026-11-08
-- Export shared device-assistance preferences through an independent SOS entry,
-  delegating its controlled web renderer to Antifraud 0.3.0. Keep runtime,
-  capability detection, storage and authorization in the owning application.
-  Native preferences rendering is not implemented by this release.
-- Typecheck, build and the independent export smoke pass. Cross-application
-  phone-authenticated browser checks belong to the CH acceptance evidence.
-- List the three implemented runtime exports separately from the acceptance
-  catalogue. Base shell/profile/card extraction from the existing domain
-  package remains pending; controller administration has a separate owner.
-- Specify shared subject-control placement, semantic option/action colours,
-  account-menu versus subject-device grants, appearance namespace parity and
-  separate model enablement/availability/preparation states in the existing
-  Tuskr cases. These are acceptance requirements, not new runtime readiness.
-- Correct the shared acceptance guides to use the selected simulated-phone
-  tests without mailbox access. Treat current email-only Organization/employee
-  contracts as an implementation gap; preserve official-source verification,
-  independent profile authority and existing GW/DID behavior.
-- Replace the dated developer handoff with numbered, README-linked guides for
-  generic portal modes/authentication and detailed cross-portal Tuskr cases.
-  Preserve the existing `SOS-PORTAL-001`-`029` and specialist research IDs.
-- Distinguish public Demo real-email account login from fixed Firebase test
-  phone fixtures, BFF-owned Demo persistence from Test Network authority/GW
-  lifecycle, and dedicated RTC media from Communication history and assistants.
-- Document positive/negative Personal ? Professional journeys, both-side
-  readback, profile/relationship revocation, sector variants and evidence
-  boundaries without claiming unexecuted gates have passed.
-- Specify dependency-by-case progression: BFF/memory Demo first, independent
-  terminology-cache and RTC additions, and memory-GW -> local Fabric ->
-  online Test Network acceptance for network cases. Retain green evidence and
-  rerun only failed/affected gates while closing the cumulative release set.
-## 0.2.3 - 2026-11-07
-- Render caller-cancelled Communications as `Cancelled`/`Cancelada` rather
-  than collapsing them into an undefined or generic ended state.
-- Let the host distinguish a caller cancellation from an unanswered timeout
-  when ending an RTC session; media teardown remains separate from canonical
-  Communication persistence.
-## 0.2.2 - 2026-11-07
-- Render the canonical ringing, missed and ended state beside every call
-  Communication in the shared Personal/Professional conversation surface.
-  Host portals no longer need divergent status labels to expose call history.
-## 0.2.1 - 2026-11-07
-- Pin `sos-data-utils-ts@0.6.28`, the exact release that owns the portal RTC
-  Communication contract consumed by `createLiveKitRealtimeCallClient`. Clean npm
-  installs no longer retain a nested pre-RTC data-utils release.
-## 0.2.0 - 2026-11-07
-- Establish this package as the shared presentation boundary consumed directly
-  by CH Personal and Professional in every flavour. Product portals provide
-  authorization, policy and BFF adapters; UHC compatibility exports no longer
-  own the active implementation.
-- Export `SubjectConversationChat` as the single subject-channel renderer over
-  canonical Communications. It projects text, governed attachments, clinical
-  Bundles, ICS/files, audio and call events without owning persistence,
-  signaling or recipient authority.
-- Export `createLiveKitRealtimeCallClient` as a dynamically loaded web RTC adapter
-  designed for later Expo substitution. It consumes only the short grant
-  issued by the BFF and never receives LiveKit API credentials.
-- Separate CH all-local, telephone-assistant, optional web-assistant and RTC
-  integration profiles. Calls use a host-injected dedicated RTC client while
-  invitations, terminal events and unanswered audio render as Communications.
-## 0.1.2 - 2026-11-07
-- Document and enforce one shared UI contract for Demo, Test Network, web and
-  Expo; presentation components never select a persistence adapter.
-## 0.1.1 - 2026-11-06
-- Document the GitHub organization handoff, BFF-validated synthetic Demo
-  boundary, scoped storage contract and two-browser call verification flow.
-## 0.1.0 - 2026-11-06
-- Establish the shared cross-sector portal-component boundary.
-- Publish the initial Tuskr-ready use-case catalogue covering shell, access,
-  cards, identity, encounters, communications, appointments, relationships,
-  calls, clinical documents, permissions and lifecycle composition.
-- Add the Personal/Professional communications matrix for card-root channels,
-  relationship child threads and persisted audio/video call-event states.
-- Keep host/tenant controller governance in Antifraud Hosting and leave
-  research/genomics outside the initial core until their package boundary is
-  decided.
-- Add the canonical `SubjectConversationChat` React Native/Web adapter over
-  Antifraud's neutral conversation surface and SOS subject-conversation
-  contracts, including text, governed attachments, FHIR documents and call
-  events without moving authorization or delivery into React.
+# Changelog
+## Unreleased
+## 0.4.0 - 2026-11-14
+- Verify the full 33 component tests and three required dependency contracts,
+  typecheck/build, source/emitted privacy and all six JavaScript public entries
+  plus CSS against the independent registry cohort. This release preserves
+  the existing shared API; it does not incorporate UHC components.
+- Require the independent dependency gate in the normal check: reject GDC
+  declarations and aliases, source/declaration/emitted imports or re-exports,
+  and every transitive registry lock entry.
+- Consume the published FHIR and SOS Data 0.7 contracts through registry-only
+  dependencies, preserving the shared UI API and the existing neutral
+  Antifraud renderer.
+- Pin the reviewed SOS Data contract version used by the shared journey
+  renderer so dependency resolution does not reinstall an older catalog.
+## 0.3.4 - 2026-11-12
+- Render provider-supplied organization/service labels for authorized foreign history without exposing service-reference internals or mutation controls.
+- Keep other-organization Encounter history read-only in the shared journey action selector. Document consent-free professional encounter traceability, scoped history read grants and the full IPS permission catalog.
+## 0.3.3 - 2026-11-11
+- Add controlled, host-authorized Encounter journey and transfer components, including persisted response validation and read-only Personal presentation. Retain the UHC transfer console through a compatibility wrapper.
+- Recover the shared person/animal clinical-section, permission and US Core STU6 contract; distinguish existing views from the pending complete example lifecycle.
+## 0.3.2 - 2026-11-10
+- Add controlled `SubjectCardLocatorFields` for card-number or DID/QR entry.
+  Number entry distinguishes person/animal and animal taxonomy, including
+  species beyond the supplied presets. Hosts provide labels/options and own
+  resolution and authorization; the fields select no mode, storage or provider.
+## 0.3.1 - 2026-11-09
+- Add a persisted RTC completion signal for local/remote hangup and injected
+  canonical terminal-state observation. Release tracks, de-duplicate end
+  requests, preserve retryable history failures and cancel invitations after
+  connection failure. Load browser media capability before issuing a grant.
+- Add shared account-level push registration controls with explicit enable,
+  current-browser disable, other-device revocation and unavailable/denied
+  states. Permission requests, transports, identity and persistence remain in
+  the host adapters.
+- Add one controlled emergency-contact card directory with separate controller
+  context, primary-recipient presentation and injected add/remove/priority
+  operations. It owns no storage or authority and can render the same state
+  across execution modes; native rendering remains a separate adapter.
+- Specify the complete created-card emergency acceptance journey under the
+  existing Tuskr IDs: My card, dependent/controller/contact defaults, pasted
+  identifier/manual tuple/camera/image intake, linked-identifier discovery,
+  Encounter-scoped contact and RTC, recipient-card history, exceptional access
+  and ambulance/hospital handover. Distinguish requirements from executed
+  evidence and isolated media cases from full lifecycle acceptance.
+## 0.3.0 - 2026-11-08
+- Export shared device-assistance preferences through an independent SOS entry,
+  delegating its controlled web renderer to Antifraud 0.3.0. Keep runtime,
+  capability detection, storage and authorization in the owning application.
+  Native preferences rendering is not implemented by this release.
+- Typecheck, build and the independent export smoke pass. Cross-application
+  phone-authenticated browser checks belong to the CH acceptance evidence.
+- List the three implemented runtime exports separately from the acceptance
+  catalogue. Base shell/profile/card extraction from the existing domain
+  package remains pending; controller administration has a separate owner.
+- Specify shared subject-control placement, semantic option/action colours,
+  account-menu versus subject-device grants, appearance namespace parity and
+  separate model enablement/availability/preparation states in the existing
+  Tuskr cases. These are acceptance requirements, not new runtime readiness.
+- Correct the shared acceptance guides to use the selected simulated-phone
+  tests without mailbox access. Treat current email-only Organization/employee
+  contracts as an implementation gap; preserve official-source verification,
+  independent profile authority and existing GW/DID behavior.
+- Replace the dated developer handoff with numbered, README-linked guides for
+  generic portal modes/authentication and detailed cross-portal Tuskr cases.
+  Preserve the existing `SOS-PORTAL-001`-`029` and specialist research IDs.
+- Distinguish public Demo real-email account login from fixed Firebase test
+  phone fixtures, BFF-owned Demo persistence from Test Network authority/GW
+  lifecycle, and dedicated RTC media from Communication history and assistants.
+- Document positive/negative Personal ? Professional journeys, both-side
+  readback, profile/relationship revocation, sector variants and evidence
+  boundaries without claiming unexecuted gates have passed.
+- Specify dependency-by-case progression: BFF/memory Demo first, independent
+  terminology-cache and RTC additions, and memory-GW -> local Fabric ->
+  online Test Network acceptance for network cases. Retain green evidence and
+  rerun only failed/affected gates while closing the cumulative release set.
+## 0.2.3 - 2026-11-07
+- Render caller-cancelled Communications as `Cancelled`/`Cancelada` rather
+  than collapsing them into an undefined or generic ended state.
+- Let the host distinguish a caller cancellation from an unanswered timeout
+  when ending an RTC session; media teardown remains separate from canonical
+  Communication persistence.
+## 0.2.2 - 2026-11-07
+- Render the canonical ringing, missed and ended state beside every call
+  Communication in the shared Personal/Professional conversation surface.
+  Host portals no longer need divergent status labels to expose call history.
+## 0.2.1 - 2026-11-07
+- Pin `sos-data-utils-ts@0.6.28`, the exact release that owns the portal RTC
+  Communication contract consumed by `createLiveKitRealtimeCallClient`. Clean npm
+  installs no longer retain a nested pre-RTC data-utils release.
+## 0.2.0 - 2026-11-07
+- Establish this package as the shared presentation boundary consumed directly
+  by CH Personal and Professional in every flavour. Product portals provide
+  authorization, policy and BFF adapters; UHC compatibility exports no longer
+  own the active implementation.
+- Export `SubjectConversationChat` as the single subject-channel renderer over
+  canonical Communications. It projects text, governed attachments, clinical
+  Bundles, ICS/files, audio and call events without owning persistence,
+  signaling or recipient authority.
+- Export `createLiveKitRealtimeCallClient` as a dynamically loaded web RTC adapter
+  designed for later Expo substitution. It consumes only the short grant
+  issued by the BFF and never receives LiveKit API credentials.
+- Separate CH all-local, telephone-assistant, optional web-assistant and RTC
+  integration profiles. Calls use a host-injected dedicated RTC client while
+  invitations, terminal events and unanswered audio render as Communications.
+## 0.1.2 - 2026-11-07
+- Document and enforce one shared UI contract for Demo, Test Network, web and
+  Expo; presentation components never select a persistence adapter.
+## 0.1.1 - 2026-11-06
+- Document the GitHub organization handoff, BFF-validated synthetic Demo
+  boundary, scoped storage contract and two-browser call verification flow.
+## 0.1.0 - 2026-11-06
+- Establish the shared cross-sector portal-component boundary.
+- Publish the initial Tuskr-ready use-case catalogue covering shell, access,
+  cards, identity, encounters, communications, appointments, relationships,
+  calls, clinical documents, permissions and lifecycle composition.
+- Add the Personal/Professional communications matrix for card-root channels,
+  relationship child threads and persisted audio/video call-event states.
+- Keep host/tenant controller governance in Antifraud Hosting and leave
+  research/genomics outside the initial core until their package boundary is
+  decided.
+- Add the canonical `SubjectConversationChat` React Native/Web adapter over
+  Antifraud's neutral conversation surface and SOS subject-conversation
+  contracts, including text, governed attachments, FHIR documents and call
+  events without moving authorization or delivery into React.

package/README.md CHANGED Viewed

@@ -1,233 +1,233 @@
-# SOS Portal Components React
-## Numbered engineering guides
-1. [00 — Documentation index](docs/00-INDEX.md)
-2. [01 — Portal modes, authentication and authority](docs/01-PORTAL_MODES_AND_AUTH.md)
-3. [02 — Cross-portal Tuskr cases](docs/02-CROSS_PORTAL_TUSKR_CASES.md)
-Read these with the owning CH application's README for runnable commands and
-flavour configuration. The cases below retain their stable IDs; the numbered
-guides supply cross-portal steps, expected results and negative checks.
-Start dependencies by use case: local Demo UI/BFF uses the memory vault and
-no GW; clinical coding/cache cases add Terminology through its SDK, and call
-cases add LiveKit independently. Network cases progress from GW memory/test
-to local Fabric, then the chosen online `dev:staging` Test Network flavours.
-Demo stays BFF-only throughout. See the
-[dependency table](docs/01-PORTAL_MODES_AND_AUTH.md#11-start-dependencies-for-the-case-being-tested).
-Rerun the smallest failed/affected gate while retaining valid green evidence;
-release closure still requires every affected boundary.
-## Runtime parity
-`SubjectCardLocatorFields` is a controlled web input, exported separately at
-`sos-portal-components-react/subject-card-locator-fields`. It distinguishes
-card number from DID/QR entry. For numbers, the user chooses person or animal;
-animals also choose a supplied species or enter another NCBI taxonomy ID.
-The host verifies those hints against the registered card. DID/QR lookup uses
-the registered identity without asking the user to reinterpret its species.
-The same renderer works in Demo and Network; it provides no authorization or
-persistence and requires a native renderer before use in Expo.
-Components share use-case state between Demo and Test Network. Native support
-is export-specific: conversation uses the React Native/Web adapter; the device
-preferences renderer currently uses web DOM. A native preferences renderer
-remains future work. Components never select storage. Applications inject memory for
-all-local, Expo SQLite for native, or an explicit durable adapter. Firestore
-must not create a Demo-only component or data model.
-CH all-local portal execution does not start or require Chat, the telephone
-assistant or the optional web assistant. Realtime audio/video is a dedicated
-RTC boundary supplied by the host BFF. Invitations, terminal states and an
-optional unanswered audio attachment are rendered from Communications.
-Shared portal UI for base components. It provides the portal UI core for
-personal and professional applications across human
-health, animal care, public safety, emergency response and other configured
-sectors. The package exists to prevent each sector flavour from reimplementing
-the same shell, access journey, card navigation and governed subject workflows.
-Public Demo authenticates a real email account and uses BFF-validated synthetic
-profiles. Fixed Firebase test-phone codes belong only to tests in ignored
-configuration, never public Demo access. Demo business state stays behind the
-BFF Confidential Storage boundary; Test Network separately proves the complete
-organization/employee/subject lifecycle through its real authority and GW.
-The first implementation of a workflow may be proven in the animal-care
-portals. That does not make every future human-health consumer depend
-permanently on an animal-care component. Promotion into this package happens
-only after the shared contract is understood. Research, genomics and other
-specialist areas remain in their current package until their long-term
-boundary is deliberately chosen.
-## Ownership boundaries
-- This package owns reusable portal presentation and controlled user intents.
-- Applications own branding, routes, environment selection, BFF calls and
-  server-resolved sector/role policy.
-- `antifraud-hosting-components-react` owns neutral host- and
-  tenant-controller administration. SOS may compose it but does not fork it.
-- `antifraud-portal-components-react` owns neutral evidence and conversation
-  primitives used beyond health.
-- `terminology-components-react` owns terminology controls; the terminology
-  service and SDK own canonical systems, releases and searches.
-- FHIR/SOS/Vet data utilities and SDKs own data contracts, validation,
-  transport, signatures and persistence. React never derives authority.
-- Sector packages own their human-health, animal-care and other
-  domain-specific extensions.
-Browser state, a visible tab or a selected role never grants authority. Every
-protected action is enabled from trusted host capabilities and remains
-revalidated by the BFF/Gateway.
-## Implemented exports
-This is the current runtime inventory, not completion of the whole catalogue:
-| Export | Owner / responsibility |
-| --- | --- |
-| `EncounterJourneyPanel` | Controlled create/status/transfer and read-only saved journey; BFF callbacks own authority and persistence. |
-| `EncounterTransferConsole` | Shared transfer presentation; UHC retains a deprecated compatibility wrapper. |
-| `SubjectConversationChat` | SOS projection of authorized subject Communications into the neutral Antifraud conversation renderer. |
-| `createLiveKitRealtimeCallClient` | Host-configured RTC client adapter; the BFF retains authorization, credentials and Communication persistence. |
-| `useRealtimeCallSessionLifecycle` | Shared persisted-end observation and profile-owned session cleanup for Personal and Professional, including React Strict Mode replay. |
-| `DeviceAssistancePreferences` | Reexport of Antifraud's controlled web preferences renderer. |
-| `PushNotificationRegistration` | Controlled browser-registration status, explicit enable and per-device revoke actions. The host owns permission, subscription/token, verified identity, BFF and transport. |
-| `EmergencyContactCardDirectory` | Controlled card-linked emergency recipients and primary priority; host callbacks retain contact mutation, controller authority and persistence. |
-The complete base-UI extraction is still pending. `PortalHeader`,
-`PortalSettingsPanel`, profile protection, subject/card navigation and several
-contact, permission and clinical controls remain in
-`uhc-portal-components-react`; application composition also remains in the
-owning portals. Research stays there pending its future owner. The catalogue
-below is acceptance scope and must not be read as an implemented export list.
-Controller administration is owned separately by
-`antifraud-hosting-components-react`.
-- `sos-portal-components-react/device-assistance-preferences` reexports the
-  controlled `DeviceAssistancePreferences` owned by the neutral Antifraud
-  package. Import `antifraud-portal-components-react/device-assistance-preferences.css`
-  once in the application shell. It separates consent, runtime availability
-  and explicit preparation; hosts supply localized labels, storage and runtime
-  adapters. Rendering/toggling does not prepare a model or grant subject access.
-  Use this independent entry on account pages to avoid loading conversation
-  and RTC modules. Do not fork another device preferences panel per flavour.
-- `sos-portal-components-react/subject-conversation-chat` provides the
-  canonical React Native/Web adapter for an already-authorized subject
-  conversation. It projects the stable SOS entry model into the neutral
-  Antifraud conversation surface backed by
-  `@kesha-antonov/react-native-chat`. Hosts retain BFF delivery, attachment
-  opening, FHIR rendering, WebRTC signaling and authorization.
-The compatibility export currently present in the human-health component
-package is deprecated and will delegate to this package while consumers move
-to the SOS-owned path.
-## Tuskr use-case catalogue
-The stable IDs below are intended to become Tuskr cases. Each case must be
-executed for every applicable flavour, actor, viewport and environment. Demo
-uses synthetic state and must say so; Test Network and Production must use
-their real authorized BFF path.
-Use [02 — Cross-portal Tuskr cases](docs/02-CROSS_PORTAL_TUSKR_CASES.md)
-for Personal ↔ Professional prerequisites, numbered actions, both-side
-readback, rejected access, reset/revocation and execution evidence. A documented
-case is an acceptance target, not an end-to-end pass claim.
-| ID | Area | Governed journey and acceptance target |
-|---|---|---|
-| SOS-PORTAL-001 | Shell | Render the shared top bar, brand slot, account/profile menu, current subject and responsive navigation without flavour-specific forks. |
-| SOS-PORTAL-002 | Entry | Choose an enabled Demo, Test Network or Production entry supplied by trusted host configuration; a browser choice never selects network infrastructure. |
-| SOS-PORTAL-003 | Sign-in | Sign in through the host adapter, restore the exact protected profile and reject a profile belonging to another access path. |
-| SOS-PORTAL-004 | Biometrics | Unlock a protected profile with platform biometrics/passkey when available and use the governed PIN/password recovery fallback without exposing keys to React. |
-| SOS-PORTAL-005 | Registration | Register or accept an invitation for the applicable person, professional or animal-responsible profile; registration alone grants no subject access. |
-| SOS-PORTAL-006 | Cards | List only server-authorized individual or animal cards, select one card and preserve its stable identifier across navigation/reload. |
-| SOS-PORTAL-007 | Card sections | Resolve card sections from subject kind, sector, role and backend capabilities; hidden or read-only sections cannot be enabled by URL or browser state. |
-| SOS-PORTAL-008 | Identity | View and edit the permitted identity fields, provenance and attestations for a selected card while preserving immutable identifiers. |
-| SOS-PORTAL-009 | Related entities | Add, view, update or remove authorized related people, animals and organizations with explicit relationship type and provenance. |
-| SOS-PORTAL-010 | Contacts | Manage ordinary and emergency contacts independently, including priority, relationship, availability and emergency-only disclosure. |
-| SOS-PORTAL-011 | Encounters | List, open and author permitted encounters; bind contributions to the acting professional, organization, subject and server-confirmed scope. |
-| SOS-PORTAL-012 | Communications | Render one canonical conversation of DIDComm/FHIR Communications with text and governed attachments such as Bundles, documents, ICS, images and audio in both Personal and an authorized Professional card channel. |
-| SOS-PORTAL-013 | Calls | Initiate and display authorized audio/video calls and outgoing, incoming, completed, rejected, cancelled or missed call events without treating call signaling as clinical authority. |
-| SOS-PORTAL-014 | Appointments | Search availability and create, update or cancel appointments for applicable services, including blood-donation centres and other scheduled providers. |
-| SOS-PORTAL-015 | Clinical viewer | View authorized clinical documents, IPS summaries, sections, timelines and source/provenance details for human or animal cards. |
-| SOS-PORTAL-016 | Clinical authoring | Create and edit clinical documents through the canonical section-based editor, including encounters, observations, immunizations and host-enabled sections. |
-| SOS-PORTAL-017 | Credentials | Create, display, scan and verify supported health/data-card credentials and QR transports while keeping signing and verification outside React. |
-| SOS-PORTAL-018 | Permissions | View and change only permitted Consent/access relationships, group memberships and card grants; notifications never substitute for authorization. |
-| SOS-PORTAL-019 | Employee lifecycle | Compose the canonical Antifraud Hosting workforce screen for invitations, licences, employees and devices; SOS supplies sector labels and adapters, not a duplicate implementation. |
-| SOS-PORTAL-020 | Individual members | Manage an individual's authorized members/delegates separately from organization employees, with explicit lifecycle and revocation. |
-| SOS-PORTAL-021 | Emergency access | Show protected emergency data and request governed exceptional/break-glass access with reason, expiry, audit and clear post-access state. |
-| SOS-PORTAL-022 | Subject index | Display real index-update Communications from authorized providers and open linked records without manufacturing parallel chat events. |
-| SOS-PORTAL-023 | Provider directory | Select authorized card/index, clinical, appointment or emergency providers from host-supplied directories without hard-coded flavour endpoints. |
-| SOS-PORTAL-024 | Accessibility | Complete every shared journey by keyboard and screen reader with visible focus, labelled controls, status announcements and responsive layouts. |
-| SOS-PORTAL-025 | Expo reuse | Render platform-neutral contracts in Expo Android/iOS adapters and web adapters while retaining one message/card/action model and host-owned native capabilities. |
-| SOS-PORTAL-026 | Preferences | Reuse one device/account Preferences surface across modes: appearance, text size, locale, accessibility and actual speech/language-model enablement/availability/preparation, with explicit disabled states and no implied subject authorization. |
-| SOS-PORTAL-027 | Failure safety | Fail closed on missing capabilities, expired sessions, invalid attachments, unavailable providers or rejected persistence and preserve an actionable, non-sensitive error. |
-| SOS-PORTAL-028 | Controller embedding | In CH Management, embed the published Antifraud controller components for groups, departments, workforce and memberships until controller access is removed from branded professional portals. |
-| SOS-PORTAL-029 | Conversation threads | Open the individual card's root channel and authorized child threads for members, related entities or emergency contacts; each thread keeps stable subject/relationship/participant identifiers, and contact status alone grants no message access. |
-### Communications execution matrix
-Tuskr must exercise `SOS-PORTAL-012`, `SOS-PORTAL-013` and
-`SOS-PORTAL-029` together:
-| Actor/surface | Root card channel | Authorized child thread | Required call events |
-|---|---|---|---|
-| Personal portal | View/send according to the individual's capability | Open a member, related-entity or emergency-contact thread only after the BFF confirms participation | outgoing, incoming, completed, rejected/cancelled and missed audio/video calls |
-| Professional portal | View/send in the selected individual's card channel only with professional subject scope | Open only child threads included in the professional's server-resolved scope | the same persisted call-event projection; no browser-manufactured duplicate |
-| Reload/cross-surface | Preserve stable channel, thread and message identifiers | Preserve the exact relationship reference and participant set | Personal and Professional render the same authorized event status and attachment metadata |
-Acceptance requires real persisted Communications (or the explicit synthetic
-Demo adapter), chronological projection without a parallel chat record, and
-negative tests proving that a contact listed for emergencies cannot enumerate
-or open a thread without separate authorization.
-## Tracked specialist integration cases
-These cases must remain visible in Tuskr and in CH while they are migrated,
-but they are not owned by the initial SOS core package.
-| ID | Current owner | Planned direction | Acceptance target |
-|---|---|---|---|
-| HEALTH-RESEARCH-001 | Human-health components / host adapter | Candidate for animal-care components | Create, update, activate and revoke a research study with server-confirmed controller or delegated authority. |
-| HEALTH-RESEARCH-002 | Human-health components / host adapter | Candidate for animal-care components | Search and add authorized research subjects without turning discovery into access. |
-| HEALTH-RESEARCH-003 | Human-health components / host adapter | Candidate for animal-care components | Import research data, map source fields, track jobs and review/reclassify/discard staged records. |
-| HEALTH-RESEARCH-004 | Human-health components / host adapter | Candidate for animal-care components | Manage research contracts, study invitations, subscriptions and governed data access separately from ordinary card permissions. |
-| HEALTH-RESEARCH-005 | Human-health components / host adapter | Undecided specialist package | Use transcription/edge models and future genomic workflows only through explicit capability, provenance and privacy policy. |
-The current source inventory still contains host-local research panels.
-Migration is complete only when consuming portals import their published
-human-health implementation and the local alternatives are deprecated.
-Group-management source already lives in
-the Antifraud Controller application; its controlled UI must be exported by
-the Antifraud Hosting component package before CH can remove its final local
-group adapter.
-## Explicitly outside the initial core
-- host registry, tenant admission and organization lifecycle policy (Antifraud
-  Controller/Hosting);
-- research-study administration, research-subject import and genomic workflows
-  (tracked above through their human-health to animal-care/specialist migration);
-- terminology databases and searches;
-- FHIR validation/conversion, DIDComm transport, wallets, signatures, QR
-  cryptography, WebRTC signaling and persistence;
-- application-specific routes, branding and deployment configuration.
-## Delivery order
-1. Inventory the current verified components in deprecated sector portals,
-   human-health components and consuming portal flavours.
-2. Add a contract test for one canonical component per use case.
-3. Move the current implementation without changing its data/authority
-   boundary, then switch all CH flavours to the published package.
-4. Mark old exports deprecated and keep their legacy tests separately runnable.
-5. Add web plus Expo adapters only where the same controlled contract is
-   genuinely reusable.
-6. Remove compatibility implementations only in a later breaking release.
-See [clinical sections, permissions and US Core contract](docs/03-CLINICAL_SECTIONS_AND_US_CORE_CONTRACT.md) for the recovered person/animal mappings and pending full example lifecycle.
+# SOS Portal Components React
+## Numbered engineering guides
+1. [00 — Documentation index](docs/00-INDEX.md)
+2. [01 — Portal modes, authentication and authority](docs/01-PORTAL_MODES_AND_AUTH.md)
+3. [02 — Cross-portal Tuskr cases](docs/02-CROSS_PORTAL_TUSKR_CASES.md)
+Read these with the owning CH application's README for runnable commands and
+flavour configuration. The cases below retain their stable IDs; the numbered
+guides supply cross-portal steps, expected results and negative checks.
+Start dependencies by use case: local Demo UI/BFF uses the memory vault and
+no GW; clinical coding/cache cases add Terminology through its SDK, and call
+cases add LiveKit independently. Network cases progress from GW memory/test
+to local Fabric, then the chosen online `dev:staging` Test Network flavours.
+Demo stays BFF-only throughout. See the
+[dependency table](docs/01-PORTAL_MODES_AND_AUTH.md#11-start-dependencies-for-the-case-being-tested).
+Rerun the smallest failed/affected gate while retaining valid green evidence;
+release closure still requires every affected boundary.
+## Runtime parity
+`SubjectCardLocatorFields` is a controlled web input, exported separately at
+`sos-portal-components-react/subject-card-locator-fields`. It distinguishes
+card number from DID/QR entry. For numbers, the user chooses person or animal;
+animals also choose a supplied species or enter another NCBI taxonomy ID.
+The host verifies those hints against the registered card. DID/QR lookup uses
+the registered identity without asking the user to reinterpret its species.
+The same renderer works in Demo and Network; it provides no authorization or
+persistence and requires a native renderer before use in Expo.
+Components share use-case state between Demo and Test Network. Native support
+is export-specific: conversation uses the React Native/Web adapter; the device
+preferences renderer currently uses web DOM. A native preferences renderer
+remains future work. Components never select storage. Applications inject memory for
+all-local, Expo SQLite for native, or an explicit durable adapter. Firestore
+must not create a Demo-only component or data model.
+CH all-local portal execution does not start or require Chat, the telephone
+assistant or the optional web assistant. Realtime audio/video is a dedicated
+RTC boundary supplied by the host BFF. Invitations, terminal states and an
+optional unanswered audio attachment are rendered from Communications.
+Shared portal UI for base components. It provides the portal UI core for
+personal and professional applications across human
+health, animal care, public safety, emergency response and other configured
+sectors. The package exists to prevent each sector flavour from reimplementing
+the same shell, access journey, card navigation and governed subject workflows.
+Public Demo authenticates a real email account and uses BFF-validated synthetic
+profiles. Fixed Firebase test-phone codes belong only to tests in ignored
+configuration, never public Demo access. Demo business state stays behind the
+BFF Confidential Storage boundary; Test Network separately proves the complete
+organization/employee/subject lifecycle through its real authority and GW.
+The first implementation of a workflow may be proven in the animal-care
+portals. That does not make every future human-health consumer depend
+permanently on an animal-care component. Promotion into this package happens
+only after the shared contract is understood. Research, genomics and other
+specialist areas remain in their current package until their long-term
+boundary is deliberately chosen.
+## Ownership boundaries
+- This package owns reusable portal presentation and controlled user intents.
+- Applications own branding, routes, environment selection, BFF calls and
+  server-resolved sector/role policy.
+- `antifraud-hosting-components-react` owns neutral host- and
+  tenant-controller administration. SOS may compose it but does not fork it.
+- `antifraud-portal-components-react` owns neutral evidence and conversation
+  primitives used beyond health.
+- `terminology-components-react` owns terminology controls; the terminology
+  service and SDK own canonical systems, releases and searches.
+- FHIR/SOS/Vet data utilities and SDKs own data contracts, validation,
+  transport, signatures and persistence. React never derives authority.
+- Sector packages own their human-health, animal-care and other
+  domain-specific extensions.
+Browser state, a visible tab or a selected role never grants authority. Every
+protected action is enabled from trusted host capabilities and remains
+revalidated by the BFF/Gateway.
+## Implemented exports
+This is the current runtime inventory, not completion of the whole catalogue:
+| Export | Owner / responsibility |
+| --- | --- |
+| `EncounterJourneyPanel` | Controlled create/status/transfer and read-only saved journey; BFF callbacks own authority and persistence. |
+| `EncounterTransferConsole` | Shared transfer presentation; UHC retains a deprecated compatibility wrapper. |
+| `SubjectConversationChat` | SOS projection of authorized subject Communications into the neutral Antifraud conversation renderer. |
+| `createLiveKitRealtimeCallClient` | Host-configured RTC client adapter; the BFF retains authorization, credentials and Communication persistence. |
+| `useRealtimeCallSessionLifecycle` | Shared persisted-end observation and profile-owned session cleanup for Personal and Professional, including React Strict Mode replay. |
+| `DeviceAssistancePreferences` | Reexport of Antifraud's controlled web preferences renderer. |
+| `PushNotificationRegistration` | Controlled browser-registration status, explicit enable and per-device revoke actions. The host owns permission, subscription/token, verified identity, BFF and transport. |
+| `EmergencyContactCardDirectory` | Controlled card-linked emergency recipients and primary priority; host callbacks retain contact mutation, controller authority and persistence. |
+The complete base-UI extraction is still pending. `PortalHeader`,
+`PortalSettingsPanel`, profile protection, subject/card navigation and several
+contact, permission and clinical controls remain in
+`uhc-portal-components-react`; application composition also remains in the
+owning portals. Research stays there pending its future owner. The catalogue
+below is acceptance scope and must not be read as an implemented export list.
+Controller administration is owned separately by
+`antifraud-hosting-components-react`.
+- `sos-portal-components-react/device-assistance-preferences` reexports the
+  controlled `DeviceAssistancePreferences` owned by the neutral Antifraud
+  package. Import `antifraud-portal-components-react/device-assistance-preferences.css`
+  once in the application shell. It separates consent, runtime availability
+  and explicit preparation; hosts supply localized labels, storage and runtime
+  adapters. Rendering/toggling does not prepare a model or grant subject access.
+  Use this independent entry on account pages to avoid loading conversation
+  and RTC modules. Do not fork another device preferences panel per flavour.
+- `sos-portal-components-react/subject-conversation-chat` provides the
+  canonical React Native/Web adapter for an already-authorized subject
+  conversation. It projects the stable SOS entry model into the neutral
+  Antifraud conversation surface backed by
+  `@kesha-antonov/react-native-chat`. Hosts retain BFF delivery, attachment
+  opening, FHIR rendering, WebRTC signaling and authorization.
+The compatibility export currently present in the human-health component
+package is deprecated and will delegate to this package while consumers move
+to the SOS-owned path.
+## Tuskr use-case catalogue
+The stable IDs below are intended to become Tuskr cases. Each case must be
+executed for every applicable flavour, actor, viewport and environment. Demo
+uses synthetic state and must say so; Test Network and Production must use
+their real authorized BFF path.
+Use [02 — Cross-portal Tuskr cases](docs/02-CROSS_PORTAL_TUSKR_CASES.md)
+for Personal ↔ Professional prerequisites, numbered actions, both-side
+readback, rejected access, reset/revocation and execution evidence. A documented
+case is an acceptance target, not an end-to-end pass claim.
+| ID | Area | Governed journey and acceptance target |
+|---|---|---|
+| SOS-PORTAL-001 | Shell | Render the shared top bar, brand slot, account/profile menu, current subject and responsive navigation without flavour-specific forks. |
+| SOS-PORTAL-002 | Entry | Choose an enabled Demo, Test Network or Production entry supplied by trusted host configuration; a browser choice never selects network infrastructure. |
+| SOS-PORTAL-003 | Sign-in | Sign in through the host adapter, restore the exact protected profile and reject a profile belonging to another access path. |
+| SOS-PORTAL-004 | Biometrics | Unlock a protected profile with platform biometrics/passkey when available and use the governed PIN/password recovery fallback without exposing keys to React. |
+| SOS-PORTAL-005 | Registration | Register or accept an invitation for the applicable person, professional or animal-responsible profile; registration alone grants no subject access. |
+| SOS-PORTAL-006 | Cards | List only server-authorized individual or animal cards, select one card and preserve its stable identifier across navigation/reload. |
+| SOS-PORTAL-007 | Card sections | Resolve card sections from subject kind, sector, role and backend capabilities; hidden or read-only sections cannot be enabled by URL or browser state. |
+| SOS-PORTAL-008 | Identity | View and edit the permitted identity fields, provenance and attestations for a selected card while preserving immutable identifiers. |
+| SOS-PORTAL-009 | Related entities | Add, view, update or remove authorized related people, animals and organizations with explicit relationship type and provenance. |
+| SOS-PORTAL-010 | Contacts | Manage ordinary and emergency contacts independently, including priority, relationship, availability and emergency-only disclosure. |
+| SOS-PORTAL-011 | Encounters | List, open and author permitted encounters; bind contributions to the acting professional, organization, subject and server-confirmed scope. |
+| SOS-PORTAL-012 | Communications | Render one canonical conversation of DIDComm/FHIR Communications with text and governed attachments such as Bundles, documents, ICS, images and audio in both Personal and an authorized Professional card channel. |
+| SOS-PORTAL-013 | Calls | Initiate and display authorized audio/video calls and outgoing, incoming, completed, rejected, cancelled or missed call events without treating call signaling as clinical authority. |
+| SOS-PORTAL-014 | Appointments | Search availability and create, update or cancel appointments for applicable services, including blood-donation centres and other scheduled providers. |
+| SOS-PORTAL-015 | Clinical viewer | View authorized clinical documents, IPS summaries, sections, timelines and source/provenance details for human or animal cards. |
+| SOS-PORTAL-016 | Clinical authoring | Create and edit clinical documents through the canonical section-based editor, including encounters, observations, immunizations and host-enabled sections. |
+| SOS-PORTAL-017 | Credentials | Create, display, scan and verify supported health/data-card credentials and QR transports while keeping signing and verification outside React. |
+| SOS-PORTAL-018 | Permissions | View and change only permitted Consent/access relationships, group memberships and card grants; notifications never substitute for authorization. |
+| SOS-PORTAL-019 | Employee lifecycle | Compose the canonical Antifraud Hosting workforce screen for invitations, licences, employees and devices; SOS supplies sector labels and adapters, not a duplicate implementation. |
+| SOS-PORTAL-020 | Individual members | Manage an individual's authorized members/delegates separately from organization employees, with explicit lifecycle and revocation. |
+| SOS-PORTAL-021 | Emergency access | Show protected emergency data and request governed exceptional/break-glass access with reason, expiry, audit and clear post-access state. |
+| SOS-PORTAL-022 | Subject index | Display real index-update Communications from authorized providers and open linked records without manufacturing parallel chat events. |
+| SOS-PORTAL-023 | Provider directory | Select authorized card/index, clinical, appointment or emergency providers from host-supplied directories without hard-coded flavour endpoints. |
+| SOS-PORTAL-024 | Accessibility | Complete every shared journey by keyboard and screen reader with visible focus, labelled controls, status announcements and responsive layouts. |
+| SOS-PORTAL-025 | Expo reuse | Render platform-neutral contracts in Expo Android/iOS adapters and web adapters while retaining one message/card/action model and host-owned native capabilities. |
+| SOS-PORTAL-026 | Preferences | Reuse one device/account Preferences surface across modes: appearance, text size, locale, accessibility and actual speech/language-model enablement/availability/preparation, with explicit disabled states and no implied subject authorization. |
+| SOS-PORTAL-027 | Failure safety | Fail closed on missing capabilities, expired sessions, invalid attachments, unavailable providers or rejected persistence and preserve an actionable, non-sensitive error. |
+| SOS-PORTAL-028 | Controller embedding | In CH Management, embed the published Antifraud controller components for groups, departments, workforce and memberships until controller access is removed from branded professional portals. |
+| SOS-PORTAL-029 | Conversation threads | Open the individual card's root channel and authorized child threads for members, related entities or emergency contacts; each thread keeps stable subject/relationship/participant identifiers, and contact status alone grants no message access. |
+### Communications execution matrix
+Tuskr must exercise `SOS-PORTAL-012`, `SOS-PORTAL-013` and
+`SOS-PORTAL-029` together:
+| Actor/surface | Root card channel | Authorized child thread | Required call events |
+|---|---|---|---|
+| Personal portal | View/send according to the individual's capability | Open a member, related-entity or emergency-contact thread only after the BFF confirms participation | outgoing, incoming, completed, rejected/cancelled and missed audio/video calls |
+| Professional portal | View/send in the selected individual's card channel only with professional subject scope | Open only child threads included in the professional's server-resolved scope | the same persisted call-event projection; no browser-manufactured duplicate |
+| Reload/cross-surface | Preserve stable channel, thread and message identifiers | Preserve the exact relationship reference and participant set | Personal and Professional render the same authorized event status and attachment metadata |
+Acceptance requires real persisted Communications (or the explicit synthetic
+Demo adapter), chronological projection without a parallel chat record, and
+negative tests proving that a contact listed for emergencies cannot enumerate
+or open a thread without separate authorization.
+## Tracked specialist integration cases
+These cases must remain visible in Tuskr and in CH while they are migrated,
+but they are not owned by the initial SOS core package.
+| ID | Current owner | Planned direction | Acceptance target |
+|---|---|---|---|
+| HEALTH-RESEARCH-001 | Human-health components / host adapter | Candidate for animal-care components | Create, update, activate and revoke a research study with server-confirmed controller or delegated authority. |
+| HEALTH-RESEARCH-002 | Human-health components / host adapter | Candidate for animal-care components | Search and add authorized research subjects without turning discovery into access. |
+| HEALTH-RESEARCH-003 | Human-health components / host adapter | Candidate for animal-care components | Import research data, map source fields, track jobs and review/reclassify/discard staged records. |
+| HEALTH-RESEARCH-004 | Human-health components / host adapter | Candidate for animal-care components | Manage research contracts, study invitations, subscriptions and governed data access separately from ordinary card permissions. |
+| HEALTH-RESEARCH-005 | Human-health components / host adapter | Undecided specialist package | Use transcription/edge models and future genomic workflows only through explicit capability, provenance and privacy policy. |
+The current source inventory still contains host-local research panels.
+Migration is complete only when consuming portals import their published
+human-health implementation and the local alternatives are deprecated.
+Group-management source already lives in
+the Antifraud Controller application; its controlled UI must be exported by
+the Antifraud Hosting component package before CH can remove its final local
+group adapter.
+## Explicitly outside the initial core
+- host registry, tenant admission and organization lifecycle policy (Antifraud
+  Controller/Hosting);
+- research-study administration, research-subject import and genomic workflows
+  (tracked above through their human-health to animal-care/specialist migration);
+- terminology databases and searches;
+- FHIR validation/conversion, DIDComm transport, wallets, signatures, QR
+  cryptography, WebRTC signaling and persistence;
+- application-specific routes, branding and deployment configuration.
+## Delivery order
+1. Inventory the current verified components in deprecated sector portals,
+   human-health components and consuming portal flavours.
+2. Add a contract test for one canonical component per use case.
+3. Move the current implementation without changing its data/authority
+   boundary, then switch all CH flavours to the published package.
+4. Mark old exports deprecated and keep their legacy tests separately runnable.
+5. Add web plus Expo adapters only where the same controlled contract is
+   genuinely reusable.
+6. Remove compatibility implementations only in a later breaking release.
+See [clinical sections, permissions and US Core contract](docs/03-CLINICAL_SECTIONS_AND_US_CORE_CONTRACT.md) for the recovered person/animal mappings and pending full example lifecycle.

package/dist/encounter-journey.css CHANGED Viewed

@@ -1,91 +1,91 @@
-.uhcp-transfer-console { background:var(--uhcp-surface,#fff); color:var(--uhcp-text,#102754); display:grid; font-family:Inter,ui-sans-serif,system-ui,sans-serif; grid-template-columns:minmax(16rem,23rem) minmax(0,1fr); min-height:calc(100vh - 4.5rem); }
-.uhcp-transfer-console button,.uhcp-transfer-console input,.uhcp-transfer-console textarea { font:inherit; }
-.uhcp-transfer-console svg { fill:none; height:1.25rem; stroke:currentColor; stroke-linecap:round; stroke-linejoin:round; stroke-width:1.8; width:1.25rem; }
-.uhcp-transfer-contacts { border-inline-end:1px solid #dce5ec; padding:1.2rem; }
-.uhcp-transfer-contacts summary { cursor:pointer; font-size:1.05rem; font-weight:850; list-style-position:inside; padding:.35rem 0 1rem; }
-.uhcp-transfer-contact-list { border-block:1px solid #e2e9ef; display:grid; padding:.45rem 0; }
-.uhcp-transfer-contact-list button { background:transparent; border:0; border-inline-start:3px solid transparent; color:inherit; cursor:pointer; display:grid; gap:.15rem; grid-template-columns:2.7rem 1fr; padding:.75rem; text-align:start; }
-.uhcp-transfer-contact-list button[aria-pressed=true] { background:var(--uhcp-surface-muted,#eaf8fd); border-inline-start-color:var(--uhcp-text,#09a9dc); }
-.uhcp-transfer-contact-list button>span { align-items:center; background:var(--uhcp-surface-muted,#d7e7f1); border-radius:50%; display:flex; font-weight:800; grid-row:span 2; height:2.4rem; justify-content:center; width:2.4rem; }
-.uhcp-transfer-contact-list small { color:var(--uhcp-text,#58708e); }
-.uhcp-transfer-contact-actions { display:grid; gap:.55rem; padding:1rem 0; }
-.uhcp-transfer-contact-actions button,.uhcp-transfer-mode button,.uhcp-transfer-composer fieldset button { align-items:center; background:var(--uhcp-surface,#fff); border:1px solid #cad7e2; border-radius:.55rem; color:inherit; cursor:pointer; display:flex; gap:.7rem; padding:.7rem .85rem; }
-.uhcp-transfer-contact-actions button[aria-pressed=true],.uhcp-transfer-mode button[aria-pressed=true] { background:var(--uhcp-surface-muted,#eaf8fd); border-color:var(--uhcp-text,#09a9dc); color:var(--uhcp-text,#006f96); font-weight:800; }
-.uhcp-transfer-composer fieldset button[aria-pressed=true] { background:var(--uhcp-surface-muted,#eaf8fd); border-color:var(--uhcp-text,#09a9dc); color:var(--uhcp-text,#006f96); font-weight:800; }
-.uhcp-transfer-composer { display:grid; gap:.8rem; }
-.uhcp-transfer-composer h3 { font-size:.95rem; margin:.2rem 0 0; }
-.uhcp-transfer-mode { display:grid; grid-template-columns:1fr 1fr; }
-.uhcp-transfer-mode button { justify-content:center; }
-.uhcp-transfer-composer label { display:grid; font-size:.82rem; font-weight:750; gap:.35rem; }
-.uhcp-transfer-composer textarea { border:1px solid #cad7e2; border-radius:.55rem; color:inherit; resize:vertical; padding:.75rem; }
-.uhcp-transfer-composer fieldset { border:0; margin:0; padding:0; }
-.uhcp-transfer-composer legend { font-size:.82rem; font-weight:750; margin-bottom:.4rem; }
-.uhcp-transfer-composer fieldset>div { display:flex; flex-wrap:wrap; gap:.4rem; }
-.uhcp-transfer-record { background:var(--uhcp-surface,#fff); border:1px dashed #09a9dc; border-radius:.55rem; color:var(--uhcp-text,#006f96); padding:1rem; }
-.uhcp-transfer-primary { background:#0796a8!important; border-color:#0796a8!important; color:#fff!important; font-weight:850!important; }
-.uhcp-transfer-main { min-width:0; padding:1rem; }
-.uhcp-transfer-patient,.uhcp-transfer-journey,.uhcp-transfer-review { border:1px solid #dce5ec; border-radius:.7rem; box-shadow:0 4px 16px rgb(16 39 84 / 5%); }
-.uhcp-transfer-patient { padding:1rem; }
-.uhcp-transfer-patient h2,.uhcp-transfer-journey h2,.uhcp-transfer-review h2 { font-size:1.18rem; margin:0; }
-.uhcp-transfer-patient>div { align-items:center; display:grid; gap:.75rem; grid-template-columns:minmax(11rem,.85fr) 1px minmax(13rem,1fr) auto; margin-top:.75rem; }
-.uhcp-transfer-patient button,.uhcp-transfer-patient label { align-items:center; background:var(--uhcp-surface,#fff); border:1px solid #9fb3c8; border-radius:.45rem; display:flex; gap:.65rem; min-height:3rem; padding:.7rem .9rem; }
-.uhcp-transfer-patient button { color:inherit; cursor:pointer; font-weight:800; justify-content:center; }
-.uhcp-transfer-patient button:last-child { background:var(--uhcp-surface-muted,#0796a8); border-color:var(--uhcp-text,#0796a8); color:#fff; }
-.uhcp-transfer-patient>div>span { background:var(--uhcp-surface-muted,#cbd7e1); height:2rem; }
-.uhcp-transfer-patient label { color:var(--uhcp-text,#64748b); }
-.uhcp-transfer-patient input { border:0; color:var(--uhcp-text,#102754); min-width:0; outline:0; width:100%; }
-.uhcp-transfer-journey { margin-top:.8rem; overflow:hidden; padding:1rem; }
-.uhcp-transfer-journey>header,.uhcp-transfer-review>header { align-items:center; display:flex; justify-content:space-between; }
-.uhcp-transfer-journey>header>div { display:flex; gap:.4rem; }
-.uhcp-transfer-journey>header button { align-items:center; background:var(--uhcp-surface,#fff); border:1px solid #cad7e2; border-radius:.45rem; color:inherit; display:flex; padding:.45rem; }
-.uhcp-transfer-journey>header button:first-child svg { transform:rotate(180deg); }
-.uhcp-transfer-rail { align-items:center; display:flex; gap:.8rem; min-height:18rem; overflow-x:auto; padding:1rem .25rem; scrollbar-color:#aebfce #edf2f5; }
-.uhcp-transfer-card { border:1px solid #cad7e2; border-radius:.5rem; flex:0 0 10rem; min-height:12rem; overflow:hidden; }
-.uhcp-transfer-card h3 { background:var(--uhcp-surface-muted,#087db8); color:var(--uhcp-text,#fff); font-size:.82rem; margin:0; padding:.65rem; }
-.uhcp-transfer-card-body { display:grid; gap:.45rem; padding:.85rem; }
-.uhcp-transfer-card-body time,.uhcp-transfer-card-body span,.uhcp-transfer-card-body code { color:var(--uhcp-text,#60738c); font-size:.72rem; }
-.uhcp-transfer-card-body small { background:var(--uhcp-surface-muted,#edf2f5); border-radius:999px; color:var(--uhcp-text,#466079); font-size:.7rem; justify-self:start; padding:.25rem .55rem; }
-.uhcp-transfer-card-body small[data-status=in-progress] { background:var(--uhcp-surface-muted,#d7f4e5); color:var(--uhcp-text,#087a47); }
-.uhcp-transfer-card-body small[data-status=completed] { background:var(--uhcp-surface-muted,#dff6e8); color:var(--uhcp-text,#087a47); }
-.uhcp-transfer-card-body small[data-status=on-hold] { background:var(--uhcp-surface-muted,#fff1d2); color:var(--uhcp-text,#9a5a00); }
-.uhcp-transfer-source { border-color:var(--uhcp-text,#078dcc); flex-basis:13.5rem; }
-.uhcp-transfer-destination { border-color:var(--uhcp-text,#069f69); flex-basis:13rem; }
-.uhcp-transfer-destination h3 { background:var(--uhcp-surface-muted,#069f69); }
-.uhcp-transfer-source fieldset { border:0; border-top:1px solid #dce5ec; margin:.2rem .7rem .7rem; padding:.7rem 0 0; }
-.uhcp-transfer-source legend { font-size:.72rem; font-weight:800; }
-.uhcp-transfer-source label { align-items:start; display:flex; gap:.45rem; padding:.35rem 0; }
-.uhcp-transfer-source label span { display:grid; }
-.uhcp-transfer-source label small { color:var(--uhcp-text,#60738c); font-size:.68rem; }
-.uhcp-transfer-arrow { align-items:center; color:var(--uhcp-text,#0796a8); display:grid; flex:0 0 5rem; grid-template-columns:1fr auto; text-align:center; }
-.uhcp-transfer-arrow span { font-size:.7rem; font-weight:800; grid-column:1/-1; }
-.uhcp-transfer-arrow i { background:var(--uhcp-surface-muted,#0796a8); height:2px; }
-.uhcp-transfer-arrow svg { margin-left:-.45rem; }
-.uhcp-transfer-help { background:var(--uhcp-surface-muted,#f4f9fc); border-radius:.5rem; padding:.65rem .8rem; }
-.uhcp-transfer-help summary { cursor:pointer; font-size:.78rem; font-weight:800; }
-.uhcp-transfer-help p { color:var(--uhcp-text,#51677e); font-size:.78rem; margin:.4rem 0 0; }
-.uhcp-transfer-controls { display:flex; gap:.55rem; justify-content:flex-end; padding-top:.75rem; }
-.uhcp-transfer-controls button { background:var(--uhcp-surface,#fff); border:1px solid #0796a8; border-radius:.45rem; color:var(--uhcp-text,#08738a); padding:.7rem 1rem; }
-.uhcp-transfer-review { margin-top:.8rem; padding:1rem; }
-.uhcp-transfer-review header p { background:var(--uhcp-surface-muted,#fff5dd); border:1px solid #f3ce79; border-radius:.4rem; color:var(--uhcp-text,#925800); font-size:.72rem; margin:0; padding:.5rem .7rem; }
-.uhcp-transfer-review ol { list-style:none; margin:.7rem 0 0; padding:0; }
-.uhcp-transfer-review li { align-items:center; border-top:1px solid #e1e8ee; display:grid; gap:.7rem; grid-template-columns:1.8rem 1fr auto; padding:.55rem; }
-.uhcp-transfer-review li>span { align-items:center; background:var(--uhcp-surface-muted,#e8f6fc); border-radius:50%; color:var(--uhcp-text,#087db8); display:flex; font-size:.72rem; font-weight:900; height:1.7rem; justify-content:center; width:1.7rem; }
-.uhcp-transfer-review li strong { font-size:.8rem; }
-.uhcp-transfer-review details { font-size:.68rem; }
-.uhcp-transfer-review summary { color:var(--uhcp-text,#60738c); cursor:pointer; }
-.uhcp-transfer-status { background:var(--uhcp-surface-muted,#dff6e8); border-radius:.45rem; color:var(--uhcp-text,#087a47); font-weight:750; padding:.75rem; }
-@media(max-width:900px){.uhcp-transfer-console{grid-template-columns:1fr}.uhcp-transfer-contacts{border-bottom:1px solid #dce5ec;border-inline-end:0}.uhcp-transfer-contact-actions{grid-template-columns:repeat(3,1fr)}.uhcp-transfer-patient>div{grid-template-columns:1fr}.uhcp-transfer-patient>div>span{display:none}.uhcp-transfer-review>header{align-items:flex-start;gap:.7rem;flex-direction:column}}
-@media(max-width:560px){.uhcp-transfer-main{padding:.55rem}.uhcp-transfer-contact-actions{grid-template-columns:1fr}.uhcp-transfer-rail{align-items:stretch}.uhcp-transfer-review li{grid-template-columns:1.8rem 1fr}.uhcp-transfer-review li details{grid-column:2}.uhcp-transfer-controls button{flex:1}.uhcp-transfer-review header p{font-size:.65rem}}
-.sos-encounter-journey { min-width:0; color:var(--uhcp-text,inherit); border:1px solid var(--uhcp-border,#dce5ec); border-radius:1rem; padding:clamp(.75rem,2vw,1.5rem); }
-.sos-encounter-journey>header,.sos-encounter-journey>form,.sos-encounter-actions { display:flex; align-items:center; flex-wrap:wrap; gap:.75rem; margin-bottom:1rem; }
-.sos-encounter-journey>header { justify-content:space-between; }
-.sos-encounter-journey h2 { margin:0; font-size:1.25rem; }
-.sos-encounter-journey label { display:grid; gap:.35rem; min-width:0; }
-.sos-encounter-journey select { max-width:100%; color:inherit; background:var(--uhcp-surface,#fff); border:1px solid var(--uhcp-border,#dce5ec); border-radius:.4rem; padding:.5rem; }
-.sos-encounter-journey button { cursor:pointer; border:1px solid var(--uhcp-border,#9bbfd1); border-radius:.5rem; padding:.55rem .8rem; color:inherit; background:var(--uhcp-surface-muted,#eef6fa); }
-.sos-encounter-journey button:disabled { opacity:.5; cursor:not-allowed; }
-.sos-encounter-journey button:focus-visible,.sos-encounter-journey select:focus-visible { outline:3px solid #1388c9; outline-offset:2px; }
-.sos-encounter-journey time,.sos-encounter-journey code { overflow-wrap:anywhere; }
-.sos-encounter-journey [role=alert] { color:var(--uhcp-danger,#b42318); }
-.sos-encounter-journey [role=status] { color:var(--uhcp-success,#087a47); }
+.uhcp-transfer-console { background:var(--uhcp-surface,#fff); color:var(--uhcp-text,#102754); display:grid; font-family:Inter,ui-sans-serif,system-ui,sans-serif; grid-template-columns:minmax(16rem,23rem) minmax(0,1fr); min-height:calc(100vh - 4.5rem); }
+.uhcp-transfer-console button,.uhcp-transfer-console input,.uhcp-transfer-console textarea { font:inherit; }
+.uhcp-transfer-console svg { fill:none; height:1.25rem; stroke:currentColor; stroke-linecap:round; stroke-linejoin:round; stroke-width:1.8; width:1.25rem; }
+.uhcp-transfer-contacts { border-inline-end:1px solid #dce5ec; padding:1.2rem; }
+.uhcp-transfer-contacts summary { cursor:pointer; font-size:1.05rem; font-weight:850; list-style-position:inside; padding:.35rem 0 1rem; }
+.uhcp-transfer-contact-list { border-block:1px solid #e2e9ef; display:grid; padding:.45rem 0; }
+.uhcp-transfer-contact-list button { background:transparent; border:0; border-inline-start:3px solid transparent; color:inherit; cursor:pointer; display:grid; gap:.15rem; grid-template-columns:2.7rem 1fr; padding:.75rem; text-align:start; }
+.uhcp-transfer-contact-list button[aria-pressed=true] { background:var(--uhcp-surface-muted,#eaf8fd); border-inline-start-color:var(--uhcp-text,#09a9dc); }
+.uhcp-transfer-contact-list button>span { align-items:center; background:var(--uhcp-surface-muted,#d7e7f1); border-radius:50%; display:flex; font-weight:800; grid-row:span 2; height:2.4rem; justify-content:center; width:2.4rem; }
+.uhcp-transfer-contact-list small { color:var(--uhcp-text,#58708e); }
+.uhcp-transfer-contact-actions { display:grid; gap:.55rem; padding:1rem 0; }
+.uhcp-transfer-contact-actions button,.uhcp-transfer-mode button,.uhcp-transfer-composer fieldset button { align-items:center; background:var(--uhcp-surface,#fff); border:1px solid #cad7e2; border-radius:.55rem; color:inherit; cursor:pointer; display:flex; gap:.7rem; padding:.7rem .85rem; }
+.uhcp-transfer-contact-actions button[aria-pressed=true],.uhcp-transfer-mode button[aria-pressed=true] { background:var(--uhcp-surface-muted,#eaf8fd); border-color:var(--uhcp-text,#09a9dc); color:var(--uhcp-text,#006f96); font-weight:800; }
+.uhcp-transfer-composer fieldset button[aria-pressed=true] { background:var(--uhcp-surface-muted,#eaf8fd); border-color:var(--uhcp-text,#09a9dc); color:var(--uhcp-text,#006f96); font-weight:800; }
+.uhcp-transfer-composer { display:grid; gap:.8rem; }
+.uhcp-transfer-composer h3 { font-size:.95rem; margin:.2rem 0 0; }
+.uhcp-transfer-mode { display:grid; grid-template-columns:1fr 1fr; }
+.uhcp-transfer-mode button { justify-content:center; }
+.uhcp-transfer-composer label { display:grid; font-size:.82rem; font-weight:750; gap:.35rem; }
+.uhcp-transfer-composer textarea { border:1px solid #cad7e2; border-radius:.55rem; color:inherit; resize:vertical; padding:.75rem; }
+.uhcp-transfer-composer fieldset { border:0; margin:0; padding:0; }
+.uhcp-transfer-composer legend { font-size:.82rem; font-weight:750; margin-bottom:.4rem; }
+.uhcp-transfer-composer fieldset>div { display:flex; flex-wrap:wrap; gap:.4rem; }
+.uhcp-transfer-record { background:var(--uhcp-surface,#fff); border:1px dashed #09a9dc; border-radius:.55rem; color:var(--uhcp-text,#006f96); padding:1rem; }
+.uhcp-transfer-primary { background:#0796a8!important; border-color:#0796a8!important; color:#fff!important; font-weight:850!important; }
+.uhcp-transfer-main { min-width:0; padding:1rem; }
+.uhcp-transfer-patient,.uhcp-transfer-journey,.uhcp-transfer-review { border:1px solid #dce5ec; border-radius:.7rem; box-shadow:0 4px 16px rgb(16 39 84 / 5%); }
+.uhcp-transfer-patient { padding:1rem; }
+.uhcp-transfer-patient h2,.uhcp-transfer-journey h2,.uhcp-transfer-review h2 { font-size:1.18rem; margin:0; }
+.uhcp-transfer-patient>div { align-items:center; display:grid; gap:.75rem; grid-template-columns:minmax(11rem,.85fr) 1px minmax(13rem,1fr) auto; margin-top:.75rem; }
+.uhcp-transfer-patient button,.uhcp-transfer-patient label { align-items:center; background:var(--uhcp-surface,#fff); border:1px solid #9fb3c8; border-radius:.45rem; display:flex; gap:.65rem; min-height:3rem; padding:.7rem .9rem; }
+.uhcp-transfer-patient button { color:inherit; cursor:pointer; font-weight:800; justify-content:center; }
+.uhcp-transfer-patient button:last-child { background:var(--uhcp-surface-muted,#0796a8); border-color:var(--uhcp-text,#0796a8); color:#fff; }
+.uhcp-transfer-patient>div>span { background:var(--uhcp-surface-muted,#cbd7e1); height:2rem; }
+.uhcp-transfer-patient label { color:var(--uhcp-text,#64748b); }
+.uhcp-transfer-patient input { border:0; color:var(--uhcp-text,#102754); min-width:0; outline:0; width:100%; }
+.uhcp-transfer-journey { margin-top:.8rem; overflow:hidden; padding:1rem; }
+.uhcp-transfer-journey>header,.uhcp-transfer-review>header { align-items:center; display:flex; justify-content:space-between; }
+.uhcp-transfer-journey>header>div { display:flex; gap:.4rem; }
+.uhcp-transfer-journey>header button { align-items:center; background:var(--uhcp-surface,#fff); border:1px solid #cad7e2; border-radius:.45rem; color:inherit; display:flex; padding:.45rem; }
+.uhcp-transfer-journey>header button:first-child svg { transform:rotate(180deg); }
+.uhcp-transfer-rail { align-items:center; display:flex; gap:.8rem; min-height:18rem; overflow-x:auto; padding:1rem .25rem; scrollbar-color:#aebfce #edf2f5; }
+.uhcp-transfer-card { border:1px solid #cad7e2; border-radius:.5rem; flex:0 0 10rem; min-height:12rem; overflow:hidden; }
+.uhcp-transfer-card h3 { background:var(--uhcp-surface-muted,#087db8); color:var(--uhcp-text,#fff); font-size:.82rem; margin:0; padding:.65rem; }
+.uhcp-transfer-card-body { display:grid; gap:.45rem; padding:.85rem; }
+.uhcp-transfer-card-body time,.uhcp-transfer-card-body span,.uhcp-transfer-card-body code { color:var(--uhcp-text,#60738c); font-size:.72rem; }
+.uhcp-transfer-card-body small { background:var(--uhcp-surface-muted,#edf2f5); border-radius:999px; color:var(--uhcp-text,#466079); font-size:.7rem; justify-self:start; padding:.25rem .55rem; }
+.uhcp-transfer-card-body small[data-status=in-progress] { background:var(--uhcp-surface-muted,#d7f4e5); color:var(--uhcp-text,#087a47); }
+.uhcp-transfer-card-body small[data-status=completed] { background:var(--uhcp-surface-muted,#dff6e8); color:var(--uhcp-text,#087a47); }
+.uhcp-transfer-card-body small[data-status=on-hold] { background:var(--uhcp-surface-muted,#fff1d2); color:var(--uhcp-text,#9a5a00); }
+.uhcp-transfer-source { border-color:var(--uhcp-text,#078dcc); flex-basis:13.5rem; }
+.uhcp-transfer-destination { border-color:var(--uhcp-text,#069f69); flex-basis:13rem; }
+.uhcp-transfer-destination h3 { background:var(--uhcp-surface-muted,#069f69); }
+.uhcp-transfer-source fieldset { border:0; border-top:1px solid #dce5ec; margin:.2rem .7rem .7rem; padding:.7rem 0 0; }
+.uhcp-transfer-source legend { font-size:.72rem; font-weight:800; }
+.uhcp-transfer-source label { align-items:start; display:flex; gap:.45rem; padding:.35rem 0; }
+.uhcp-transfer-source label span { display:grid; }
+.uhcp-transfer-source label small { color:var(--uhcp-text,#60738c); font-size:.68rem; }
+.uhcp-transfer-arrow { align-items:center; color:var(--uhcp-text,#0796a8); display:grid; flex:0 0 5rem; grid-template-columns:1fr auto; text-align:center; }
+.uhcp-transfer-arrow span { font-size:.7rem; font-weight:800; grid-column:1/-1; }
+.uhcp-transfer-arrow i { background:var(--uhcp-surface-muted,#0796a8); height:2px; }
+.uhcp-transfer-arrow svg { margin-left:-.45rem; }
+.uhcp-transfer-help { background:var(--uhcp-surface-muted,#f4f9fc); border-radius:.5rem; padding:.65rem .8rem; }
+.uhcp-transfer-help summary { cursor:pointer; font-size:.78rem; font-weight:800; }
+.uhcp-transfer-help p { color:var(--uhcp-text,#51677e); font-size:.78rem; margin:.4rem 0 0; }
+.uhcp-transfer-controls { display:flex; gap:.55rem; justify-content:flex-end; padding-top:.75rem; }
+.uhcp-transfer-controls button { background:var(--uhcp-surface,#fff); border:1px solid #0796a8; border-radius:.45rem; color:var(--uhcp-text,#08738a); padding:.7rem 1rem; }
+.uhcp-transfer-review { margin-top:.8rem; padding:1rem; }
+.uhcp-transfer-review header p { background:var(--uhcp-surface-muted,#fff5dd); border:1px solid #f3ce79; border-radius:.4rem; color:var(--uhcp-text,#925800); font-size:.72rem; margin:0; padding:.5rem .7rem; }
+.uhcp-transfer-review ol { list-style:none; margin:.7rem 0 0; padding:0; }
+.uhcp-transfer-review li { align-items:center; border-top:1px solid #e1e8ee; display:grid; gap:.7rem; grid-template-columns:1.8rem 1fr auto; padding:.55rem; }
+.uhcp-transfer-review li>span { align-items:center; background:var(--uhcp-surface-muted,#e8f6fc); border-radius:50%; color:var(--uhcp-text,#087db8); display:flex; font-size:.72rem; font-weight:900; height:1.7rem; justify-content:center; width:1.7rem; }
+.uhcp-transfer-review li strong { font-size:.8rem; }
+.uhcp-transfer-review details { font-size:.68rem; }
+.uhcp-transfer-review summary { color:var(--uhcp-text,#60738c); cursor:pointer; }
+.uhcp-transfer-status { background:var(--uhcp-surface-muted,#dff6e8); border-radius:.45rem; color:var(--uhcp-text,#087a47); font-weight:750; padding:.75rem; }
+@media(max-width:900px){.uhcp-transfer-console{grid-template-columns:1fr}.uhcp-transfer-contacts{border-bottom:1px solid #dce5ec;border-inline-end:0}.uhcp-transfer-contact-actions{grid-template-columns:repeat(3,1fr)}.uhcp-transfer-patient>div{grid-template-columns:1fr}.uhcp-transfer-patient>div>span{display:none}.uhcp-transfer-review>header{align-items:flex-start;gap:.7rem;flex-direction:column}}
+@media(max-width:560px){.uhcp-transfer-main{padding:.55rem}.uhcp-transfer-contact-actions{grid-template-columns:1fr}.uhcp-transfer-rail{align-items:stretch}.uhcp-transfer-review li{grid-template-columns:1.8rem 1fr}.uhcp-transfer-review li details{grid-column:2}.uhcp-transfer-controls button{flex:1}.uhcp-transfer-review header p{font-size:.65rem}}
+.sos-encounter-journey { min-width:0; color:var(--uhcp-text,inherit); border:1px solid var(--uhcp-border,#dce5ec); border-radius:1rem; padding:clamp(.75rem,2vw,1.5rem); }
+.sos-encounter-journey>header,.sos-encounter-journey>form,.sos-encounter-actions { display:flex; align-items:center; flex-wrap:wrap; gap:.75rem; margin-bottom:1rem; }
+.sos-encounter-journey>header { justify-content:space-between; }
+.sos-encounter-journey h2 { margin:0; font-size:1.25rem; }
+.sos-encounter-journey label { display:grid; gap:.35rem; min-width:0; }
+.sos-encounter-journey select { max-width:100%; color:inherit; background:var(--uhcp-surface,#fff); border:1px solid var(--uhcp-border,#dce5ec); border-radius:.4rem; padding:.5rem; }
+.sos-encounter-journey button { cursor:pointer; border:1px solid var(--uhcp-border,#9bbfd1); border-radius:.5rem; padding:.55rem .8rem; color:inherit; background:var(--uhcp-surface-muted,#eef6fa); }
+.sos-encounter-journey button:disabled { opacity:.5; cursor:not-allowed; }
+.sos-encounter-journey button:focus-visible,.sos-encounter-journey select:focus-visible { outline:3px solid #1388c9; outline-offset:2px; }
+.sos-encounter-journey time,.sos-encounter-journey code { overflow-wrap:anywhere; }
+.sos-encounter-journey [role=alert] { color:var(--uhcp-danger,#b42318); }
+.sos-encounter-journey [role=status] { color:var(--uhcp-success,#087a47); }

package/package.json CHANGED Viewed

@@ -1,110 +1,111 @@
-{
-  "name": "sos-portal-components-react",
-  "version": "0.3.4",
-  "description": "Shared portal UI for base components",
-  "license": "Apache-2.0",
-  "type": "module",
-  "main": "./dist/index.js",
-  "types": "./dist/index.d.ts",
-  "exports": {
-    "./subject-card-locator-fields": {
-      "types": "./dist/SubjectCardLocatorFields.d.ts",
-      "default": "./dist/SubjectCardLocatorFields.js"
-    },
-    "./device-assistance-preferences": {
-      "types": "./dist/DeviceAssistancePreferences.d.ts",
-      "default": "./dist/DeviceAssistancePreferences.js"
-    },
-    ".": {
-      "types": "./dist/index.d.ts",
-      "default": "./dist/index.js"
-    },
-    "./subject-conversation-chat": {
-      "types": "./dist/SubjectConversationChat.d.ts",
-      "default": "./dist/SubjectConversationChat.js"
-    },
-    "./encounter-journey": {
-      "types": "./dist/EncounterJourneyPanel.d.ts",
-      "default": "./dist/EncounterJourneyPanel.js"
-    },
-    "./encounter-transfer-console": {
-      "types": "./dist/EncounterTransferConsole.d.ts",
-      "default": "./dist/EncounterTransferConsole.js"
-    },
-    "./encounter-journey.css": "./dist/encounter-journey.css"
-  },
-  "files": [
-    "dist",
-    "README.md",
-    "CHANGELOG.md"
-  ],
-  "scripts": {
-    "clean": "node -e \"require('node:fs').rmSync('dist',{recursive:true,force:true})\"",
-    "build": "npm run clean && tsc -p tsconfig.build.json && node -e \"require('node:fs').copyFileSync('src/encounter-journey.css','dist/encounter-journey.css')\"",
-    "typecheck": "tsc -p tsconfig.json --noEmit",
-    "test": "vitest run --maxWorkers=1",
-    "check": "npm run typecheck && npm test && npm run build",
-    "prepack": "npm run check"
-  },
-  "engines": {
-    "node": ">=24.0.0"
-  },
-  "peerDependencies": {
-    "@kesha-antonov/react-native-chat": "^6.0.1",
-    "livekit-client": ">=2.23.0 <3",
-    "react": ">=18.3.0",
-    "react-dom": ">=18.3.0",
-    "react-native": ">=0.82.0",
-    "react-native-gesture-handler": ">=3.0.0",
-    "react-native-keyboard-controller": ">=1.0.0",
-    "react-native-reanimated": ">=3.0.0",
-    "react-native-safe-area-context": ">=5.0.0"
-  },
-  "peerDependenciesMeta": {
-    "@kesha-antonov/react-native-chat": {
-      "optional": true
-    },
-    "livekit-client": {
-      "optional": true
-    },
-    "react-native": {
-      "optional": true
-    },
-    "react-native-gesture-handler": {
-      "optional": true
-    },
-    "react-native-keyboard-controller": {
-      "optional": true
-    },
-    "react-native-reanimated": {
-      "optional": true
-    },
-    "react-native-safe-area-context": {
-      "optional": true
-    }
-  },
-  "dependencies": {
-    "antifraud-portal-components-react": "0.3.0",
-    "fhir-data-utils-ts": "0.6.24",
-    "sos-data-utils-ts": "0.6.34"
-  },
-  "devDependencies": {
-    "@testing-library/react": "^16.3.2",
-    "@types/node": "22.19.15",
-    "@types/react": "19.2.17",
-    "@types/react-dom": "19.2.3",
-    "jsdom": "26.1.0",
-    "livekit-client": "2.23.0",
-    "react": "19.2.8",
-    "react-dom": "19.2.8",
-    "typescript": "5.9.3",
-    "vitest": "4.1.12"
-  },
-  "publishConfig": {
-    "access": "public"
-  },
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/soschain/sos-portal-components-react.git"
-  }
-}
+{
+  "name": "sos-portal-components-react",
+  "version": "0.4.0",
+  "description": "Shared portal UI for base components",
+  "license": "Apache-2.0",
+  "type": "module",
+  "main": "./dist/index.js",
+  "types": "./dist/index.d.ts",
+  "exports": {
+    "./subject-card-locator-fields": {
+      "types": "./dist/SubjectCardLocatorFields.d.ts",
+      "default": "./dist/SubjectCardLocatorFields.js"
+    },
+    "./device-assistance-preferences": {
+      "types": "./dist/DeviceAssistancePreferences.d.ts",
+      "default": "./dist/DeviceAssistancePreferences.js"
+    },
+    ".": {
+      "types": "./dist/index.d.ts",
+      "default": "./dist/index.js"
+    },
+    "./subject-conversation-chat": {
+      "types": "./dist/SubjectConversationChat.d.ts",
+      "default": "./dist/SubjectConversationChat.js"
+    },
+    "./encounter-journey": {
+      "types": "./dist/EncounterJourneyPanel.d.ts",
+      "default": "./dist/EncounterJourneyPanel.js"
+    },
+    "./encounter-transfer-console": {
+      "types": "./dist/EncounterTransferConsole.d.ts",
+      "default": "./dist/EncounterTransferConsole.js"
+    },
+    "./encounter-journey.css": "./dist/encounter-journey.css"
+  },
+  "files": [
+    "dist",
+    "README.md",
+    "CHANGELOG.md"
+  ],
+  "scripts": {
+    "clean": "node -e \"require('node:fs').rmSync('dist',{recursive:true,force:true})\"",
+    "build": "npm run clean && tsc -p tsconfig.build.json && node -e \"require('node:fs').copyFileSync('src/encounter-journey.css','dist/encounter-journey.css')\"",
+    "typecheck": "tsc -p tsconfig.json --noEmit",
+    "test": "vitest run --maxWorkers=1",
+    "check:independent-dependencies": "node --test tests/no-gdc-dependencies.contract.mjs",
+    "check": "npm run typecheck && npm test && npm run build && npm run check:independent-dependencies",
+    "prepack": "npm run check"
+  },
+  "engines": {
+    "node": ">=24.0.0"
+  },
+  "peerDependencies": {
+    "@kesha-antonov/react-native-chat": "^6.0.1",
+    "livekit-client": ">=2.23.0 <3",
+    "react": ">=18.3.0",
+    "react-dom": ">=18.3.0",
+    "react-native": ">=0.82.0",
+    "react-native-gesture-handler": ">=3.0.0",
+    "react-native-keyboard-controller": ">=1.0.0",
+    "react-native-reanimated": ">=3.0.0",
+    "react-native-safe-area-context": ">=5.0.0"
+  },
+  "peerDependenciesMeta": {
+    "@kesha-antonov/react-native-chat": {
+      "optional": true
+    },
+    "livekit-client": {
+      "optional": true
+    },
+    "react-native": {
+      "optional": true
+    },
+    "react-native-gesture-handler": {
+      "optional": true
+    },
+    "react-native-keyboard-controller": {
+      "optional": true
+    },
+    "react-native-reanimated": {
+      "optional": true
+    },
+    "react-native-safe-area-context": {
+      "optional": true
+    }
+  },
+  "dependencies": {
+    "antifraud-portal-components-react": "0.3.0",
+    "fhir-data-utils-ts": "0.7.0",
+    "sos-data-utils-ts": "0.7.0"
+  },
+  "devDependencies": {
+    "@testing-library/react": "^16.3.2",
+    "@types/node": "22.19.15",
+    "@types/react": "19.2.17",
+    "@types/react-dom": "19.2.3",
+    "jsdom": "26.1.0",
+    "livekit-client": "2.23.0",
+    "react": "19.2.8",
+    "react-dom": "19.2.8",
+    "typescript": "5.9.3",
+    "vitest": "4.1.12"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/soschain/sos-portal-components-react.git"
+  }
+}