@incodetech/prizma-core-screens 0.2.7 → 0.2.12

package/dist/DigitalIdUploadReviewScreen.js

@@ -0,0 +1,44 @@
+'use client';
+import { jsx as _jsx } from "react/jsx-runtime";
+import { forwardRef } from 'react';
+import { PrizmaCaptureDigitalId } from '@incodetech/prizma-core-web/capture-digital-id';
+import { PrizmaReviewScreen } from './ReviewScreen';
+import './ScreenLayout.css';
+/**
+ * Digital ID Upload — review / analyzing / success, built on the
+ * `PrizmaReviewScreen` archetype (GUIDELINES.md §6-H). Figma: `Upload Digital
+ * ID` file (wxFsHRvllern4VnjRqM4JO), "Web Happy Path - Light Mode" section —
+ * `Review Document` / `Analyzing` / `Success` (nodes 25351:14725/6/7).
+ *
+ * The media stage is Core's `PrizmaCaptureDigitalId` across all three stages
+ * — its own state enum (`review` / `analyzing` / `success`) maps directly
+ * onto the archetype's stage axis, so it already owns the border treatment
+ * (neutral on review, green 4px on analyzing/success), the scan-flash sweep
+ * and the filename row. Nothing is hand-built here, unlike
+ * `DocumentCaptureConfirmUploadScreen`'s bespoke file-card — Core ships a
+ * purpose-built component for this module.
+ *
+ * Header/footer visibility is genuinely per-stage in this Figma (logo nav +
+ * verified tag show on `review`, both are absent on `analyzing` and
+ * `success`) — not a layout choice this file invents, just the existing
+ * `showHeader`/`showFooter` chrome knobs (owner rule 2026-08-18: header and
+ * footer are independently controlled) applied per stage.
+ *
+ * Always opts into the archetype's `centeredWhenNoNav` — it only takes effect
+ * while the nav is hidden (`analyzing`/`success` here), where this Figma
+ * draws the header + media as one group centred with equal space above and
+ * below it, not a pinned header (see ReviewScreen.tsx for the mechanics).
+ * `review` always shows its own nav, so the flag is a no-op there, and the
+ * default `false` leaves Document Capture's existing analyzing/success
+ * screens byte-for-byte unchanged (neither ever hides the nav here).
+ *
+ * GAP (report, not workaround — README rule 2): Figma's `Success` section
+ * also shows a subtitle ("Let's continue") under the success title, but the
+ * shared `PrizmaReviewScreen` archetype only renders a subtitle on
+ * `stage="review"` — every other current consumer's success state has none.
+ * Left unset here pending an owner call on whether to extend the shared
+ * archetype with a `successSubtitle` slot.
+ */
+export const DigitalIdUploadReviewScreen = forwardRef(({ strings, stage = 'review', filename, progress = 45, showHeader = stage === 'review', showFooter = stage === 'review', screenId = `digital-id-upload-${stage}`, overrides, onAction, ...shell }, ref) => (_jsx(PrizmaReviewScreen, { ref: ref, stage: stage, title: strings.review.title, subtitle: strings.review.subtitle, successTitle: strings.review.successTitle, analyzingLabel: strings.review.analyzingLabel, centeredWhenNoNav: true, progress: progress, primaryLabel: strings.review.ctaLabel, secondaryLabel: strings.review.replaceLabel, verifiedLabel: strings.verifiedLabel, navLabel: strings.navLabel, showHeader: showHeader, showFooter: showFooter, screenId: screenId, overrides: overrides, onAction: onAction, ...shell, children: _jsx(PrizmaCaptureDigitalId, { state: stage, filename: filename }) })));
+DigitalIdUploadReviewScreen.displayName = 'DigitalIdUploadReviewScreen';
+export default DigitalIdUploadReviewScreen;

package/dist/DigitalIdUploadStrings.d.ts

@@ -0,0 +1,64 @@
+/** The three stages the confirm flow's screen shares — matches
+ *  `PrizmaReviewScreen`'s own `PrizmaReviewStage` (ReviewScreen.tsx). Kept as
+ *  a separate module-scoped type rather than importing it, same convention as
+ *  `DocumentCaptureConfirmStage` (DocumentCaptureStrings.ts). */
+export type DigitalIdUploadConfirmStage = 'review' | 'analyzing' | 'success';
+export interface DigitalIdUploadStrings {
+    /** Accessible name for the logo nav region (i18n — no baked-in English). */
+    navLabel?: string;
+    /** "verified by" attribution copy for the footer tag. */
+    verifiedLabel: string;
+    /** `Tutorial Screen` (node 25351:14722). */
+    tutorial: {
+        title: string;
+        subtitle?: string;
+        /** "Upload PDF" */
+        ctaLabel: string;
+    };
+    /** `Review Document` / `Analyzing` / `Success` (nodes
+     *  25351:14725/14726/14727) — one screen, three stages. */
+    review: {
+        /** `review` title ("Review document"). */
+        title: string;
+        /** `review` description. Figma draws no subtitle on `analyzing` or
+         *  `success` — the shared `PrizmaReviewScreen` archetype already only
+         *  shows one on `review`, so this needs no per-stage handling here. */
+        subtitle?: string;
+        /** Loading-bar caption on `analyzing` ("Analyzing.."). */
+        analyzingLabel: string;
+        /** H2 on `success` ("Successfully processed!"). */
+        successTitle: string;
+        /** Secondary CTA on `review` ("Replace file"). */
+        replaceLabel: string;
+        /** Primary CTA on `review` / `success` ("Continue"). */
+        ctaLabel: string;
+    };
+    /** `Errors` section, `Error` frame (node 25874:11957) — the uploaded file
+     *  itself was rejected (wrong document type). Built on the SAME
+     *  `PrizmaReviewScreen` archetype as `review`, stage `"error"`: the card
+     *  reuses `PrizmaCaptureDigitalId state="error"` (red 4px border), not a
+     *  generic archetype-F verdict screen (DigitalIdUploadErrorScreen.tsx). */
+    error: {
+        /** "ID type is not accepted" */
+        title: string;
+        /** "Please try scanning a different document" */
+        subtitle?: string;
+        /** "Scan your ID" */
+        ctaLabel: string;
+    };
+    /** `Errors` section, `File Limit Error` frame (node 26083:3981) — the file
+     *  was never uploaded at all (client-side size check), so there is no
+     *  rejected document to show. Built on Archetype F (`PrizmaResultScreen`,
+     *  ResultScreen.tsx) rather than the review archetype `error` uses above —
+     *  Figma centres the status + title + subtitle in the full available
+     *  height with no media stage at all, exactly F's shape, not H's
+     *  header-above-a-card one (DigitalIdUploadFileTooLargeScreen.tsx). */
+    fileTooLarge: {
+        /** "File is too large" */
+        title: string;
+        /** "The selected file is larger than 5 MB, please upload a smaller one" */
+        subtitle?: string;
+        /** "Choose another file" */
+        ctaLabel: string;
+    };
+}

package/dist/DigitalIdUploadStrings.js

@@ -0,0 +1,19 @@
+// Digital ID Upload module — copy contract.
+//
+// Every Digital ID Upload screen receives the SAME `strings:
+// DigitalIdUploadStrings` object (rule: all copy via props, no hardcoded
+// English — GUIDELINES.md §9).
+//
+// Authoritative screens: the "Web Happy Path - Light Mode" purple section of
+// the Upload Digital ID Figma file (wxFsHRvllern4VnjRqM4JO, node 25351:14721)
+// — covers `tutorial` and the `review` / `analyzing` / `success` stages of
+// the confirm flow — plus TWO separate `Errors` sections: node 25874:11955
+// (`ID type is not accepted`) and node 26083:3981 (`File Limit Error`, "File
+// is too large"). Three frames of the happy-path section are NOT part of
+// this contract: `1-1-1-how to verify` (a verification-method chooser shared
+// with ID Capture — see IdCaptureDocumentSelectionScreen.tsx, which is one
+// row short of this Figma's version), a native iOS file-browser frame (OS
+// chrome, DEVIATIONS.md #DC-20 precedent), and `1-18-1-id-hold-on` (ID
+// Capture's own server-side-wait screen — dropped from this module by
+// product decision, not a gap to fill).
+export {};

package/dist/DigitalIdUploadTutorialScreen.d.ts

@@ -0,0 +1,28 @@
+import React from 'react';
+import { type PrizmaTutorialScreenProps } from './TutorialScreen';
+import type { PrizmaScreenActionHandler, PrizmaScreenOverrides } from './types';
+import type { DigitalIdUploadStrings } from './DigitalIdUploadStrings';
+import './ScreenLayout.css';
+export interface DigitalIdUploadTutorialScreenProps extends Omit<PrizmaTutorialScreenProps, 'title' | 'subtitle' | 'ctaLabel' | 'illustration' | 'verifiedLabel' | 'navLabel'> {
+    /** Module copy — this screen reads the `tutorial` slice (+ shared labels). */
+    strings: DigitalIdUploadStrings;
+    screenId?: string;
+    overrides?: PrizmaScreenOverrides;
+    onAction?: PrizmaScreenActionHandler;
+}
+/**
+ * Digital ID Upload — tutorial, built on the `PrizmaTutorialScreen` archetype
+ * (GUIDELINES.md §6-A). Figma: `Upload Digital ID` file
+ * (wxFsHRvllern4VnjRqM4JO), "Web Happy Path - Light Mode" section, `Tutorial
+ * Screen` (node 25351:14722).
+ *
+ * The illustration slot is Core's own `PrizmaCaptureDigitalId` in its
+ * `tutorial` state — the Figma file names this exact instance "Capture /
+ * Digital ID" (node 26161:10686, Figma description: "Incode specific
+ * component for Digital ID module experience"), the same managed component
+ * already shipped as `core/platforms/web/src/CaptureDigitalId.tsx`. No module
+ * illustration is drawn here — the component owns its own tutorial artwork
+ * (`PrizmaIllustrationDigitalId`).
+ */
+export declare const DigitalIdUploadTutorialScreen: React.ForwardRefExoticComponent<DigitalIdUploadTutorialScreenProps & React.RefAttributes<HTMLDivElement>>;
+export default DigitalIdUploadTutorialScreen;

package/dist/DigitalIdUploadTutorialScreen.js

@@ -0,0 +1,23 @@
+'use client';
+import { jsx as _jsx } from "react/jsx-runtime";
+import { forwardRef } from 'react';
+import { PrizmaCaptureDigitalId } from '@incodetech/prizma-core-web/capture-digital-id';
+import { PrizmaTutorialScreen } from './TutorialScreen';
+import './ScreenLayout.css';
+/**
+ * Digital ID Upload — tutorial, built on the `PrizmaTutorialScreen` archetype
+ * (GUIDELINES.md §6-A). Figma: `Upload Digital ID` file
+ * (wxFsHRvllern4VnjRqM4JO), "Web Happy Path - Light Mode" section, `Tutorial
+ * Screen` (node 25351:14722).
+ *
+ * The illustration slot is Core's own `PrizmaCaptureDigitalId` in its
+ * `tutorial` state — the Figma file names this exact instance "Capture /
+ * Digital ID" (node 26161:10686, Figma description: "Incode specific
+ * component for Digital ID module experience"), the same managed component
+ * already shipped as `core/platforms/web/src/CaptureDigitalId.tsx`. No module
+ * illustration is drawn here — the component owns its own tutorial artwork
+ * (`PrizmaIllustrationDigitalId`).
+ */
+export const DigitalIdUploadTutorialScreen = forwardRef(({ strings, screenId = 'digital-id-upload-tutorial', overrides, onAction, ...shell }, ref) => (_jsx(PrizmaTutorialScreen, { ref: ref, title: strings.tutorial.title, subtitle: strings.tutorial.subtitle, ctaLabel: strings.tutorial.ctaLabel, illustration: _jsx(PrizmaCaptureDigitalId, { state: "tutorial" }), verifiedLabel: strings.verifiedLabel, navLabel: strings.navLabel, screenId: screenId, overrides: overrides, onAction: onAction, ...shell })));
+DigitalIdUploadTutorialScreen.displayName = 'DigitalIdUploadTutorialScreen';
+export default DigitalIdUploadTutorialScreen;

package/dist/DocumentCaptureIllustration.d.ts

@@ -6,7 +6,7 @@ import './DocumentCaptureLayout.css';
  *
  * WHY IT LIVES IN THE MODULE LAYER: `prizma-core-web` ships
  * `PrizmaIllustrationSelfie`, `…IdTutorial`, `…IdIntro`, `…IdFlip`,
- * `…IdHint`, `…IdFeedback`, `…NfcScan`, `…NfcIssue`, `…Geolocation`,
+ * `…IdHint`, `…IdFeedback`, `…NfcScan`, `…Geolocation`,
  * `…DigitalId` and `…Avatar` — there is NO document / proof-of-address
  * illustration. GUIDELINES.md §10 is the standing asset rule for that gap
  * ("Illustrations…: inline SVG React components (Figma-sourced), tintable via

package/dist/EkybCountryScreen.d.ts

@@ -39,12 +39,12 @@ export interface EkybCountryScreenProps extends Omit<PrizmaFormScreenProps, 'tit
  *    live interaction) — the same mechanism Phone Input's `countryCode` and
  *    CURP's `Gene.dropdown` sections use. The search bar Figma draws inside the
  *    menu is Core's own `searchable`.
- * 3. Menu rows and the closed field read the same "🇺🇸 United States": flag
- *    and country name, no dial code. Figma 5707:54174 draws the rows with
- *    Phone Input's "+1" prefixes, dropped by the owner (Elena, 2026-09-28)
- *    because a country of registration has no phone prefix. The flag travels
- *    inside the label text because Core still ships no country-flag primitive
- *    (#PI-3).
+ * 3. Menu rows and the closed field read the same flag + "United States",
+ *    no dial code. Figma 5707:54174 draws the rows with Phone Input's "+1"
+ *    prefixes, dropped by the owner (Elena, 2026-09-28) because a country of
+ *    registration has no phone prefix. The flag is Core's raster in the
+ *    dropdown's leading slot, not an emoji in the label (Elena, 2026-10-23;
+ *    #PI-3, the WatchlistBusinessFormScreen precedent).
  *
  * This page is the only eKYB form page with NO "Back" secondary and NO Stepper —
  * it is step 0, before the three-step wizard starts.

package/dist/EkybCountryScreen.js

@@ -2,6 +2,7 @@
 import { jsx as _jsx } from "react/jsx-runtime";
 import { forwardRef } from 'react';
 import { PrizmaDropdown } from '@incodetech/prizma-core-web/dropdown';
+import { PrizmaCountryFlag } from '@incodetech/prizma-core-web/combined';
 import { PrizmaFormScreen } from './FormScreen';
 import './ScreenLayout.css';
 /**
@@ -26,12 +27,12 @@ import './ScreenLayout.css';
  *    live interaction) — the same mechanism Phone Input's `countryCode` and
  *    CURP's `Gene.dropdown` sections use. The search bar Figma draws inside the
  *    menu is Core's own `searchable`.
- * 3. Menu rows and the closed field read the same "🇺🇸 United States": flag
- *    and country name, no dial code. Figma 5707:54174 draws the rows with
- *    Phone Input's "+1" prefixes, dropped by the owner (Elena, 2026-09-28)
- *    because a country of registration has no phone prefix. The flag travels
- *    inside the label text because Core still ships no country-flag primitive
- *    (#PI-3).
+ * 3. Menu rows and the closed field read the same flag + "United States",
+ *    no dial code. Figma 5707:54174 draws the rows with Phone Input's "+1"
+ *    prefixes, dropped by the owner (Elena, 2026-09-28) because a country of
+ *    registration has no phone prefix. The flag is Core's raster in the
+ *    dropdown's leading slot, not an emoji in the label (Elena, 2026-10-23;
+ *    #PI-3, the WatchlistBusinessFormScreen precedent).
  *
  * This page is the only eKYB form page with NO "Back" secondary and NO Stepper —
  * it is step 0, before the three-step wizard starts.
@@ -70,7 +71,19 @@ export const EkybCountryScreen = forwardRef(({ strings, state = 'empty', countri
                (DEVIATIONS #PI-6). */
             defaultValue: selected, searchable: true, searchPlaceholder: copy.searchPlaceholder, clearSearchLabel: copy.clearSearchLabel, 
             /* The `dropdown` section IS the open-menu spec state. */
-            forceOpen: state === 'dropdown' }) }));
+            forceOpen: state === 'dropdown', 
+            /* Core's canonical flag raster in the closed field and every menu
+               row (see note 3). A country outside the bank falls back to its
+               `flag` emoji. */
+            renderLeading: (option) => {
+                const match = countries.find((c) => c.value === option.value);
+                return match ? (_jsx(PrizmaCountryFlag, { country: {
+                        code: match.value,
+                        name: match.label,
+                        dialCode: '',
+                        flag: match.flag ?? '',
+                    } })) : null;
+            } }) }));
 });
 EkybCountryScreen.displayName = 'EkybCountryScreen';
 export default EkybCountryScreen;

package/dist/EkybStrings.d.ts

@@ -59,8 +59,13 @@ export interface EkybOption {
     label: string;
     /** Compact face for the CLOSED field when it differs from the menu row —
      *  Core's own `PrizmaDropdownOption.fieldLabel`. The eKYB country list
-     *  does not need it: rows and field both read "🇺🇸 United States". */
+     *  does not need it: rows and field both read "United States" after the
+     *  flag. */
     fieldLabel?: string;
+    /** Country menus only: the emoji fallback for a `value` outside Core's
+     *  flag raster bank. The country screen draws the bank's flag by `value`,
+     *  so this never travels inside `label`. */
+    flag?: string;
 }
 /** The values the business-identity page carries. Runtime data, never copy. */
 export interface EkybBusinessValues {

package/dist/ErrorScreensScreen.d.ts

@@ -21,7 +21,7 @@ export interface ErrorScreensScreenProps extends Omit<PrizmaResultScreenProps, '
  * Error screens — the session-level failures, built on the Result archetype
  * (GUIDELINES.md §6-F, `PrizmaResultScreen`).
  *
- * ONE screen for all three generic sections. They draw the identical skeleton —
+ * ONE screen for all four generic sections. They draw the identical skeleton —
  * a centred mark + title + supporting line over a CTA band — and differ only in
  * copy, in which mark leads, and in what the band carries:
  *
@@ -29,8 +29,11 @@ export interface ErrorScreensScreenProps extends Omit<PrizmaResultScreenProps, '
  * - `noConnection`       — Wi-Fi glyph, "Refresh"
  * - `unsupportedBrowser` — canonical negative mark, the session URL above
  *                          "Copy link", with "Continue anyways" under it
+ * - `somethingWentWrong` — canonical negative mark, "Try again" when the copy
+ *                          carries a CTA, "Quit process" under it when it
+ *                          carries a quit label; a dead end when it has neither
  *
- * Chrome is CONSTANT. All three frames are drawn without the logo header and
+ * Chrome is CONSTANT. All the frames are drawn without the logo header and
  * without the verified tag; both are kept here, because the owner rule of
  * 2026-08-18 (#F-30, #F-34) makes the chrome the same on every screen so
  * nothing shifts between states, and every module's connectivity screen must

package/dist/ErrorScreensScreen.js

@@ -9,7 +9,7 @@ import './ScreenLayout.css';
  * Error screens — the session-level failures, built on the Result archetype
  * (GUIDELINES.md §6-F, `PrizmaResultScreen`).
  *
- * ONE screen for all three generic sections. They draw the identical skeleton —
+ * ONE screen for all four generic sections. They draw the identical skeleton —
  * a centred mark + title + supporting line over a CTA band — and differ only in
  * copy, in which mark leads, and in what the band carries:
  *
@@ -17,8 +17,11 @@ import './ScreenLayout.css';
  * - `noConnection`       — Wi-Fi glyph, "Refresh"
  * - `unsupportedBrowser` — canonical negative mark, the session URL above
  *                          "Copy link", with "Continue anyways" under it
+ * - `somethingWentWrong` — canonical negative mark, "Try again" when the copy
+ *                          carries a CTA, "Quit process" under it when it
+ *                          carries a quit label; a dead end when it has neither
  *
- * Chrome is CONSTANT. All three frames are drawn without the logo header and
+ * Chrome is CONSTANT. All the frames are drawn without the logo header and
  * without the verified tag; both are kept here, because the owner rule of
  * 2026-08-18 (#F-30, #F-34) makes the chrome the same on every screen so
  * nothing shifts between states, and every module's connectivity screen must
@@ -49,11 +52,19 @@ import './ScreenLayout.css';
 export const ErrorScreensScreen = forwardRef(({ strings, variant = 'sessionExpired', sessionUrl, copied = false, screenId = `error-screens-${variant}`, overrides, onAction, ...shell }, ref) => {
     const unsupported = variant === 'unsupportedBrowser';
     const noConnection = variant === 'noConnection';
+    const generic = variant === 'somethingWentWrong';
     const copy = unsupported
         ? strings.unsupportedBrowser
         : noConnection
             ? strings.noConnection
-            : strings.sessionExpired;
+            : generic
+                ? strings.somethingWentWrong
+                : strings.sessionExpired;
+    const linkLabel = unsupported
+        ? strings.unsupportedBrowser.continueLabel
+        : generic
+            ? strings.somethingWentWrong.quitLabel
+            : undefined;
     return (_jsx(PrizmaResultScreen, { ref: ref, 
         /* The connectivity screen leads with the Wi-Fi glyph instead of a
            status mark; the other two carry the canonical negative mark. */
@@ -65,7 +76,7 @@ export const ErrorScreensScreen = forwardRef(({ strings, variant = 'sessionExpir
                 .filter(Boolean)
                 .join(' '), children: _jsx(IconWifiOff, { size: "l" }) })) : undefined, progress: unsupported && copied ? (_jsx(PrizmaSnackbar, { state: "success", contentResizing: "fill", children: strings.unsupportedBrowser.copiedLabel })) : undefined, title: copy.title, subtitle: copy.subtitle, disclaimer: unsupported
             ? sessionUrl ?? strings.unsupportedBrowser.urlPlaceholder
-            : undefined, ctaLabel: copy.ctaLabel, linkLabel: unsupported ? strings.unsupportedBrowser.continueLabel : undefined, verifiedLabel: strings.verifiedLabel, navLabel: strings.navLabel, screenId: screenId, overrides: overrides, onAction: onAction, ...shell }));
+            : undefined, ctaLabel: copy.ctaLabel, linkLabel: linkLabel, verifiedLabel: strings.verifiedLabel, navLabel: strings.navLabel, screenId: screenId, overrides: overrides, onAction: onAction, ...shell }));
 });
 ErrorScreensScreen.displayName = 'ErrorScreensScreen';
 export default ErrorScreensScreen;

package/dist/ErrorScreensStrings.d.ts

@@ -1,10 +1,11 @@
 /**
- * The three sections.
+ * The four sections.
  * - `sessionExpired`     — the link is dead; the user must go back to the provider
  * - `noConnection`       — the network went away; retry when it returns
  * - `unsupportedBrowser` — the SDK cannot run here; copy the link and move
+ * - `somethingWentWrong` — the generic failure; try again, or nothing, or quit
  */
-export type ErrorScreensVariant = 'sessionExpired' | 'noConnection' | 'unsupportedBrowser';
+export type ErrorScreensVariant = 'sessionExpired' | 'noConnection' | 'unsupportedBrowser' | 'somethingWentWrong';
 export interface ErrorScreensCopy {
     title: string;
     subtitle?: string;
@@ -28,4 +29,18 @@ export interface ErrorScreensStrings {
         /** Snackbar copy after the link is copied — the frame's second state. */
         copiedLabel: string;
     };
+    /**
+     * The generic failure. Three ways the modules fill it, all the same screen:
+     * `ctaLabel` "Try again" (eKYC, eKYB, Forms, Email Input);
+     * no `ctaLabel`, a dead end (Certificate Issuance, Qualified Signature);
+     * `ctaLabel` plus `quitLabel`, the way out under the retry (Video Selfie).
+     * Phone Input's `unknown` fills it with "Continue" instead, because a retry
+     * may not be possible there (owner, 2026-10-09) — the CTA is the module's
+     * call; the shape and the title are what the family fixes.
+     * The title never carries an ellipsis — a failure is not in progress.
+     */
+    somethingWentWrong: ErrorScreensCopy & {
+        /** Tertiary link under the CTA — "Quit process". Omit for no way out. */
+        quitLabel?: string;
+    };
 }

package/dist/ErrorScreensStrings.js

@@ -6,19 +6,27 @@
 //   214:3357 Geolocation.error.noNetwork      → `noConnection`
 //   240:154  Error screen - Unsupported browser → `unsupportedBrowser`
 //
-// The three failures that belong to the SESSION rather than to any module: the
-// link has expired, the network went away, the browser cannot run the SDK.
-// Every module can hit all three, which is why they are drawn once in the
-// generic file — a user who sees three different "no internet" screens in one
-// journey reads them as three different products.
+// plus the one failure every module draws for itself and the file never did:
+//
+//   —        <module>.error "Something went wrong" → `somethingWentWrong`
+//
+// The failures that belong to the SESSION rather than to any module: the link
+// has expired, the network went away, the browser cannot run the SDK, the
+// server said no for a reason the user cannot act on. Every module can hit all
+// four, which is why they are recorded once in the generic family — a user who
+// sees three different "no internet" screens in one journey reads them as three
+// different products.
 //
 // `noConnection` is deliberately the same screen every module already ships
 // (`FaceCaptureNoConnectionScreen`, `IdCaptureNoConnectionScreen`,
-// `DocumentCaptureNoConnectionScreen`, `GeolocationErrorScreen`'s `noNetwork`).
-// The generic entry is where the shape is DOCUMENTED; the module copies stay
-// put until someone retires them deliberately, because deleting four exported
-// components to save one screen is a breaking change for every host that
-// imports them. Flagged for the owner.
+// `DocumentCaptureNoConnectionScreen`, `GeolocationErrorScreen`'s `noNetwork`,
+// Phone Input's and Video Selfie's `noConnection`). `somethingWentWrong` is the
+// same screen eKYC, eKYB, Forms, Email Input, Phone Input, Certificate
+// Issuance, both signatures and Video Selfie already ship. The generic entry is
+// where the shape and the copy are DOCUMENTED; the module copies stay put until
+// someone retires them deliberately, because deleting exported components to
+// save one screen is a breaking change for every host that imports them.
+// Flagged for the owner (DEVIATIONS #GEN-7, #GEN-18).
 //
 // The family has no flow of its own: each of these is entered from wherever the
 // session broke and exits to a retry or to nothing. Core Lab lists it as a

package/dist/FaceCaptureCapturingScreen.d.ts

@@ -9,6 +9,19 @@ export interface FaceCaptureCapturingScreenProps extends Omit<PrizmaCaptureScree
     state?: FaceCaptureCapturingState;
     /** Live camera feed (<video>) or sample still (<img>) for the ring window. */
     camera?: ReactNode;
+    /**
+     * Raise the "Need more time?" offer over the feed — the accessibility
+     * notification shown 20 s before auto capture falls back to manual.
+     *
+     * It is a MODIFIER of whatever capturing state is already on screen, not a
+     * sixteenth state: the timer runs underneath the guidance, so the user can be
+     * told to move closer and offered more time in the same frame. Needs
+     * `strings.extendTime`; without it the flag is a no-op, which is what a host
+     * that has not localized the copy should get rather than English.
+     */
+    extendTime?: boolean;
+    /** Tapping "Extend auto-capture". The host resets its own fallback timer. */
+    onExtendTime?: () => void;
 }
 /**
  * Face Capture — auto-capture stage (Archetype B, GUIDELINES.md §6-B).
@@ -27,6 +40,56 @@ export interface FaceCaptureCapturingScreenProps extends Omit<PrizmaCaptureScree
  *
  * The archetype adds no offsets of its own — the component owns that spacing
  * (same deviation row).
+ *
+ * ── The "Need more time?" offer (`extendTime`) ──────────────────────────────
+ *
+ * Auto capture gives up after a configured timeout and drops the user into
+ * manual capture. Someone who is struggling — a tremor, low vision, bad light,
+ * an unfamiliar phone — gets moved off the EASIER path precisely because they
+ * were slow, which is backwards. So 20 s before the switch, the screen offers
+ * to stay on auto. A client turns it on per flow from the dashboard; with it
+ * off, nothing about today's capture changes.
+ *
+ * NOT a nicety — it is the conformance route for WCAG 2.2.1 Timing Adjustable
+ * via the *Extend* clause (warn before the limit, ≥20 s to act, ≥10 extensions).
+ * Two things follow that the visuals cannot settle: the notice must be able to
+ * come back ten times, and it must be ANNOUNCED early enough to be acted on.
+ *
+ * ── Live-region politeness: `role="alert"`, not the default ────────────────
+ *
+ * SETTLED 2026-10-05 (Camila). The Snackbar computes `role="status"` (polite)
+ * for every state but error, and this instance overrides it to `alert`.
+ *
+ * A polite region is allowed to wait until the screen reader finishes whatever
+ * it is already saying — and on this screen it always IS saying something: the
+ * capture instruction under the ring changes as the face moves, so the queue
+ * is rarely empty. The offer has a 20 s life. Queued behind two or three
+ * guidance announcements it can be read out after it has already expired,
+ * which turns the one affordance a struggling user needs into an
+ * announcement that the limit has passed.
+ *
+ * That is not a polish issue, it is the conformance failing: WCAG 2.2.1's
+ * Extend clause requires the warning to be given in time to ACT on it. An
+ * announcement the user cannot act on does not satisfy it, however correct the
+ * visuals. `alert` is assertive, so it interrupts the guidance and is heard
+ * while the 20 s is still running.
+ *
+ * The usual objection to `alert` is that interrupting is rude. It applies to
+ * notices that can wait; this one cannot, and it is strictly better to
+ * interrupt "Move closer" than to let the window close in silence. It is also
+ * why the offer must not be re-raised on a timer — each new `alert` interrupts
+ * again. It appears once per countdown, and WCAG allows that up to ten times.
+ *
+ * ⚠ NEW, not yet authored in Core. Two parts of this notice have no Figma
+ * variant behind them and are drawn from the exploration, not from the SoT:
+ *   • the bold title line — the Snackbar has no `title` slot, so it rides
+ *     inside `children` as a <strong>. Core to decide whether to adopt a real
+ *     slot, at which point this moves onto it.
+ *   • the state — it is `neutral` (blue surface, ⓘ glyph), Camila's call
+ *     2026-10-05. `warning` would signal attention more sharply but turns the
+ *     surface amber, and the exploration's open question is whether amber
+ *     reads as "hurry up" to someone who was already struggling. The icon
+ *     cannot be chosen independently: `ICON_BY_STATE` binds it to `state`.
  */
 export declare const FaceCaptureCapturingScreen: React.ForwardRefExoticComponent<FaceCaptureCapturingScreenProps & React.RefAttributes<HTMLDivElement>>;
 export default FaceCaptureCapturingScreen;

package/dist/FaceCaptureCapturingScreen.js

@@ -1,6 +1,7 @@
 'use client';
-import { jsx as _jsx } from "react/jsx-runtime";
+import { jsx as _jsx, jsxs as _jsxs } from "react/jsx-runtime";
 import { forwardRef } from 'react';
+import { PrizmaSnackbar } from '@incodetech/prizma-core-web/snackbar';
 import { PrizmaCaptureScreen } from './CaptureScreen';
 import './FaceCaptureLayout.css';
 /**
@@ -47,7 +48,66 @@ const SELFIE_STATE = {
  *
  * The archetype adds no offsets of its own — the component owns that spacing
  * (same deviation row).
+ *
+ * ── The "Need more time?" offer (`extendTime`) ──────────────────────────────
+ *
+ * Auto capture gives up after a configured timeout and drops the user into
+ * manual capture. Someone who is struggling — a tremor, low vision, bad light,
+ * an unfamiliar phone — gets moved off the EASIER path precisely because they
+ * were slow, which is backwards. So 20 s before the switch, the screen offers
+ * to stay on auto. A client turns it on per flow from the dashboard; with it
+ * off, nothing about today's capture changes.
+ *
+ * NOT a nicety — it is the conformance route for WCAG 2.2.1 Timing Adjustable
+ * via the *Extend* clause (warn before the limit, ≥20 s to act, ≥10 extensions).
+ * Two things follow that the visuals cannot settle: the notice must be able to
+ * come back ten times, and it must be ANNOUNCED early enough to be acted on.
+ *
+ * ── Live-region politeness: `role="alert"`, not the default ────────────────
+ *
+ * SETTLED 2026-10-05 (Camila). The Snackbar computes `role="status"` (polite)
+ * for every state but error, and this instance overrides it to `alert`.
+ *
+ * A polite region is allowed to wait until the screen reader finishes whatever
+ * it is already saying — and on this screen it always IS saying something: the
+ * capture instruction under the ring changes as the face moves, so the queue
+ * is rarely empty. The offer has a 20 s life. Queued behind two or three
+ * guidance announcements it can be read out after it has already expired,
+ * which turns the one affordance a struggling user needs into an
+ * announcement that the limit has passed.
+ *
+ * That is not a polish issue, it is the conformance failing: WCAG 2.2.1's
+ * Extend clause requires the warning to be given in time to ACT on it. An
+ * announcement the user cannot act on does not satisfy it, however correct the
+ * visuals. `alert` is assertive, so it interrupts the guidance and is heard
+ * while the 20 s is still running.
+ *
+ * The usual objection to `alert` is that interrupting is rude. It applies to
+ * notices that can wait; this one cannot, and it is strictly better to
+ * interrupt "Move closer" than to let the window close in silence. It is also
+ * why the offer must not be re-raised on a timer — each new `alert` interrupts
+ * again. It appears once per countdown, and WCAG allows that up to ten times.
+ *
+ * ⚠ NEW, not yet authored in Core. Two parts of this notice have no Figma
+ * variant behind them and are drawn from the exploration, not from the SoT:
+ *   • the bold title line — the Snackbar has no `title` slot, so it rides
+ *     inside `children` as a <strong>. Core to decide whether to adopt a real
+ *     slot, at which point this moves onto it.
+ *   • the state — it is `neutral` (blue surface, ⓘ glyph), Camila's call
+ *     2026-10-05. `warning` would signal attention more sharply but turns the
+ *     surface amber, and the exploration's open question is whether amber
+ *     reads as "hurry up" to someone who was already struggling. The icon
+ *     cannot be chosen independently: `ICON_BY_STATE` binds it to `state`.
  */
-export const FaceCaptureCapturingScreen = forwardRef(({ strings, state = 'initiating', camera, screenId = 'face-capture-capturing', className, ...rest }, ref) => (_jsx(PrizmaCaptureScreen, { ref: ref, className: className, state: SELFIE_STATE[state], camera: camera, feedbackText: strings.capturing[state], verifiedLabel: strings.verifiedLabel, navLabel: strings.navLabel, screenId: screenId, ...rest })));
+export const FaceCaptureCapturingScreen = forwardRef(({ strings, state = 'initiating', camera, extendTime, onExtendTime, screenId = 'face-capture-capturing', className, ...rest }, ref) => {
+    const offer = strings.extendTime;
+    // No copy, no notice: a host that has not localized this must not get
+    // English, and the flag alone is not permission to invent it.
+    const notice = extendTime && offer ? (_jsxs(PrizmaSnackbar, { state: "neutral", isMultiline: true, 
+        // Assertive on purpose — see the live-region note in this file's
+        // header. The component default here would be `status`.
+        role: "alert", linkLabel: offer.linkLabel, onLinkClick: onExtendTime, children: [_jsx("strong", { children: offer.title }), _jsx("br", {}), offer.description] })) : undefined;
+    return (_jsx(PrizmaCaptureScreen, { ref: ref, className: className, state: SELFIE_STATE[state], camera: camera, feedbackText: strings.capturing[state], notice: notice, verifiedLabel: strings.verifiedLabel, navLabel: strings.navLabel, screenId: screenId, ...rest }));
+});
 FaceCaptureCapturingScreen.displayName = 'FaceCaptureCapturingScreen';
 export default FaceCaptureCapturingScreen;