@vtex/faststore 0.0.5 → 0.0.7

package/dist/utils/safe-href.d.ts

@@ -0,0 +1,11 @@
+//#region src/utils/safe-href.d.ts
+/**
+ * Builds the sign-in destination, carrying the current path so the shopper can be returned where they
+ * started. The sender's half only: nothing stops a hand-crafted link, so the sign-in route is to narrow
+ * the parameter again on arrival. A path the narrowing refuses drops the parameter instead of
+ * travelling encoded, and so does a router reporting no path — `usePathname()`'s type is why this takes
+ * a nullable one.
+ */
+export declare function resolveSignInHref(pathname: string | null): string;
+//#endregion
+//# sourceMappingURL=safe-href.d.ts.map

package/dist/utils/substitute-template.js

@@ -0,0 +1,33 @@
+//#region src/utils/substitute-template.ts
+const TOKEN_PATTERN = /\{(\w+)\}/g;
+/**
+* Shared copy-template substitution (T97, T31 — specs/make-the-payment-components-authored-copy.md
+* Decision 7). Replaces every seven-plus `String.prototype.replace('{token}', value)` call sites
+* across `payment-summary.tsx`, `order-placed-payment-summary.tsx`, and `installments.tsx`, each of
+* which substituted only the *first* occurrence of a token and, at two sites, passed the value as a
+* replacement *string* — letting a server-sourced value containing `$&`/`` $` ``/`$'`/`$$` rewrite the
+* surrounding template text.
+*
+* One `/\{(\w+)\}/g` pass with a replacer *function*: every occurrence of every token is substituted
+* in a single scan, every value is inserted literally (a function's return value is never
+* re-interpreted as a replacement pattern), and a token with no matching entry in `tokens` is left
+* verbatim — so a template can be reworded freely without this helper silently dropping an
+* unrecognized placeholder. Because it is one pass, a substituted value can never itself be re-scanned
+* by a later token's own substitution.
+*
+* `Object.hasOwn`, not `tokenName in tokens` or a bare index lookup (fix pass, finding 6): every plain
+* object inherits from `Object.prototype`, so `tokens['toString']` resolves to
+* `Object.prototype.toString` — a function, therefore never `null`/`undefined` — rather than falling
+* through to `match` on a `??` lookup. `{toString}`, `{constructor}`, and `{__proto__}` would each
+* silently render an inherited value instead of being left verbatim as documented above.
+*/
+function substituteTemplate(template, tokens) {
+	return template.replace(TOKEN_PATTERN, (match, tokenName) => {
+		if (!Object.hasOwn(tokens, tokenName)) return match;
+		return tokens[tokenName] ?? match;
+	});
+}
+//#endregion
+export { substituteTemplate };
+
+//# sourceMappingURL=substitute-template.js.map

package/dist/utils/substitute-template.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"substitute-template.js","names":[],"sources":["../../src/utils/substitute-template.ts"],"sourcesContent":["const TOKEN_PATTERN = /\\{(\\w+)\\}/g;\n\n/**\n * Shared copy-template substitution (T97, T31 — specs/make-the-payment-components-authored-copy.md\n * Decision 7). Replaces every seven-plus `String.prototype.replace('{token}', value)` call sites\n * across `payment-summary.tsx`, `order-placed-payment-summary.tsx`, and `installments.tsx`, each of\n * which substituted only the *first* occurrence of a token and, at two sites, passed the value as a\n * replacement *string* — letting a server-sourced value containing `$&`/`` $` ``/`$'`/`$$` rewrite the\n * surrounding template text.\n *\n * One `/\\{(\\w+)\\}/g` pass with a replacer *function*: every occurrence of every token is substituted\n * in a single scan, every value is inserted literally (a function's return value is never\n * re-interpreted as a replacement pattern), and a token with no matching entry in `tokens` is left\n * verbatim — so a template can be reworded freely without this helper silently dropping an\n * unrecognized placeholder. Because it is one pass, a substituted value can never itself be re-scanned\n * by a later token's own substitution.\n *\n * `Object.hasOwn`, not `tokenName in tokens` or a bare index lookup (fix pass, finding 6): every plain\n * object inherits from `Object.prototype`, so `tokens['toString']` resolves to\n * `Object.prototype.toString` — a function, therefore never `null`/`undefined` — rather than falling\n * through to `match` on a `??` lookup. `{toString}`, `{constructor}`, and `{__proto__}` would each\n * silently render an inherited value instead of being left verbatim as documented above.\n */\nexport function substituteTemplate(template: string, tokens: Readonly<Record<string, string>>): string {\n  return template.replace(TOKEN_PATTERN, (match, tokenName: string) => {\n    if (!Object.hasOwn(tokens, tokenName)) return match;\n    // `noUncheckedIndexedAccess` still types this lookup as `string | undefined`; the `Object.hasOwn`\n    // check above is what actually guarantees a string is here, so this `??` can never fall through\n    // for a real token — it only satisfies the index-signature type, never re-opens finding 6's bug.\n    return tokens[tokenName] ?? match;\n  });\n}\n"],"mappings":";AAAA,MAAM,gBAAgB;;;;;;;;;;;;;;;;;;;;;;AAuBtB,SAAgB,mBAAmB,UAAkB,QAAkD;CACrG,OAAO,SAAS,QAAQ,gBAAgB,OAAO,cAAsB;EACnE,IAAI,CAAC,OAAO,OAAO,QAAQ,SAAS,GAAG,OAAO;EAI9C,OAAO,OAAO,cAAc;CAC9B,CAAC;AACH"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vtex/faststore",
-  "version": "0.0.5",
+  "version": "0.0.7",
   "description": "FastStore AI Native component library built on Base UI with AI-editable styles",
   "license": "MIT",
   "homepage": "https://developers.vtex.com/docs/guides/faststore",
@@ -25,6 +25,11 @@
       "import": "./dist/graphql.js",
       "default": "./dist/graphql.js"
     },
+    "./cli": {
+      "types": "./dist/cli/index.d.ts",
+      "import": "./dist/cli/index.js",
+      "default": "./dist/cli/index.js"
+    },
     "./internal/client": {
       "types": "./dist/internal/client.d.ts",
       "import": "./dist/internal/client.js"
@@ -52,6 +57,7 @@
     "@base-ui/react": "^1.3.0",
     "@graphql-typed-document-node/core": "^3.2.0",
     "graphql": "^16.13.1",
+    "react-hook-form": "^7.85.0",
     "react-intl": "^10.1.22",
     "rxjs": "^7.8.2",
     "tailwindcss": "^4.2.2",
@@ -62,6 +68,12 @@
     "@apollo/client-integration-nextjs": "^0.14.5",
     "next": ">=16",
     "react": "^19.0.0",
-    "react-dom": "^19.0.0"
+    "react-dom": "^19.0.0",
+    "typescript": "^5.9.3"
+  },
+  "peerDependenciesMeta": {
+    "typescript": {
+      "optional": true
+    }
   }
 }

package/src/styles/tailwind.css

@@ -30,3 +30,37 @@
   --max-width-md: var(--container-md);
   --max-width-lg: var(--container-lg);
 }
+
+@layer base {
+  /* Default visible focus indicator for the payment surface (T38, REQ-11's WCAG scenario).
+     `@layer base` so any merchant utility class outranks it under Tailwind 4's layer order.
+     `currentColor` because the merchant's palette is unknown here — see Decision 6 on contrast.
+     Scoped by an explicit hook list, not by an ancestor: `PaymentSectionController` renders no DOM
+     element, so no ancestor selector reaches a controller-composed page. */
+  [data-fs-payment-method-list] :focus-visible,
+  [data-fs-installments] :focus-visible,
+  [data-fs-saved-cards] :focus-visible,
+  [data-fs-billing-address] :focus-visible,
+  [data-fs-card-entry] :focus-visible,
+  [data-fs-cardholder-document] :focus-visible,
+  [data-fs-save-card] :focus-visible,
+  [data-fs-place-order] :focus-visible,
+  [data-fs-installments-option]:focus-visible {
+    outline: 2px solid currentColor;
+    outline-offset: 2px;
+  }
+
+  /* `<fieldset>` carries `min-inline-size: min-content`, which Tailwind's preflight does not reset,
+     so it refuses to shrink inside a flex row. Live already via CardEntry's fieldset; mitigated here
+     for the three groups T38 adds. Scoped by the same explicit hook-list approach as the focus rule
+     above, not by `[data-fs-fieldset-root]`: the Fieldset particle emits that attribute
+     unconditionally, so it also reaches `ClientProfileForm`'s optional grouping fieldset — a
+     non-payment component whose rendering must not change (measured: 95px vs. 113px in a 200px flex
+     row with a competing sibling). */
+  [data-fs-payment-method-list-fieldset],
+  [data-fs-installments-fieldset],
+  [data-fs-saved-cards-fieldset],
+  [data-fs-card-entry-fieldset] {
+    min-inline-size: 0;
+  }
+}

package/dist/docs/client-profile-form.md

@@ -1,192 +0,0 @@
-# ClientProfileForm
-
-**Category:** identity
-**Purpose:** The batched customer-information form for the checkout identity step — the `InformationFormUSA` replacement. Pre-fills first/last name, phone, document, and both consent opt-ins from the shopper's saved profile and preferences; displays the email read-only. A single Save / Continue action validates the draft and dispatches at most one `clientProfileUpdate` and one `clientPreferencesUpdate`, each carrying only the fields the shopper edited, with pending/confirmation/error feedback.
-
----
-
-## Visual cues (how to identify in an image)
-
-- A single form block on a checkout identity step titled "Your information" (or similar), grouping: a read-only email display, first name, last name, a country-masked phone field, an optional tax-document field (e.g. CPF for Brazil), and two checkboxes ("email me with news and offers", "save my information for next time").
-- One visible primary button at the bottom labelled "Save and continue" (or similar) — not a hidden submit.
-- Pre-filled values for a returning/identified shopper; blank, still-editable fields for a guest or an incomplete profile.
-- An inline error banner on failure, or a confirmation line on success, appearing near the button.
-
-Use `ClientProfileForm` (not a hand-assembled combination of `Field`/`PhoneField`/`DocumentField`) whenever the image shows this whole batched-save customer-information block.
-
----
-
-## When to use
-
-- The customer-information section of the checkout identity step, for both returning/identified shoppers (pre-fill + edit) and guests (fill from empty).
-- Anywhere name, phone, document, and consent opt-ins must be collected together and persisted in one explicit action.
-
-## When NOT to use
-
-- Editing the email — that is `EmailIdentificationControl`'s job; this form only displays it.
-- A single standalone phone or opt-in field with its own save-on-blur behavior — use `ClientProfilePhoneControl` / `NewsletterOptInControl` / `SavePersonalDataOptInControl` instead. **Never place a standalone per-field identity Control and this form for the same field on the same view** — both would write the field, racing each other.
-- Address fields — those belong to Delivery, not this form.
-
----
-
-## Composition
-
-`ClientProfileForm` is a **compound**: `Root` owns the data + mechanics; the field/fieldset/feedback
-parts are composed freely (any order, any subset). The schema author decides which fields render — a
-merchant whose platform config drops a field (or whose account can't persist one, e.g. an unsupported
-`savePersonalData`) simply does not compose that part.
-
-```
-SessionRoot                                 (required ancestor; session tri-state + canEditData)
-└── ClientProfileForm.Root                  (data-fs-client-profile-form; own fragment/data root; owns draft + Save)
-    ├── ClientProfileForm.Fieldset section="profile" [legend]
-    │     ├── .EmailField                    (read-only)
-    │     ├── .FirstNameField / .LastNameField
-    │     ├── .PhoneField                    (uses country from Root)
-    │     └── .DocumentField                 (self-gates on documentType)
-    ├── ClientProfileForm.Fieldset section="preferences" [legend]
-    │     ├── .NewsletterCheckbox
-    │     └── .SavePersonalDataCheckbox       (omit to drop the field entirely — no CSS hack)
-    ├── .Error / .Confirmation
-    └── .SubmitButton
-```
-
-`Root` is self-contained: it declares the colocated fragment over `clientProfile` + `clientPreferences`
-and must not be nested inside `ClientProfileRoot` / `ClientPreferencesRoot` (those self-persist per
-field on blur, double-writing against this form's batched Save). Every part `requiresContext:
-'client-profile-form'`; a custom/derived field declares its own additional `requiresContext`.
-
----
-
-## Behavior
-
-- **Sections**: compose `ClientProfileForm.Fieldset` blocks with a `section` name → `data-fs-client-profile-form-section="<name>"`, and an optional `legend`. Not hard-coded — the author groups fields however the design needs.
-- **Pre-fill**: every field seeds from `$data` on mount; missing profile fields render empty and stay editable.
-- **Draft & dirty tracking**: edits are tracked locally per field; only touched fields are dispatched. Background `$data` refreshes re-seed untouched fields only — an in-progress edit is never clobbered.
-- **Save**: validates **field format only** — phone mask and document check-digit, each blocking Save when the field is non-empty and malformed. It does not enforce requiredness: the parts are composed freely by the schema, so a required check here could fire for a field the page never mounted. Which fields a shopper must fill is a business rule, waiting on the composable entity forms RFC (#572) to decide where it belongs. The format checks carry the same composition hazard in a narrower form, and it is still open: they key off the Root's `country` and `documentType` rather than off which leaves were composed, so a store that sets `documentType` without composing `DocumentField` can block Save with no field to render the error in and nowhere to move focus. Closing it properly means the leaves registering themselves with the Root, which is that same RFC's territory. The phone case is wider than the document one and needs no merchant configuration at all — see Known gaps below. On Save it dispatches at most one `clientProfileUpdate` (dirty profile fields) and one `clientPreferencesUpdate` (dirty consent flags) in parallel; a Save with nothing dirty dispatches nothing and shows the confirmation, so the press still answers.
-- **Document erase**: clearing a previously-saved document and pressing Save sends `document: ''` — an explicit erase, not an omission.
-- **Feedback**: `data-fs-client-profile-form-pending` while a write is in flight (fieldset disabled, Save not re-triggerable); an inline `role="alert"` region on `userErrors`; an `<output>` confirmation on success, cleared on the next edit.
-- **Read-only**: `session.canEditData === false` renders `data-fs-client-profile-form-readonly`, disables every field, and omits the Save button entirely.
-- **The form announces nothing**: a completed Save shows the confirmation and stops there. It publishes no signal, so nothing elsewhere collapses, advances or reacts. Whether finishing this form should move a section or a wizard is a sequencing question, and the mechanism for it is being designed in the flow-of-steps RFC (#611) rather than assumed here.
-- **The form never learns who listens.** It reports nothing at all, so `IdentityEditController` cannot react to it: that section moves only on its own buttons. Compose the swap around this form: an `IdentityEditController` holding an `IdentitySummaryView` with the summary, an `IdentityEditForm` with `ClientProfileForm.Root`, an `IdentityEditButton` in the heading, and an `IdentityEditCancelButton` as cancel next to the form. The same form therefore works unchanged inside a collapsing section or on a page of its own.
-
----
-
-## Props
-
-**`ClientProfileForm.Root`** — `country` (`'US' | 'BR'`, default `'US'`; provided to the phone leaf via
-context), `documentType` (string, e.g. `'CPF'`; the document leaf renders only when supported).
-Declares `actions: { identity: ['clientProfileUpdate', 'clientPreferencesUpdate'] }`,
-`requiresContext: 'session'`, `providesContext: 'client-profile-form'`.
-
-**`ClientProfileForm.Fieldset`** — `legend` (optional visible title), `section` (name → `data-fs-*-section`).
-
-**Field parts** (`.EmailField`, `.FirstNameField`, `.LastNameField`, `.PhoneField`, `.DocumentField`,
-`.NewsletterCheckbox`, `.SavePersonalDataCheckbox`) — each takes an optional `label` (sensible default).
-**`.Confirmation`** — `message` (default `'Your information has been saved.'`). **`.SubmitButton`** —
-`label` (default `'Save and continue'`) or composed `children`.
-
----
-
-## Canonical schema example
-
-```json
-{
-  "session": {
-    "type": "SessionRoot",
-    "children": ["email-identification", "profile-form"]
-  },
-  "email-identification": {
-    "type": "EmailIdentificationControl",
-    "children": []
-  },
-  "profile-form": {
-    "type": "ClientProfileFormRoot",
-    "props": { "country": "BR", "documentType": "CPF" },
-    "children": ["profile-fieldset", "preferences-fieldset", "form-error", "form-confirmation", "form-submit"]
-  },
-  "profile-fieldset": {
-    "type": "ClientProfileFormFieldset",
-    "props": { "section": "profile", "legend": "Your information" },
-    "children": ["email", "first-name", "last-name", "phone", "document"]
-  },
-  "email": { "type": "ClientProfileFormEmailField", "children": [] },
-  "first-name": { "type": "ClientProfileFormFirstNameField", "children": [] },
-  "last-name": { "type": "ClientProfileFormLastNameField", "children": [] },
-  "phone": { "type": "ClientProfileFormPhoneField", "children": [] },
-  "document": { "type": "ClientProfileFormDocumentField", "children": [] },
-  "preferences-fieldset": {
-    "type": "ClientProfileFormFieldset",
-    "props": { "section": "preferences" },
-    "children": ["newsletter"]
-  },
-  "newsletter": { "type": "ClientProfileFormNewsletterCheckbox", "children": [] },
-  "form-error": { "type": "ClientProfileFormError", "children": [] },
-  "form-confirmation": { "type": "ClientProfileFormConfirmation", "children": [] },
-  "form-submit": { "type": "ClientProfileFormSubmitButton", "children": [] }
-}
-```
-
-Both fieldsets are children of the Root, not siblings of it: every part declares
-`requiresContext: 'client-profile-form'`, so a fieldset placed outside is rejected by the
-context-constraint walk at build time.
-
-(Omitting `ClientProfileFormSavePersonalDataCheckbox` above drops that field entirely — the intended
-way to exclude a field the account can't persist, with no CSS hack and no shared-component change.)
-
----
-
-## Common mistakes
-
-- **Rendering `ClientProfileForm` outside `SessionRoot`.** `useSession()` throws; every identity page must host a `SessionRoot`.
-- **Nesting it inside `ClientProfileRoot` / `ClientPreferencesRoot`, or placing a standalone Control for the same field alongside it.** The form is its own data root and its own write surface — double-nesting or double-placing creates a double-write race.
-- **Expecting the email to be editable.** It is always read-only here; email changes go through `EmailIdentificationControl`.
-- **Expecting per-keystroke or per-blur saves.** All fields are form-bound; only pressing Save dispatches a write.
-- **Expecting the form to enforce required fields.** It validates format only. A blank field saves, because the form cannot know which of its freely-composed parts the page actually mounted.
-- **Rendering a field part outside `ClientProfileForm.Root`.** Every part `requiresContext: 'client-profile-form'` and throws otherwise.
-
----
-
-## Styling
-
-| Component | What you style | Plausible classes |
-|---|---|---|
-| `ClientProfileForm` | The `data-fs-client-profile-form` root; carries `-pending`/`-readonly`/`-saved` presence attributes | `flex flex-col gap-10` |
-| Section | `data-fs-client-profile-form-section="profile\|preferences"` — the two entity-anchored fieldsets | `flex flex-col gap-4` |
-| Field wrapper | `data-fs-client-profile-form-field="email\|first-name\|last-name\|phone\|document\|newsletter\|save-personal-data"` | `flex flex-col gap-4` |
-| Error / confirmation | `[data-fs-client-profile-form-error]` / `[data-fs-client-profile-form-confirmation]` | `text-sm text-red-600` / `text-sm text-green-600` |
-
-Field-level visuals (borders, focus rings, error color) are owned by the composed particles' own swatches (`field`, `phone-field`, `document-field`, `checkbox`, `button`) and are not redefined here.
-
----
-
-## Known gaps
-
-Found by review and deliberately left for the dedicated revision of these components, rather than patched
-here. The first is the widest.
-
-- **Format validation runs against fields the page may never have composed, and the phone case needs no
-  merchant configuration at all.** `country` defaults to `'US'`, so the phone check always runs. A store
-  composing `Root` + name fields + `SubmitButton`, serving a shopper whose stored phone is a legacy
-  malformed value, gets a Save that sets `errors.phone`, finds no phone input to focus, renders no message
-  because `PhoneField` is not mounted, and returns — dead on every press, button still enabled. The
-  `documentType` variant of the same hole at least requires the merchant to have set a Root prop. Closing
-  both properly means the leaves registering themselves with the Root; see the composable entity forms RFC
-  (#572).
-- **Two other early returns leave Save silent.** A missing `$actions.identity`, or a dirty field with no
-  matching write function, returns without touching `pending`, `serverError` or `saved` — the same dead
-  press the pristine branch above was changed to avoid.
-- **`VALIDATION_ORDER` is a hard-coded `['phone', 'document']`,** but the leaves are now composed in any
-  order. With both fields malformed, focus jumps to the phone input even when the document error is the one
-  the shopper can see first. The order should come from DOM position now that the fixed template is gone.
-- **The re-seed of untouched fields mutates a ref during render** and queues its `setDraft` in the same
-  pass. A discarded render keeps the ref but loses the update, so pristine fields can hold stale values
-  after `$data` arrives.
-
-## Related
-
-- [[email-identification]] — the sibling identification control this form's email display defers to.
-- [[client-profile]] — the standalone, per-field-blur phone binding; do not compose alongside this form for the same field.
-- [[client-preferences]] — the standalone, per-field-blur consent Controls; do not compose alongside this form for the same field.
-- [[session]] — provides the identification tri-state and the required `SessionRoot` ancestor.
-- [[phone-field]], [[document-field]], [[field]], [[fieldset]], [[checkbox]] — the particles this matter composes directly.

package/dist/matter/client-profile-form/client-profile-form.d.ts

@@ -1,126 +0,0 @@
-import { ComponentDefinition } from "../../core/dist/define-component.js";
-import "../../core/dist/index.js";
-import { ComponentActions } from "../../sdk/actions/types.js";
-import { PhoneCountry } from "../../particles/phone-field/phone-field.js";
-import { ReactNode } from "react";
-//#region src/matter/client-profile-form/client-profile-form.d.ts
-/** The `$data` slice forwarded by the reactive runtime — both identity sibling entities. */
-export type ClientProfileFormData = {
-  clientProfile?: {
-    email?: string | null;
-    firstName?: string | null;
-    lastName?: string | null;
-    phone?: string | null;
-    document?: string | null;
-  } | null;
-  clientPreferences?: {
-    optinNewsLetter?: boolean | null;
-    savePersonalData?: boolean | null;
-  } | null;
-} | null;
-export type ClientProfileFormRootProps = {
-  /** Phone mask/validation country, provided to the phone leaf via context. */
-  country?: PhoneCountry;
-  /** Locale document type; the document leaf renders only when supported. Provided via context. */
-  documentType?: string;
-  className?: string;
-  children?: ReactNode;
-  /** `ClientProfileFormData` slice forwarded by the reactive runtime. */
-  $data?: ClientProfileFormData;
-  /** Compiler-injected action surface; carries `identity.clientProfileUpdate` / `clientPreferencesUpdate`. */
-  $actions?: ComponentActions;
-};
-export type ClientProfileFormFieldsetProps = {
-  /** Visible legend; omitted (no title) when unset. */
-  legend?: string;
-  /** Value emitted on `data-fs-client-profile-form-section` for scoped styling (e.g. `profile`). */
-  section?: string;
-  className?: string;
-  children?: ReactNode;
-};
-type LabelledFieldProps = {
-  label?: string;
-  className?: string;
-};
-export type ClientProfileFormEmailFieldProps = LabelledFieldProps;
-export type ClientProfileFormFirstNameFieldProps = LabelledFieldProps;
-export type ClientProfileFormLastNameFieldProps = LabelledFieldProps;
-export type ClientProfileFormPhoneFieldProps = LabelledFieldProps;
-export type ClientProfileFormDocumentFieldProps = LabelledFieldProps;
-export type ClientProfileFormNewsletterCheckboxProps = LabelledFieldProps;
-export type ClientProfileFormSavePersonalDataCheckboxProps = LabelledFieldProps;
-export type ClientProfileFormErrorProps = {
-  className?: string;
-};
-export type ClientProfileFormConfirmationProps = {
-  message?: string;
-  className?: string;
-};
-export type ClientProfileFormSubmitButtonProps = {
-  label?: string;
-  className?: string;
-  children?: ReactNode;
-};
-export declare const ClientProfileFormRootDefinition: ComponentDefinition<ClientProfileFormRootProps>;
-export declare const ClientProfileFormFieldsetDefinition: ComponentDefinition<ClientProfileFormFieldsetProps>;
-export declare const ClientProfileFormEmailFieldDefinition: ComponentDefinition<LabelledFieldProps>;
-export declare const ClientProfileFormFirstNameFieldDefinition: ComponentDefinition<LabelledFieldProps>;
-export declare const ClientProfileFormLastNameFieldDefinition: ComponentDefinition<LabelledFieldProps>;
-export declare const ClientProfileFormPhoneFieldDefinition: ComponentDefinition<LabelledFieldProps>;
-export declare const ClientProfileFormDocumentFieldDefinition: ComponentDefinition<LabelledFieldProps>;
-export declare const ClientProfileFormNewsletterCheckboxDefinition: ComponentDefinition<LabelledFieldProps>;
-export declare const ClientProfileFormSavePersonalDataCheckboxDefinition: ComponentDefinition<LabelledFieldProps>;
-export declare const ClientProfileFormErrorDefinition: ComponentDefinition<ClientProfileFormErrorProps>;
-export declare const ClientProfileFormConfirmationDefinition: ComponentDefinition<ClientProfileFormConfirmationProps>;
-export declare const ClientProfileFormSubmitButtonDefinition: ComponentDefinition<ClientProfileFormSubmitButtonProps>;
-/**
- * Data root + form shell. Seeds a local draft from `$data`, tracks dirty fields (background `$data`
- * refreshes only re-seed untouched fields), runs format-only validation, and on Save dispatches the
- * batched `clientProfileUpdate` / `clientPreferencesUpdate` (touched fields only), showing the
- * confirmation on success. Provides everything the field leaves need via context; renders a `<form>`
- * around its children.
- *
- * It publishes nothing. A finished press is not announced, so no section collapses as a result and
- * nothing outside this form can react to it. Whether a checkout sequences on a completed form is left to
- * the flow-of-steps RFC (#611).
- */
-export declare function ClientProfileFormRoot({ country, documentType, className, children, $data: $dataProp, $actions: $actionsProp }: Readonly<ClientProfileFormRootProps>): import("react/jsx-runtime").JSX.Element;
-export declare function ClientProfileFormFieldset({ legend, section, className, children }: ClientProfileFormFieldsetProps): import("react/jsx-runtime").JSX.Element;
-export declare function ClientProfileFormEmailField({ label, className }: ClientProfileFormEmailFieldProps): import("react/jsx-runtime").JSX.Element;
-export declare function ClientProfileFormFirstNameField({ label, className }: ClientProfileFormFirstNameFieldProps): import("react/jsx-runtime").JSX.Element;
-export declare function ClientProfileFormLastNameField({ label, className }: ClientProfileFormLastNameFieldProps): import("react/jsx-runtime").JSX.Element;
-export declare function ClientProfileFormPhoneField({ label, className }: ClientProfileFormPhoneFieldProps): import("react/jsx-runtime").JSX.Element;
-export declare function ClientProfileFormDocumentField({ label, className }: ClientProfileFormDocumentFieldProps): import("react/jsx-runtime").JSX.Element | null;
-export declare function ClientProfileFormNewsletterCheckbox({ label, className }: ClientProfileFormNewsletterCheckboxProps): import("react/jsx-runtime").JSX.Element;
-export declare function ClientProfileFormSavePersonalDataCheckbox({ label, className }: ClientProfileFormSavePersonalDataCheckboxProps): import("react/jsx-runtime").JSX.Element;
-export declare function ClientProfileFormError({ className }: ClientProfileFormErrorProps): import("react/jsx-runtime").JSX.Element | null;
-export declare function ClientProfileFormConfirmation({ message, className }: ClientProfileFormConfirmationProps): import("react/jsx-runtime").JSX.Element | null;
-export declare function ClientProfileFormSubmitButton({ label, className, children }: ClientProfileFormSubmitButtonProps): import("react/jsx-runtime").JSX.Element | null;
-export declare const ClientProfileForm: {
-  Root: typeof ClientProfileFormRoot;
-  RootDefinition: ComponentDefinition<ClientProfileFormRootProps>;
-  Fieldset: typeof ClientProfileFormFieldset;
-  FieldsetDefinition: ComponentDefinition<ClientProfileFormFieldsetProps>;
-  EmailField: typeof ClientProfileFormEmailField;
-  EmailFieldDefinition: ComponentDefinition<LabelledFieldProps>;
-  FirstNameField: typeof ClientProfileFormFirstNameField;
-  FirstNameFieldDefinition: ComponentDefinition<LabelledFieldProps>;
-  LastNameField: typeof ClientProfileFormLastNameField;
-  LastNameFieldDefinition: ComponentDefinition<LabelledFieldProps>;
-  PhoneField: typeof ClientProfileFormPhoneField;
-  PhoneFieldDefinition: ComponentDefinition<LabelledFieldProps>;
-  DocumentField: typeof ClientProfileFormDocumentField;
-  DocumentFieldDefinition: ComponentDefinition<LabelledFieldProps>;
-  NewsletterCheckbox: typeof ClientProfileFormNewsletterCheckbox;
-  NewsletterCheckboxDefinition: ComponentDefinition<LabelledFieldProps>;
-  SavePersonalDataCheckbox: typeof ClientProfileFormSavePersonalDataCheckbox;
-  SavePersonalDataCheckboxDefinition: ComponentDefinition<LabelledFieldProps>;
-  Error: typeof ClientProfileFormError;
-  ErrorDefinition: ComponentDefinition<ClientProfileFormErrorProps>;
-  Confirmation: typeof ClientProfileFormConfirmation;
-  ConfirmationDefinition: ComponentDefinition<ClientProfileFormConfirmationProps>;
-  SubmitButton: typeof ClientProfileFormSubmitButton;
-  SubmitButtonDefinition: ComponentDefinition<ClientProfileFormSubmitButtonProps>;
-};
-//#endregion
-//# sourceMappingURL=client-profile-form.d.ts.map