@incodetech/prizma-core-screens 0.2.4 → 0.2.12

package/dist/BiometricConsentScreen.d.ts

@@ -0,0 +1,95 @@
+import React from 'react';
+import { type PrizmaFormScreenProps } from './FormScreen';
+import type { PrizmaScreenActionHandler, PrizmaScreenOverrides } from './types';
+import type { BiometricConsentState, BiometricConsentStrings } from './BiometricConsentStrings';
+import './ScreenLayout.css';
+export interface BiometricConsentScreenProps extends Omit<PrizmaFormScreenProps, 'title' | 'subtitle' | 'ctaLabel' | 'ctaDisabled' | 'verifiedLabel' | 'children' | 'navLabel' | 'linkLabel' | 'linkDisabled' | 'linkContent' | 'overlay' | 'fieldsOffset' | 'fieldsGap' | 'fieldsAlign' | 'scrollFields'> {
+    /** Module copy — this screen reads the `consent` and `quit` slices. */
+    strings: BiometricConsentStrings;
+    /** Which of the two section states to render. Default `default`. */
+    state?: BiometricConsentState;
+    /**
+     * Cancel was pressed: present the quit confirmation over the consent. The
+     * consent underneath keeps its `state` — the box is whatever the person had.
+     * Its two answers: the confirm emits `cta` (the session ends), the dismiss
+     * emits `secondary` (back to the consent). DEVIATIONS #BC-7.
+     */
+    quitConfirm?: boolean;
+    /**
+     * The box was ticked or unticked. A REAL change event from Core's own
+     * `<input type="checkbox">` — the card is a `<label>`, so tapping the copy
+     * toggles it too, which is the behaviour the request named ("tapping the body
+     * also toggles the checkbox"). The screen stays controlled by `state`; this
+     * only reports the press so a host (or the Core Lab prototype) can move the
+     * state itself. The sibling consent screen forwards no such handler and its
+     * prototype had to listen on a wrapper instead — this closes that gap for this
+     * module.
+     */
+    onConsentChange?: (checked: boolean) => void;
+    screenId?: string;
+    overrides?: PrizmaScreenOverrides;
+    onAction?: PrizmaScreenActionHandler;
+}
+/**
+ * Biometric Consent — the mandatory biometric-processing consent, built on the
+ * Form archetype (GUIDELINES.md §6-E, `PrizmaFormScreen`).
+ *
+ * ONE screen for the whole `biometricConsent` section (2001:16315): the two
+ * state frames (`empty` 2001:16361, `checked` 2001:16372) share an identical
+ * skeleton — nav → Title (H2 + H5) → one consent card → Continue → Cancel →
+ * tag — and differ ONLY in whether the box is ticked and the CTA released.
+ * Plus the quit confirmation (`quitConfirm`), a Core sheet or dialog presented
+ * over either state when Cancel is pressed.
+ *
+ * WHY ARCHETYPE E. The same reason the sibling consent screen gives: a
+ * `PrizmaCheckbox` is a real `<input type="checkbox">` that joins the form, and
+ * the gated CTA is the whole point of a consent screen — `PrizmaListScreen` has
+ * no `ctaDisabled` slot. E also carries the one tertiary action under the
+ * primary (`linkLabel`), which is exactly where the frame draws Cancel.
+ *
+ * THE CARD SITS AT THE BOTTOM OF THE COLUMN, NOT UNDER THE TITLE. The frame's
+ * middle (2001:15150) is a `justify-between` column: the Title block at the top,
+ * the consent card flush against the CTA band with the frame's Spacing/16
+ * between them, and everything in between left empty. That is the opposite of
+ * every other Form consumer, whose stack hangs off the title, so the screen
+ * SELECTS it through the archetype's `fieldsAlign="end"` slot rather than
+ * declaring a layout of its own — the value lives once, in `FormScreen.css`.
+ * DEVIATIONS #BC-1.
+ *
+ * Five things are deliberate:
+ *
+ * 1. The consent card is Core's `PrizmaCheckbox size="L"` — the component IS
+ *    the tinted container Figma draws (padding, radius, `Surface/Brand/50`,
+ *    the 28×28 box, the Size-S body). Its `segments` carry the inline
+ *    "Incode's Privacy Policy" link, which opens the document without toggling
+ *    the box. Nothing about the card is composed here.
+ * 2. The box is CONTROLLED by `state`, like every other spec state in this
+ *    package, and the real change event is forwarded through `onConsentChange`
+ *    so a host can drive it. `disabled` is NOT used — the frame draws the card
+ *    on the live surface in both states (#PI-6: never borrow a semantic state
+ *    to make something inert).
+ * 3. The CTA is gated by `ctaDisabled`, Core's own
+ *    `button/primary/surface|text/disabled` treatment, until the box is ticked
+ *    — the behaviour the requesting engineer asked for and the two sibling
+ *    consents already ship. The frame paints Continue blue in both states;
+ *    recorded, not resolved silently (DEVIATIONS #BC-2).
+ * 4. Cancel is the archetype's `tertiary-link` button and emits `secondary`.
+ *    The frame draws it as the Button group's "Tertiary CTA" slot in body-800
+ *    ink with no underline on the ES/PT copies and in brand blue on the EN one
+ *    — Core ships one L tertiary (underlined, `button/tertiary/text/default`)
+ *    and the component wins (DEVIATIONS #BC-4).
+ * 5. The quit confirmation rides archetype E's `overlay` slot: the screen owns
+ *    the scrim and the placement (the foundation's `__sheet-scrim` /
+ *    `__modal-panel` recipes), Core owns the card — `PrizmaModalContent`,
+ *    the `default` variant exactly as the design system documents it: close
+ *    icon, title, optional subtitle, and its own `vertical-v1` Button Group
+ *    (Quit over Cancel). Placed the way Core's presenter places a modal —
+ *    pinned to the bottom of the frame with a Spacing/12 margin, never
+ *    centred — on EVERY platform. The owner ruled out a bottom sheet on the
+ *    phone, then a centred card (Camila, 2026-10-13): "use the default modal
+ *    … so we try with an existing component". The close icon dismisses, the
+ *    same as Cancel. Nothing is drawn behind it that the consent did not
+ *    already draw. DEVIATIONS #BC-7, #BC-8.
+ */
+export declare const BiometricConsentScreen: React.ForwardRefExoticComponent<BiometricConsentScreenProps & React.RefAttributes<HTMLDivElement>>;
+export default BiometricConsentScreen;

package/dist/BiometricConsentScreen.js

@@ -0,0 +1,91 @@
+'use client';
+import { jsx as _jsx, Fragment as _Fragment, jsxs as _jsxs } from "react/jsx-runtime";
+import { forwardRef } from 'react';
+import { PrizmaCheckbox } from '@incodetech/prizma-core-web/checkbox';
+import { PrizmaModalContent } from '@incodetech/prizma-core-web/modal';
+import { PrizmaFormScreen } from './FormScreen';
+import './ScreenLayout.css';
+/**
+ * Biometric Consent — the mandatory biometric-processing consent, built on the
+ * Form archetype (GUIDELINES.md §6-E, `PrizmaFormScreen`).
+ *
+ * ONE screen for the whole `biometricConsent` section (2001:16315): the two
+ * state frames (`empty` 2001:16361, `checked` 2001:16372) share an identical
+ * skeleton — nav → Title (H2 + H5) → one consent card → Continue → Cancel →
+ * tag — and differ ONLY in whether the box is ticked and the CTA released.
+ * Plus the quit confirmation (`quitConfirm`), a Core sheet or dialog presented
+ * over either state when Cancel is pressed.
+ *
+ * WHY ARCHETYPE E. The same reason the sibling consent screen gives: a
+ * `PrizmaCheckbox` is a real `<input type="checkbox">` that joins the form, and
+ * the gated CTA is the whole point of a consent screen — `PrizmaListScreen` has
+ * no `ctaDisabled` slot. E also carries the one tertiary action under the
+ * primary (`linkLabel`), which is exactly where the frame draws Cancel.
+ *
+ * THE CARD SITS AT THE BOTTOM OF THE COLUMN, NOT UNDER THE TITLE. The frame's
+ * middle (2001:15150) is a `justify-between` column: the Title block at the top,
+ * the consent card flush against the CTA band with the frame's Spacing/16
+ * between them, and everything in between left empty. That is the opposite of
+ * every other Form consumer, whose stack hangs off the title, so the screen
+ * SELECTS it through the archetype's `fieldsAlign="end"` slot rather than
+ * declaring a layout of its own — the value lives once, in `FormScreen.css`.
+ * DEVIATIONS #BC-1.
+ *
+ * Five things are deliberate:
+ *
+ * 1. The consent card is Core's `PrizmaCheckbox size="L"` — the component IS
+ *    the tinted container Figma draws (padding, radius, `Surface/Brand/50`,
+ *    the 28×28 box, the Size-S body). Its `segments` carry the inline
+ *    "Incode's Privacy Policy" link, which opens the document without toggling
+ *    the box. Nothing about the card is composed here.
+ * 2. The box is CONTROLLED by `state`, like every other spec state in this
+ *    package, and the real change event is forwarded through `onConsentChange`
+ *    so a host can drive it. `disabled` is NOT used — the frame draws the card
+ *    on the live surface in both states (#PI-6: never borrow a semantic state
+ *    to make something inert).
+ * 3. The CTA is gated by `ctaDisabled`, Core's own
+ *    `button/primary/surface|text/disabled` treatment, until the box is ticked
+ *    — the behaviour the requesting engineer asked for and the two sibling
+ *    consents already ship. The frame paints Continue blue in both states;
+ *    recorded, not resolved silently (DEVIATIONS #BC-2).
+ * 4. Cancel is the archetype's `tertiary-link` button and emits `secondary`.
+ *    The frame draws it as the Button group's "Tertiary CTA" slot in body-800
+ *    ink with no underline on the ES/PT copies and in brand blue on the EN one
+ *    — Core ships one L tertiary (underlined, `button/tertiary/text/default`)
+ *    and the component wins (DEVIATIONS #BC-4).
+ * 5. The quit confirmation rides archetype E's `overlay` slot: the screen owns
+ *    the scrim and the placement (the foundation's `__sheet-scrim` /
+ *    `__modal-panel` recipes), Core owns the card — `PrizmaModalContent`,
+ *    the `default` variant exactly as the design system documents it: close
+ *    icon, title, optional subtitle, and its own `vertical-v1` Button Group
+ *    (Quit over Cancel). Placed the way Core's presenter places a modal —
+ *    pinned to the bottom of the frame with a Spacing/12 margin, never
+ *    centred — on EVERY platform. The owner ruled out a bottom sheet on the
+ *    phone, then a centred card (Camila, 2026-10-13): "use the default modal
+ *    … so we try with an existing component". The close icon dismisses, the
+ *    same as Cancel. Nothing is drawn behind it that the consent did not
+ *    already draw. DEVIATIONS #BC-7, #BC-8.
+ */
+export const BiometricConsentScreen = forwardRef(({ strings, state = 'default', quitConfirm = false, onConsentChange, screenId = quitConfirm ? 'biometric-consent-quit' : `biometric-consent-${state}`, overrides, onAction, ...shell }, ref) => {
+    const accepted = state === 'accepted';
+    const quit = quitConfirm ? (_jsxs(_Fragment, { children: [_jsx("div", { className: "prizma-screen-layout__sheet-scrim", "aria-hidden": "true" }), _jsx("div", { className: "prizma-screen-layout__modal-panel", children: _jsx(PrizmaModalContent, { variant: "default", title: strings.quit.title, subtitle: strings.quit.subtitle, closeLabel: strings.quit.closeLabel, onClose: () => onAction?.({ type: 'secondary', screenId }), buttonGroupProps: {
+                        primaryLabel: strings.quit.confirmLabel,
+                        secondaryLabel: strings.quit.dismissLabel,
+                        onPrimaryClick: () => onAction?.({ type: 'cta', screenId }),
+                        onSecondaryClick: () => onAction?.({ type: 'secondary', screenId }),
+                    } }) })] })) : undefined;
+    return (_jsx(PrizmaFormScreen, { ref: ref, title: strings.consent.title, subtitle: strings.consent.subtitle, 
+        /* The card hangs off the CTA band, not the title — the frame's
+           justify-between middle. Selected from the archetype, not declared. */
+        fieldsAlign: "end", ctaLabel: strings.consent.ctaLabel, 
+        /* "Continue" stays inert until the box is ticked. */
+        ctaDisabled: !accepted, linkLabel: strings.consent.cancelLabel, verifiedLabel: strings.verifiedLabel, navLabel: strings.navLabel, screenId: screenId, overrides: overrides, 
+        /* With the sheet up, the consent's own buttons are under the scrim and
+           must not report: the sheet's two answers are the only actions. */
+        onAction: quitConfirm ? undefined : onAction, overlay: quit, ...shell, children: _jsx(PrizmaCheckbox, { size: "L", checked: accepted, 
+            /* Mandatory for a11y (`aria-required`); the L container never paints
+               a `*` and the frame draws none. */
+            required: true, "aria-label": strings.consent.ariaLabel, segments: strings.consent.body, onCheckedChange: quitConfirm ? undefined : onConsentChange }) }));
+});
+BiometricConsentScreen.displayName = 'BiometricConsentScreen';
+export default BiometricConsentScreen;

package/dist/BiometricConsentStrings.d.ts

@@ -0,0 +1,84 @@
+import type { PrizmaConsentSegment } from '@incodetech/prizma-core-web/checkbox';
+/**
+ * The two states the section draws. Both share ONE layout — nav → Title →
+ * (space) → consent card → Continue → Cancel → tag — and differ only in whether
+ * the box is ticked and, with it, whether Continue is released:
+ *
+ * - `default`  — `biometricConsent.empty` (2001:16361): the box unticked.
+ *                Continue is DISABLED. The frame paints it brand blue; the
+ *                requesting engineer asked for it greyed until the box is
+ *                ticked, "like in Data Sharing Consent" (Uros, #uxp-design
+ *                2026-09-02), which is also what the two sibling consent
+ *                screens do. DEVIATIONS #BC-2 — flip `ctaDisabled` in the
+ *                screen if the frame is the final word.
+ * - `accepted` — `biometricConsent.checked` (2001:16372): the box ticked,
+ *                Continue released to brand blue.
+ *
+ * There is NO refusal state. With Continue gated, "pressed with nothing ticked"
+ * cannot happen, and the file draws no such frame — the sibling modules' added
+ * `rejected` state is deliberately not copied here (DEVIATIONS #BC-3).
+ *
+ * The quit confirmation is NOT a third state: it is a dialog presented over
+ * either state (`quitConfirm` on the screen), because what is underneath — the
+ * box empty or ticked — is whatever the person had before they pressed Cancel.
+ */
+export type BiometricConsentState = 'default' | 'accepted';
+export interface BiometricConsentStrings {
+    /** "verified by" attribution in the footer tag. */
+    verifiedLabel: string;
+    /** Accessible name for the logo nav row. */
+    navLabel?: string;
+    /** The `biometricConsent` section. */
+    consent: {
+        /** H2 ("Request for Biometric Processing"). Centered, per the section. */
+        title: string;
+        /** H5 under the title ("Your verification is powered by Incode…"). The
+         *  section draws one on every frame. */
+        subtitle: string;
+        /**
+         * The consent card's copy, as ordered segments: a plain string renders as
+         * body copy, an object renders as an inline `<a>` that opens the document
+         * WITHOUT toggling the box. Core's own `PrizmaConsentSegment` contract — the
+         * multi-link path on `PrizmaCheckbox size="L"` — so a consent citing two
+         * documents stays expressible (#PI-10: each link is separately actionable).
+         * In production this body arrives from the backend.
+         */
+        body: PrizmaConsentSegment[];
+        /** Accessible name for the box — the card copy is a paragraph, too long to
+         *  serve as one. */
+        ariaLabel?: string;
+        /** Primary CTA ("Continue"). Disabled until the box is ticked. */
+        ctaLabel: string;
+        /** The tertiary action under Continue ("Cancel"). Declining is a hard stop:
+         *  the session cannot process the person's biometrics without this consent. */
+        cancelLabel: string;
+    };
+    /**
+     * The confirmation presented when Cancel is pressed, before the session ends.
+     *
+     * NOT IN THE FIGMA FILE, and not in the shipped Web SDK either — today
+     * `manager.cancel()` ends the session the moment Cancel is tapped. Added at
+     * the owner's request (Camila, 2026-10-13): Cancel is irreversible here, the
+     * person cannot be verified without the consent, and a mis-tap on the
+     * tertiary under Continue should not cost them the session. It is Core's
+     * Modal, `default` variant, on EVERY platform — the existing component as
+     * the design system documents it, close icon and all, pinned to the bottom
+     * of the frame the way Core's presenter places it; not a bottom sheet and
+     * not a centred card (owner calls, same day). The copy is the
+     * SDK's own close dialog (`page.close.confirmQuit` / `page.close.confirm` /
+     * `page.close.cancel`), so nothing is invented. DEVIATIONS #BC-7.
+     */
+    quit: {
+        /** Dialog title ("Are you sure you want to quit?"). */
+        title: string;
+        /** Optional supporting line. The SDK's close dialog carries none. */
+        subtitle?: string;
+        /** The destructive confirmation ("Quit") — primary, on top. */
+        confirmLabel: string;
+        /** Dismiss and stay on the consent ("Cancel") — secondary, below it. */
+        dismissLabel: string;
+        /** Accessible name of the card's close icon ("Close"), which also
+         *  dismisses. Core's Default modal always draws the icon. */
+        closeLabel: string;
+    };
+}

package/dist/BiometricConsentStrings.js

@@ -0,0 +1,31 @@
+// Biometric Consent — copy contract.
+//
+// The mandatory biometric consent the BACKEND decides to show — at the start of
+// a flow, or right after ID capture — when the session comes from a protected
+// geography (Illinois BIPA and the handful of states like it), or when the state
+// on the captured ID says so. It is NOT the User Consent / Data Sharing Consent
+// module: it is the flow builder's "Required biometric consent" setting, it uses
+// its own endpoint, and declining it is a hard stop. Uros Milivojevic
+// (#uxp-design, 2026-09-01): "Compared to User Consent it has a Cancel button
+// next to Continue, a subtitle, and a long consent body loaded from the BE with
+// tappable links (tapping the body also toggles the checkbox)."
+//
+// Figma: `Biometric Consent Screen` (vXvIMQF5DSJgkQHhFAQcWC), section
+// `biometricConsent` (2001:16315). ONE screen, drawn across:
+//   · 2001:16361 `biometricConsent.empty`    the master — box unticked
+//   · 2001:16372 `biometricConsent.checked`  the box ticked
+//   · `🔧 Behavior`, `🖤 Dark mode`, `🇪🇸 ES`, `🇵🇹 PT` and the six device
+//     sections are the same two states re-presented: dark is token-driven
+//     (`[data-prizma-theme='dark']`), the locales are the host's locale pack,
+//     and the widths are excluded by the no-per-width-variants rule (DEVIATIONS
+//     #17).
+//
+// The screen is: nav → Title (H2 + H5 subtitle) → one consent card pinned to
+// the BOTTOM of the column → Continue → Cancel → tag. No disclosure paragraph —
+// unlike the consent screen the two sibling modules share, the legal body here
+// lives INSIDE the card, and the backend supplies it.
+//
+// No hardcoded English anywhere in a screen: every visible string arrives here,
+// so the host's locale pack drives the module (the Figma file ships ES + PT
+// columns beside the EN one).
+export {};

package/dist/CaptureScreen.d.ts

@@ -27,6 +27,19 @@ export interface PrizmaCaptureScreenProps extends Omit<PrizmaScreenShellProps, '
     manualFeedbackText?: string;
     /** Per-state status copy (uploading / success / error / warning). */
     statusLabels?: Partial<Record<PrizmaSelfieCaptureState, string>>;
+    /**
+     * A notice band above the footer — a Snackbar the module raises over the live
+     * feed without taking the camera away (Face Capture's "Need more time?" offer
+     * is the first consumer).
+     *
+     * ANCHORED, like the footer and the control strip, and for the same reason:
+     * the owner's rule is that anchored chrome sits at the same position on every
+     * screen (2026-08-18). Flowing it would push Core's ring up, and the ring
+     * offset is the one thing this archetype is forbidden to touch
+     * (DEVIATIONS #12). It rides the empty band under the instruction line, which
+     * is where the module Figma puts it.
+     */
+    notice?: ReactNode;
     /** "verified by" attribution copy for the footer tag. */
     verifiedLabel: string;
     navLabel?: string;

package/dist/CaptureScreen.js

@@ -19,12 +19,12 @@ import './ScreenLayout.css';
  * loading and result screens of a capture module use this archetype too —
  * not the centered Processing archetype (DEVIATIONS #11).
  */
-export const PrizmaCaptureScreen = forwardRef(({ showHeader, showFooter = true, cameraOpen = true, state, camera, feedbackText, isManual, manualFeedbackText, statusLabels, verifiedLabel, navLabel, screenId, overrides, onAction, ...shell }, ref) => (
+export const PrizmaCaptureScreen = forwardRef(({ showHeader, showFooter = true, cameraOpen = true, state, camera, feedbackText, isManual, manualFeedbackText, statusLabels, notice, verifiedLabel, navLabel, screenId, overrides, onAction, ...shell }, ref) => (
 // Pin light ONLY while the camera feed is open: Core paints the live
 // capture area with Static inks because "the capture screen stays WHITE in
 // both modes — light is needed for the shot" (SelfieCapture.css, owner
 // 2026-07-14). Feed-closed screens are ordinary screens and follow the app.
 // DEVIATIONS #F-27.
-_jsxs(PrizmaScreenShell, { ref: ref, theme: cameraOpen ? 'light' : undefined, ...shell, children: [_jsx(PrizmaScreenNav, { reserved: !(showHeader ?? (cameraOpen ? Boolean(overrides?.logo) : true)), logo: overrides?.logo, navLabel: navLabel }), _jsxs("div", { className: "prizma-screen-layout__content prizma-screen-layout__content--capture", children: [_jsx(PrizmaSelfieCapture, { state: state, camera: camera, showFeedback: Boolean(feedbackText ?? manualFeedbackText), feedbackText: feedbackText, isManual: isManual, manualFeedbackText: manualFeedbackText, statusLabels: statusLabels }), showFooter ? (_jsx("div", { className: "prizma-screen-layout__footer prizma-screen-layout__footer--pinned", children: _jsx(PrizmaTag, { label: verifiedLabel }) })) : null] })] })));
+_jsxs(PrizmaScreenShell, { ref: ref, theme: cameraOpen ? 'light' : undefined, ...shell, children: [_jsx(PrizmaScreenNav, { reserved: !(showHeader ?? (cameraOpen ? Boolean(overrides?.logo) : true)), logo: overrides?.logo, navLabel: navLabel }), _jsxs("div", { className: "prizma-screen-layout__content prizma-screen-layout__content--capture", children: [_jsx(PrizmaSelfieCapture, { state: state, camera: camera, showFeedback: Boolean(feedbackText ?? manualFeedbackText), feedbackText: feedbackText, isManual: isManual, manualFeedbackText: manualFeedbackText, statusLabels: statusLabels }), notice ? (_jsx("div", { className: "prizma-screen-layout__capture-notice", children: notice })) : null, showFooter ? (_jsx("div", { className: "prizma-screen-layout__footer prizma-screen-layout__footer--pinned", children: _jsx(PrizmaTag, { label: verifiedLabel }) })) : null] })] })));
 PrizmaCaptureScreen.displayName = 'PrizmaCaptureScreen';
 export default PrizmaCaptureScreen;

package/dist/CurpEnterScreen.d.ts

@@ -46,6 +46,13 @@ export interface CurpEnterScreenProps extends Omit<PrizmaFormScreenProps, 'title
  * `linkContent` slot: no primitive is invented, no layout is declared, and the
  * two actions stay distinguishable (`cta` vs `secondary`, the #PI-10 rule).
  * The gap is reported for promotion — see the module's DEVIATIONS rows.
+ *
+ * `emptyError` is the empty-submit state (rule from Elena, 2026-09-30,
+ * GUIDELINES §6-E empty-submit rule): "Continue" was pressed with nothing
+ * typed. The field renders empty with no placeholder, in Core's error state
+ * with `requiredError`, and the primary CTA is disabled, following the drawn
+ * precedent in `FormsFieldScreen`. The resting `default` keeps the CTA enabled
+ * so the user can reach this state.
  */
 export declare const CurpEnterScreen: React.ForwardRefExoticComponent<CurpEnterScreenProps & React.RefAttributes<HTMLDivElement>>;
 export default CurpEnterScreen;

package/dist/CurpEnterScreen.js

@@ -37,6 +37,13 @@ import './CurpLayout.css';
  * `linkContent` slot: no primitive is invented, no layout is declared, and the
  * two actions stay distinguishable (`cta` vs `secondary`, the #PI-10 rule).
  * The gap is reported for promotion — see the module's DEVIATIONS rows.
+ *
+ * `emptyError` is the empty-submit state (rule from Elena, 2026-09-30,
+ * GUIDELINES §6-E empty-submit rule): "Continue" was pressed with nothing
+ * typed. The field renders empty with no placeholder, in Core's error state
+ * with `requiredError`, and the primary CTA is disabled, following the drawn
+ * precedent in `FormsFieldScreen`. The resting `default` keeps the CTA enabled
+ * so the user can reach this state.
  */
 export const CurpEnterScreen = forwardRef(({ strings, state = 'default', value, screenId = `curp-enter-${state}`, className, overrides, onAction, ...shell }, ref) => {
     // Figma treats the five sections as four distinct field treatments:
@@ -47,6 +54,9 @@ export const CurpEnterScreen = forwardRef(({ strings, state = 'default', value,
     // surface.
     const busy = state === 'loading';
     const invalid = state === 'error';
+    // Empty submit: the field stays empty, drops its placeholder and takes
+    // Core's error state with the shared "required" row; the CTA greys.
+    const emptyError = state === 'emptyError';
     const focused = state === 'focused' || state === 'filled';
     return (_jsx(PrizmaFormScreen, { ref: ref, 
         /* Scopes the one module rule that lets the `error` section keep the
@@ -63,11 +73,15 @@ export const CurpEnterScreen = forwardRef(({ strings, state = 'default', value,
             .filter(Boolean)
             .join(' '), title: strings.enter.title, subtitle: strings.enter.subtitle, ctaLabel: strings.enter.ctaLabel, 
         /* The `loading` section swaps the CTA label for Core's spinner. */
-        ctaLoading: busy, ctaLoadingLabel: strings.enter.ctaLoadingLabel, linkContent: _jsx(PrizmaButton, { variant: "secondary", size: "L", 
+        ctaLoading: busy, ctaDisabled: emptyError, ctaLoadingLabel: strings.enter.ctaLoadingLabel, linkContent: _jsx(PrizmaButton, { variant: "secondary", size: "L", 
             /* Figma greys this action too while the lookup runs. */
-            disabled: busy, onClick: () => onAction?.({ type: 'secondary', screenId }), children: strings.enter.noCurpLabel }), verifiedLabel: strings.verifiedLabel, navLabel: strings.navLabel, screenId: screenId, overrides: overrides, onAction: onAction, ...shell, children: _jsx(PrizmaTextField, { className: focused ? 'prizma-input-textfield--focused' : undefined, "aria-label": strings.enter.fieldLabel, placeholder: strings.enter.placeholder, defaultValue: value ?? '', 
+            disabled: busy, onClick: () => onAction?.({ type: 'secondary', screenId }), children: strings.enter.noCurpLabel }), verifiedLabel: strings.verifiedLabel, navLabel: strings.navLabel, screenId: screenId, overrides: overrides, onAction: onAction, ...shell, children: _jsx(PrizmaTextField, { className: focused ? 'prizma-input-textfield--focused' : undefined, "aria-label": strings.enter.fieldLabel, placeholder: emptyError ? undefined : strings.enter.placeholder, defaultValue: emptyError ? '' : value ?? '', 
             /* A CURP is an 18-character uppercase key. */
-            autoCapitalize: "characters", autoComplete: "off", spellCheck: false, disabled: busy, error: invalid, errorText: invalid ? strings.enter.errorText : undefined, 
+            autoCapitalize: "characters", autoComplete: "off", spellCheck: false, disabled: busy, error: invalid || emptyError, errorText: invalid
+                ? strings.enter.errorText
+                : emptyError
+                    ? strings.requiredError
+                    : undefined, 
             /* The clear ✕ is drawn only on the error section (76:36434); the
                `filled` section (79:1553) draws none. Core still owns WHEN it
                shows — its `--show` state needs a value in the field. */

package/dist/CurpGenerateScreen.d.ts

@@ -42,6 +42,14 @@ export interface CurpGenerateScreenProps extends Omit<PrizmaFormScreenProps, 'ti
  * The `dropdown` section IS the open-menu spec state, which Core exposes as the
  * documentation-only `forceOpen` (a screen is one static state, never a live
  * interaction) — the same mechanism Phone Input's `countryCode` section uses.
+ *
+ * `emptyError` is the empty-submit state (rule from Elena, 2026-09-30,
+ * GUIDELINES §6-E empty-submit rule): "Generate" was pressed with the form
+ * empty. All six fields carry the required `*`, so all six render empty with no
+ * placeholder, in Core's error state with `requiredError`; no menu is open and
+ * the primary CTA is disabled, following the drawn precedent in
+ * `FormsFieldScreen`. The resting `default` keeps the CTA enabled so the user
+ * can reach this state.
  */
 export declare const CurpGenerateScreen: React.ForwardRefExoticComponent<CurpGenerateScreenProps & React.RefAttributes<HTMLDivElement>>;
 export default CurpGenerateScreen;

package/dist/CurpGenerateScreen.js

@@ -29,29 +29,44 @@ import './CurpLayout.css';
  * The `dropdown` section IS the open-menu spec state, which Core exposes as the
  * documentation-only `forceOpen` (a screen is one static state, never a live
  * interaction) — the same mechanism Phone Input's `countryCode` section uses.
+ *
+ * `emptyError` is the empty-submit state (rule from Elena, 2026-09-30,
+ * GUIDELINES §6-E empty-submit rule): "Generate" was pressed with the form
+ * empty. All six fields carry the required `*`, so all six render empty with no
+ * placeholder, in Core's error state with `requiredError`; no menu is open and
+ * the primary CTA is disabled, following the drawn precedent in
+ * `FormsFieldScreen`. The resting `default` keeps the CTA enabled so the user
+ * can reach this state.
  */
 export const CurpGenerateScreen = forwardRef(({ strings, state = 'default', values, genders = [], states = [], screenId = `curp-generate-${state}`, className, overrides, onAction, ...shell }, ref) => {
     const copy = strings.generate;
+    // Empty submit: every required field drops its value and placeholder and
+    // takes Core's error state with the shared "required" row; the CTA greys.
+    const emptyError = state === 'emptyError';
+    const ph = (placeholder) => (emptyError ? undefined : placeholder);
+    const err = {
+        error: emptyError,
+        errorText: emptyError ? strings.requiredError : undefined,
+    };
     return (_jsxs(PrizmaFormScreen, { ref: ref, 
-        /* Scopes the two module rules in CurpLayout.css (see the foundation and
-           Core requests recorded there):
-           - `--scroll` lets the six-field stack scroll inside the 844 frame
-             instead of overflowing its box and painting over the CTA. EVERY
-             section gets it, `dropdown` included — Figma draws "Generate"
-             clear and unobstructed under the open menu.
-           - `--menu-open` flips Core's absolutely-positioned menu above its
-             trigger on the one section that forces it open, so the three
-             gender rows stay inside the scrolling column. */
-        className: [
+        /* The six-field stack scrolls inside the 844 frame through the
+           foundation's `scrollFields` (overflow + the Spacing/16 that keeps the
+           cut clear of "Generate"). EVERY section gets it, `dropdown` included:
+           Figma draws "Generate" clear and unobstructed under the open menu.
+           It replaces the module's old `--scroll` rule, which scrolled but
+           carried no spacing, so the last field ran flush into the button.
+           `--menu-open` (CurpLayout.css) flips Core's absolutely-positioned
+           menu above its trigger on the one section that forces it open, so
+           the three gender rows stay inside the scrolling column. */
+        scrollFields: true, className: [
             'curp-generate',
-            'curp-generate--scroll',
             state === 'dropdown' ? 'curp-generate--menu-open' : '',
             className,
         ]
             .filter(Boolean)
-            .join(' '), title: copy.title, subtitle: copy.subtitle, ctaLabel: copy.ctaLabel, ctaLoadingLabel: copy.ctaLoadingLabel, verifiedLabel: strings.verifiedLabel, navLabel: strings.navLabel, screenId: screenId, overrides: overrides, onAction: onAction, ...shell, children: [_jsx(PrizmaTextField, { label: copy.firstName.label, placeholder: copy.firstName.placeholder, required: true, requiredHint: strings.requiredHint, autoComplete: "off", defaultValue: values?.firstName ?? '' }), _jsx(PrizmaTextField, { label: copy.firstLastName.label, placeholder: copy.firstLastName.placeholder, required: true, requiredHint: strings.requiredHint, autoComplete: "off", defaultValue: values?.firstLastName ?? '' }), _jsx(PrizmaTextField, { label: copy.secondLastName.label, placeholder: copy.secondLastName.placeholder, required: true, requiredHint: strings.requiredHint, autoComplete: "off", defaultValue: values?.secondLastName ?? '' }), _jsx(PrizmaDropdown, { label: copy.gender.label, placeholder: copy.gender.placeholder, required: true, requiredHint: strings.requiredHint, options: genders, defaultValue: values?.gender ?? null, searchPlaceholder: copy.gender.searchPlaceholder, 
+            .join(' '), title: copy.title, subtitle: copy.subtitle, ctaLabel: copy.ctaLabel, ctaDisabled: emptyError, ctaLoadingLabel: copy.ctaLoadingLabel, verifiedLabel: strings.verifiedLabel, navLabel: strings.navLabel, screenId: screenId, overrides: overrides, onAction: onAction, ...shell, children: [_jsx(PrizmaTextField, { label: copy.firstName.label, placeholder: ph(copy.firstName.placeholder), required: true, requiredHint: strings.requiredHint, autoComplete: "off", defaultValue: emptyError ? '' : values?.firstName ?? '', ...err }), _jsx(PrizmaTextField, { label: copy.firstLastName.label, placeholder: ph(copy.firstLastName.placeholder), required: true, requiredHint: strings.requiredHint, autoComplete: "off", defaultValue: emptyError ? '' : values?.firstLastName ?? '', ...err }), _jsx(PrizmaTextField, { label: copy.secondLastName.label, placeholder: ph(copy.secondLastName.placeholder), required: true, requiredHint: strings.requiredHint, autoComplete: "off", defaultValue: emptyError ? '' : values?.secondLastName ?? '', ...err }), _jsx(PrizmaDropdown, { label: copy.gender.label, placeholder: ph(copy.gender.placeholder), required: true, requiredHint: strings.requiredHint, options: genders, defaultValue: emptyError ? null : values?.gender ?? null, ...err, searchPlaceholder: copy.gender.searchPlaceholder, 
                 /* The `dropdown` section is the open Gender menu. */
-                forceOpen: state === 'dropdown' }), _jsx(PrizmaDateField, { label: copy.dateOfBirth.label, placeholder: copy.dateOfBirth.placeholder, required: true, requiredHint: strings.requiredHint, calendarLabel: copy.dateOfBirth.calendarLabel, defaultValue: values?.dateOfBirth ?? '' }), _jsx(PrizmaDropdown, { label: copy.birthState.label, placeholder: copy.birthState.placeholder, required: true, requiredHint: strings.requiredHint, options: states, defaultValue: values?.birthState ?? null, searchable: true, searchPlaceholder: copy.birthState.searchPlaceholder })] }));
+                forceOpen: state === 'dropdown' }), _jsx(PrizmaDateField, { label: copy.dateOfBirth.label, placeholder: ph(copy.dateOfBirth.placeholder), required: true, requiredHint: strings.requiredHint, calendarLabel: copy.dateOfBirth.calendarLabel, defaultValue: emptyError ? '' : values?.dateOfBirth ?? '', ...err }), _jsx(PrizmaDropdown, { label: copy.birthState.label, placeholder: ph(copy.birthState.placeholder), required: true, requiredHint: strings.requiredHint, options: states, defaultValue: emptyError ? null : values?.birthState ?? null, ...err, searchable: true, searchPlaceholder: copy.birthState.searchPlaceholder })] }));
 });
 CurpGenerateScreen.displayName = 'CurpGenerateScreen';
 export default CurpGenerateScreen;

package/dist/CurpLayout.css

@@ -1,6 +1,6 @@
 /* CURP — module layout additions.
  *
- * THREE rules, and none of them declares spacing: the content column, the 24px
+ * TWO rules, and none of them declares spacing: the content column, the 24px
  * gutters, the title → fields Spacing/32, the field gaps, the CTA column and
  * the anchored footer all stay the foundation's (`ScreenLayout.css`,
  * `FormScreen.css`). Nothing here re-declares an archetype value, invents a
@@ -10,40 +10,14 @@
  */
 
 /* ── The generator's field stack is taller than the screen ───────────────────
- * `CURP.Gene.default` is a 1051-tall frame: its `input-list` alone is 548 tall
- * (six 78px labelled fields at Spacing/16) and the CONTENT frame grows to 861
- * instead of the usual 654. At the 390×844 reference the column has ~470 for
- * it, so the last dropdown and the CTA fall past the fold.
- *
- * Archetype E's `.prizma-form-screen__fields` is `flex: 1; min-height: 0` with
- * no overflow behaviour — it was measured against Phone Input, whose forms are
- * one or two fields — so the surplus is silently clipped by `ScreenShell`'s
- * `overflow: hidden`, and (because the fields cannot shrink below
- * `--prizma-input-size-field-height`) it first PAINTS OVER the sibling CTA.
- * Screens are authored at 390×844 and never reflow (README / DEVIATIONS #17),
- * so growing the frame is not an option either.
- *
- * The stack is therefore allowed to scroll INSIDE the column: the title, the
- * CTA and the anchored tag stay put and the six fields pan, which is the
- * closest a fixed 844 frame gets to Figma's taller page. It adds NO padding, NO
- * gap and NO size of its own.
- *
- * Applied to EVERY `CURP.Gene.*` section including `dropdown`. The earlier
- * build withheld it from `dropdown` to keep Core's absolutely-positioned menu
- * from being clipped, and that traded one clipped element for a worse one: with
- * `overflow: visible` the 548-tall stack overflowed its box and painted the
- * open menu straight across the "Generate" button, which Figma (2058:16373)
- * draws clear and unobstructed under the menu. The CTA is never allowed to be
- * overlapped; the menu is handled by the next rule instead.
- *
- * FOUNDATION REQUEST: promote this to `FormScreen.css` as a
- * `.prizma-form-screen__fields--scroll` variant (or make overflow the default),
- * driven by a `scrollFields` prop on `PrizmaFormScreen`. Every long-form module
- * still to come in Wave 3 — eKYC, eKYB, address entry — will hit the same wall.
+ * `CURP.Gene.default` is a 1051-tall frame (six 78px labelled fields at
+ * Spacing/16), so at 390×844 the stack scrolls inside the column. That is the
+ * foundation's `scrollFields` on `PrizmaFormScreen` now (FormScreen.css
+ * `__fields--scroll`), which also carries the Spacing/16 between the cut and
+ * the CTA. The module used to hand-roll `overflow-y: auto` here with no
+ * spacing, so the last field ran flush into "Generate" (Elena, 2026-09-30).
+ * Removed in favour of the foundation rule.
  */
-.curp-generate--scroll .prizma-form-screen__fields {
-  overflow-y: auto;
-}
 
 /* ── The open Gender menu must stay inside the scrolling column ──────────────
  * `CURP.Gene.dropdown` exists to show the three gender rows, so they may not be

package/dist/CurpStrings.d.ts

@@ -11,15 +11,23 @@
  * - `error`   — negative field + clear ✕ + the "Invalid CURP" row
  * - `loading` — both actions inert while the lookup runs; the spinner rides the
  *   CTA, never the field (the Phone Input lesson, DEVIATIONS #PI-5)
+ * - `emptyError` — "Continue" pressed with the field still empty: the field
+ *   stays empty (no placeholder) in Core's error state with `requiredError`,
+ *   and the CTA is disabled. GUIDELINES §6-E empty-submit rule (Elena,
+ *   2026-09-30).
  */
-export type CurpEnterState = 'default' | 'focused' | 'filled' | 'error' | 'loading';
+export type CurpEnterState = 'default' | 'focused' | 'filled' | 'error' | 'loading' | 'emptyError';
 /**
  * The `CURP.Gene.*` form sections — the six-field generator:
  * - `default`  — every field empty on its placeholder
  * - `dropdown` — the Gender menu open over the form (Core's `forceOpen`)
  * - `filled`   — every field carrying a value
+ * - `emptyError` — "Generate" pressed with the form still empty: every required
+ *   field stays empty (no placeholder) in Core's error state with
+ *   `requiredError`, no menu is open, and the CTA is disabled. GUIDELINES §6-E
+ *   empty-submit rule (Elena, 2026-09-30).
  */
-export type CurpGenerateState = 'default' | 'dropdown' | 'filled';
+export type CurpGenerateState = 'default' | 'dropdown' | 'filled' | 'emptyError';
 /**
  * The two spinner sections. `verifying` is `CURP.EnterCURP.veryfing` (the
  * Figma layer name carries the typo); `generating` is `CURP.Gene.generating`.
@@ -73,6 +81,12 @@ export interface CurpStrings {
      * the marker is localizable and never hardcoded in a screen.
      */
     requiredHint?: string;
+    /**
+     * Error row under every required field left empty when the primary CTA is
+     * pressed (the `emptyError` state of the entry and generator forms):
+     * "This field is required". SDK key `dynamicForms.fieldRequired`.
+     */
+    requiredError: string;
     /** CURP.EnterCURP.{default,focused,filled,error,loading} */
     enter: {
         /** H2 ("Enter your CURP"). */

package/dist/DemoScreensLayout.css

@@ -389,6 +389,22 @@
   background: var(--prizma-surface-neutral-50);
   align-items: center;
   justify-content: center;
+  /* The card hugs its content and is taller than a short window: on the Duo
+   * open full screen (626) unsafe centring put 90px of it above the page and
+   * 90 below, heading cut off (sweep 2026-10-20). `safe` starts the card at
+   * the top of the page when it does not fit, and does nothing when it does
+   * (#F-37, same mechanism). The plain `center` is the fallback. */
+  justify-content: safe center;
+}
+
+/* …and under 720 the page scrolls, as a desktop page does when the window is
+ * shorter than its content. The shell is `overflow: hidden` for the screens
+ * that pin chrome to its edges; this page pins nothing, the tag rides in the
+ * card's band. */
+@container pcs-screen (max-height: 720px) {
+  .prizma-screen-shell.demo-screens-redirect {
+    overflow-y: auto;
+  }
 }
 
 .demo-screens-redirect__card {

package/dist/DemoScreensRedirectScreen.d.ts

@@ -13,8 +13,13 @@ import './DemoScreensLayout.css';
  *  - `resend`    "Link sent!", resend available
  *  - `resent`    "Link sent!" with the "resent" snackbar
  *  - `tooMany`   "Too many attempts"
+ *  - `invalidUuid` the link's UUID was rejected (expired or unknown): no leg
+ *                to offer, only the error. One message for Flows and
+ *                Workflows alike, since the backend answers the same way for
+ *                both (Elena, 2026-10-21: web SDK 2.0 showed "QR code
+ *                expired" for Flows and "Session expired" with 2.0 off).
  */
-export type DemoScreensRedirectStage = 'qr' | 'sms' | 'smsFilled' | 'sent' | 'resend' | 'resent' | 'tooMany';
+export type DemoScreensRedirectStage = 'qr' | 'sms' | 'smsFilled' | 'sent' | 'resend' | 'resent' | 'tooMany' | 'invalidUuid';
 export interface DemoScreensRedirectScreenProps extends Omit<PrizmaScreenShellProps, 'dark' | 'title' | 'children'> {
     /** Family copy — this screen reads the `redirect` slice. */
     strings: DemoScreensStrings;