@incodetech/prizma-core-screens 0.2.7 → 0.2.12

package/dist/PermissionsBrowserStepsScreen.d.ts

@@ -18,15 +18,22 @@ export interface PermissionsBrowserStepsScreenProps extends Omit<PrizmaListScree
  *
  * Figma: `1-4-2-id` of the `Permissions` section, plus the four
  * `Android browsers` frames of the Web full-flow board (4:8159 — Chrome,
- * Firefox, Samsung Internet, Opera). ONE screen for all five: they draw the
+ * Firefox, Samsung Internet, Opera). The browser set and every step path are
+ * Geolocation's (`GeolocationBrowserStepsScreen`), nine browsers, with the
+ * camera in place of the location. ONE screen for all of them: they draw the
  * identical skeleton — title block → a step list filling the middle → the
  * refresh CTA — and differ only in the rows, because re-enabling the camera is
- * a different journey in each browser. Five files would have been five chances
+ * a different journey in each browser. Nine files would have been nine chances
  * to drift.
  *
  * The rows are Core's `PrizmaCardListCommonIssues` verbatim; only the leading
  * glyph is chosen here, from the canonical bank (see `STEP_ICONS`).
  *
+ * No subtitle: none of the frames draws the browser name under the title,
+ * and the same call was made for Geolocation's step lists (owner call, Elena
+ * 2026-09-30). `label` stays in the strings as the section's identifier for
+ * hosts and catalogs; the screen itself shows title + steps.
+ *
  * The title block is LEFT-aligned for this whole family. Every frame starts the
  * two-line headline flush at the gutter over left-led step rows; a centred
  * headline above a left-aligned list reads as a mistake. The screen therefore

package/dist/PermissionsBrowserStepsScreen.js

@@ -15,6 +15,7 @@ import './ScreenLayout.css';
  * both forbidden (rule 1, GUIDELINES §10), so each row takes the nearest
  * canonical glyph:
  *
+ *   addressBar  → IconTextAi          the address bar's page / site control
  *   settings    → IconLock            site settings sit behind the address-bar lock
  *   browser     → IconTextAi          Safari's "AA" is the address-bar text control
  *   menu        → IconNumberedList    the ⋮ overflow opens a menu list
@@ -31,6 +32,7 @@ import './ScreenLayout.css';
  * glyphs or bless the substitutions — one decision covers both families.
  */
 const STEP_ICONS = {
+    addressBar: _jsx(IconTextAi, { size: "m" }),
     settings: _jsx(IconLock, { size: "m" }),
     browser: _jsx(IconTextAi, { size: "m" }),
     menu: _jsx(IconNumberedList, { size: "m" }),
@@ -47,15 +49,22 @@ const STEP_ICONS = {
  *
  * Figma: `1-4-2-id` of the `Permissions` section, plus the four
  * `Android browsers` frames of the Web full-flow board (4:8159 — Chrome,
- * Firefox, Samsung Internet, Opera). ONE screen for all five: they draw the
+ * Firefox, Samsung Internet, Opera). The browser set and every step path are
+ * Geolocation's (`GeolocationBrowserStepsScreen`), nine browsers, with the
+ * camera in place of the location. ONE screen for all of them: they draw the
  * identical skeleton — title block → a step list filling the middle → the
  * refresh CTA — and differ only in the rows, because re-enabling the camera is
- * a different journey in each browser. Five files would have been five chances
+ * a different journey in each browser. Nine files would have been nine chances
  * to drift.
  *
  * The rows are Core's `PrizmaCardListCommonIssues` verbatim; only the leading
  * glyph is chosen here, from the canonical bank (see `STEP_ICONS`).
  *
+ * No subtitle: none of the frames draws the browser name under the title,
+ * and the same call was made for Geolocation's step lists (owner call, Elena
+ * 2026-09-30). `label` stays in the strings as the section's identifier for
+ * hosts and catalogs; the screen itself shows title + steps.
+ *
  * The title block is LEFT-aligned for this whole family. Every frame starts the
  * two-line headline flush at the gutter over left-led step rows; a centred
  * headline above a left-aligned list reads as a mistake. The screen therefore
@@ -76,7 +85,7 @@ export const PermissionsBrowserStepsScreen = forwardRef(({ strings, browser = 's
         ...overrides,
         align: overrides?.align ?? 'left',
     };
-    return (_jsx(PrizmaListScreen, { ref: ref, showHeader: showHeader, title: strings.browserSteps.title, subtitle: slice?.label, ctaLabel: strings.browserSteps.ctaLabel, verifiedLabel: strings.verifiedLabel, navLabel: strings.navLabel, screenId: screenId, overrides: alignedOverrides, onAction: onAction, ...shell, children: _jsx(PrizmaCardListCommonIssues, { items: (slice?.steps ?? []).map((step) => ({
+    return (_jsx(PrizmaListScreen, { ref: ref, showHeader: showHeader, title: strings.browserSteps.title, ctaLabel: strings.browserSteps.ctaLabel, verifiedLabel: strings.verifiedLabel, navLabel: strings.navLabel, screenId: screenId, overrides: alignedOverrides, onAction: onAction, ...shell, children: _jsx(PrizmaCardListCommonIssues, { items: (slice?.steps ?? []).map((step) => ({
                 icon: STEP_ICONS[step.kind],
                 title: step.label,
                 showSubtitle: false,

package/dist/PermissionsLayout.css

@@ -0,0 +1,47 @@
+/* Permissions — the pre-permission sheet (`PermissionsAskScreen`).
+ *
+ * Same idiom as Document Capture's method sheet (DEVIATIONS #DC-30): Core's
+ * `PrizmaBottomSheetContent` owns the panel (handle, radius, padding, title,
+ * button group); the screen owns the scrim, because the safe presenter portals
+ * to `document.body` and would escape the 390 × 844 frame. The scrim drinks
+ * Core's own `Surface/Overlay` token. No animation: a screen is one static
+ * spec state. */
+.permissions-sheet-scrim {
+  position: absolute;
+  inset: 0;
+  z-index: 1;
+  background: var(--prizma-surface-overlay);
+}
+
+.permissions-sheet-panel {
+  position: absolute;
+  left: 0;
+  right: 0;
+  bottom: 0;
+  z-index: 2;
+}
+
+/* The frame's `System UI Bottom Bar` (34) sits INSIDE the sheet. Core reserves
+ * it as `env(safe-area-inset-bottom, var(--prizma-sheet-size-safe-area))`, but
+ * a browser defines the inset as 0 on a flat screen, so the fallback never
+ * applies and the CTAs drop to 12px off the frame's bottom. Screens in this
+ * package reserve device chrome as fixed values (`--pcs-status-bar`), so the
+ * sheet takes Core's own Sheet/Size/Safe-area token directly here. */
+.permissions-sheet-panel .prizma-bottom-sheet__safe-area {
+  height: var(--prizma-sheet-size-safe-area);
+}
+
+/* Desktop: the same ask as Core's centred Modal (`presentation="dialog"`).
+ * Same split as NFC's settings dialog: Core's `PrizmaModalContent` is the card
+ * (width 100% up to its own Modal/Size/Max-width), this only centres it with
+ * the Spacing/12 gutter. */
+.permissions-dialog-panel {
+  position: absolute;
+  inset: 0;
+  z-index: 2;
+  display: flex;
+  align-items: center;
+  justify-content: center;
+  padding-inline: var(--prizma-spacing-12);
+  box-sizing: border-box;
+}

package/dist/PermissionsStrings.d.ts

@@ -11,13 +11,14 @@ export interface PermissionsReasonRow {
     description?: string;
 }
 /**
- * Which browser's "turn it back on" journey to show. `safariIos` is the base
- * `1-4-2-id` frame; the other four are the `Android browsers` section of the
- * Web flow (4:8159). Re-enabling a permission is a different journey in every
- * browser, which is why one screen carries five step lists rather than five
- * screens carrying one skeleton.
+ * Which browser's "turn it back on" journey to show. The SAME nine browsers,
+ * keys and order as Geolocation's (`GeolocationBrowser`), because a refused
+ * camera and a refused location are the same journey through the same browser
+ * settings; only the permission's name changes (Camila, 2026-10-07). The
+ * Permissions Figma draws five of them (`1-4-2-id` for Safari plus the four
+ * `Android browsers` frames, 4:8159); the other four follow Geolocation.
  */
-export type PermissionsBrowser = 'safariIos' | 'chromeAndroid' | 'firefoxAndroid' | 'samsungAndroid' | 'operaAndroid';
+export type PermissionsBrowser = 'safariIos' | 'chromeIos' | 'firefoxIos' | 'operaIos' | 'chromeAndroid' | 'firefoxAndroid' | 'operaAndroid' | 'samsungAndroid' | 'unrecognizedAndroid' | 'chromeDesktop' | 'edgeDesktop' | 'firefoxDesktop' | 'safariMac';
 /**
  * Step kind → canonical bank glyph, resolved in
  * `PermissionsBrowserStepsScreen`. Figma leads every row with OS/browser chrome
@@ -28,14 +29,14 @@ export type PermissionsBrowser = 'safariIos' | 'chromeAndroid' | 'firefoxAndroid
  * escalated (`GeolocationBrowserStepsScreen`); this family reuses it rather
  * than inventing a second one.
  */
-export type PermissionsStepKind = 'settings' | 'browser' | 'menu' | 'permissions' | 'camera' | 'toggle' | 'device' | 'apps' | 'return';
+export type PermissionsStepKind = 'addressBar' | 'settings' | 'browser' | 'menu' | 'permissions' | 'camera' | 'toggle' | 'device' | 'apps' | 'return';
 export interface PermissionsStep {
     kind: PermissionsStepKind;
     label: string;
 }
 export interface PermissionsBrowserSteps {
     /** Names the browser under the headline. Figma labels the section, not the
-     *  screen; the label keeps five otherwise near-identical cards apart. */
+     *  screen; the label keeps nine otherwise near-identical cards apart. */
     label: string;
     steps: PermissionsStep[];
 }
@@ -44,6 +45,16 @@ export interface PermissionsStrings {
     navLabel?: string;
     /** "verified by" attribution copy for the footer tag. */
     verifiedLabel: string;
+    /** `1-3-1-id-permission-modal` — the pre-permission sheet, the very first
+     *  ask. Its "Allow" is what raises the real OS prompt. */
+    ask: {
+        title: string;
+        subtitle?: string;
+        /** Primary — raises the OS prompt. */
+        allowLabel: string;
+        /** Secondary — declines; the flow moves on to `required`. */
+        denyLabel: string;
+    };
     /** `1-3-2-id` — the permission was refused and the flow explains why it needs it. */
     required: {
         title: string;
@@ -54,7 +65,7 @@ export interface PermissionsStrings {
         quitLabel: string;
         ctaLabel: string;
     };
-    /** `1-3-2-id-allow-camera` — the first ask, before any refusal. */
+    /** `1-3-2-id-allow-camera` — the softer ask after the REAL OS prompt was refused. */
     allow: {
         title: string;
         subtitle?: string;

package/dist/PermissionsStrings.js

@@ -12,20 +12,26 @@
 // is the ID Capture-flavoured copy of the same skeleton; it stays where it is so
 // nothing that imports it breaks (DEVIATIONS #IDC-26).
 //
-// The section's seven frames collapse onto THREE built screens:
+// The section's seven frames collapse onto FOUR built screens:
 //
+//   1-3-1-id-permission-modal         → PermissionsAskScreen       (the sheet)
 //   1-3-2-id                          → PermissionsRequiredScreen  (reason rows)
 //   1-3-2-id-allow-camera             → PermissionsAllowScreen     (subtitle)
 //   1-4-2-id (+ 4 Android siblings)   → PermissionsBrowserStepsScreen
 //
-// The other four are OS chrome and are NOT built:
+// The other three are OS chrome and are NOT built:
 //
-//   1-3-1-id-permission-modal   the browser's own "Allow camera access" sheet
 //   1-4-1-id                    the iOS "…Would Like to Access the Camera" alert
 //   1-3-2-id-quit-process       an iOS confirm alert layered over 1-3-2-id
 //   1-3-2-id-allow-camera-quit  the same alert layered over the allow screen
 //
-// None of them is a Prizma surface: their chrome does not exist in Core and
+// `1-3-1-id-permission-modal` was on this list until 2026-10-07. It is not the
+// browser's prompt: it is the SDK's own camera pre-permission sheet (the SDK
+// release notes call it "the camera permission sheet", shown by every module
+// that asks for the camera), drawn with Core's Bottom Sheet dialog and Button
+// Group. So it is built, from those two components (DEVIATIONS #GEN-1).
+//
+// None of the remaining three is a Prizma surface: their chrome does not exist in Core and
 // rebuilding it would mean inventing primitives and shipping platform rasters,
 // both forbidden (rule 1, GUIDELINES §10). Same call as Document Capture's iOS
 // action sheets (#DC-20) and Geolocation's system alert. Core Lab draws them as

package/dist/PhoneInputOtpScreen.d.ts

@@ -13,6 +13,14 @@ export interface PhoneInputOtpScreenProps extends Omit<PrizmaFormScreenProps, 't
     value?: string;
     /** How many digits the code carries. Default 6. */
     length?: number;
+    /**
+     * Seconds left before the code can be resent. While it is above 0 (and the
+     * copy carries `otp.resendCountdownLabel`), the resend line becomes one
+     * disabled link, "Resend code in 30s", exactly as Figma draws
+     * `phoneNumber.OTP.typing`. The host owns the timer; the screen only draws
+     * the number it is given.
+     */
+    resendIn?: number;
     screenId?: string;
     overrides?: PrizmaScreenOverrides;
     onAction?: PrizmaScreenActionHandler;

package/dist/PhoneInputOtpScreen.js

@@ -21,24 +21,31 @@ import './PhoneInputLayout.css';
  * wins; `PrizmaOtp.loading` stays correct for hosts that want the in-field
  * spinner. DEVIATIONS #PI-5.
  */
-export const PhoneInputOtpScreen = forwardRef(({ strings, state = 'typing', value, length = 6, screenId = `phone-input-otp-${state}`, overrides, onAction, ...shell }, ref) => (_jsx(PrizmaFormScreen, { ref: ref, title: strings.otp.title, subtitle: strings.otp.subtitle, ctaLabel: strings.otp.ctaLabel, 
-    /* Figma greys the CTA until the code is complete. */
-    ctaDisabled: state === 'typing', 
-    /* The spinner rides the CTA, not the field (see the note above). */
-    ctaLoading: state === 'processing', ctaLoadingLabel: strings.otp.ctaLoadingLabel, 
-    /* "Didn't receive the code? Resend code or Change phone number" — drawn
-       under the CTA on every OTP section. ONE sentence, TWO independently
-       actionable links, so it uses the archetype's composed-line slot rather
-       than `linkLabel` (a full-width 56px button cannot sit inside a line of
-       body text, and one button could not tell the two actions apart —
-       DEVIATIONS #PI-10). */
-    linkContent: strings.otp.resendPrompt ? (_jsxs("p", { className: "prizma-screen-layout__inline-prompt", children: [strings.otp.resendPrompt, ' ', strings.otp.resendLabel ? (_jsx("button", { type: "button", className: "prizma-screen-layout__inline-link", onClick: () => onAction?.({ type: 'secondary', screenId }), children: strings.otp.resendLabel })) : null, strings.otp.changeNumberLabel ? (_jsxs(_Fragment, { children: [' ', strings.otp.resendSeparator, ' ', _jsx("button", { type: "button", className: "prizma-screen-layout__inline-link", onClick: () => onAction?.({ type: 'tertiary', screenId }), children: strings.otp.changeNumberLabel })] })) : null] })) : undefined, verifiedLabel: strings.verifiedLabel, navLabel: strings.navLabel, screenId: screenId, overrides: overrides, onAction: onAction, ...shell, children: _jsx(PrizmaOtp, { length: length, 
-        /* Uncontrolled, for the same reason as the phone field: `readOnly`
-           would paint Core's DISABLED surface on the resting states, which is
-           grey Figma does not draw there (DEVIATIONS #PI-6). */
-        defaultValue: value ?? '', 
-        /* `processing` is the one section Figma greys — the code stays legible
-           while the check runs. */
-        disabled: state === 'processing', error: state === 'error', errorText: state === 'error' ? strings.otp.errorText : undefined }) })));
+export const PhoneInputOtpScreen = forwardRef(({ strings, state = 'typing', value, length = 6, resendIn, screenId = `phone-input-otp-${state}`, overrides, onAction, ...shell }, ref) => {
+    const counting = (resendIn ?? 0) > 0 && Boolean(strings.otp.resendCountdownLabel);
+    return (_jsx(PrizmaFormScreen, { ref: ref, title: strings.otp.title, subtitle: strings.otp.subtitle, ctaLabel: strings.otp.ctaLabel, 
+        /* Figma greys the CTA until the code is complete. */
+        ctaDisabled: state === 'typing', 
+        /* The spinner rides the CTA, not the field (see the note above). */
+        ctaLoading: state === 'processing', ctaLoadingLabel: strings.otp.ctaLoadingLabel, 
+        /* "Didn't receive the code? Resend code or Change phone number" — drawn
+           under the CTA on every OTP section. ONE sentence, TWO independently
+           actionable links, so it uses the archetype's composed-line slot rather
+           than `linkLabel` (a full-width 56px button cannot sit inside a line of
+           body text, and one button could not tell the two actions apart —
+           DEVIATIONS #PI-10). */
+        /* While the resend timer runs, the line is ONE disabled link (Figma
+           `OTP.typing`: Tertiary / Link · Disabled), not the composed sentence. */
+        linkLabel: counting
+            ? strings.otp.resendCountdownLabel.replace('{{time}}', String(resendIn))
+            : undefined, linkDisabled: counting, linkContent: !counting && strings.otp.resendPrompt ? (_jsxs("p", { className: "prizma-screen-layout__inline-prompt", children: [strings.otp.resendPrompt, ' ', strings.otp.resendLabel ? (_jsx("button", { type: "button", className: "prizma-screen-layout__inline-link", onClick: () => onAction?.({ type: 'secondary', screenId }), children: strings.otp.resendLabel })) : null, strings.otp.changeNumberLabel ? (_jsxs(_Fragment, { children: [' ', strings.otp.resendSeparator, ' ', _jsx("button", { type: "button", className: "prizma-screen-layout__inline-link", onClick: () => onAction?.({ type: 'tertiary', screenId }), children: strings.otp.changeNumberLabel })] })) : null] })) : undefined, verifiedLabel: strings.verifiedLabel, navLabel: strings.navLabel, screenId: screenId, overrides: overrides, onAction: onAction, ...shell, children: _jsx(PrizmaOtp, { length: length, 
+            /* Uncontrolled, for the same reason as the phone field: `readOnly`
+               would paint Core's DISABLED surface on the resting states, which is
+               grey Figma does not draw there (DEVIATIONS #PI-6). */
+            defaultValue: value ?? '', 
+            /* `processing` is the one section Figma greys — the code stays legible
+               while the check runs. */
+            disabled: state === 'processing', error: state === 'error', errorText: state === 'error' ? strings.otp.errorText : undefined }) }));
+});
 PhoneInputOtpScreen.displayName = 'PhoneInputOtpScreen';
 export default PhoneInputOtpScreen;

package/dist/PhoneInputStrings.d.ts

@@ -28,8 +28,9 @@ export type PhoneInputOtpState = 'typing' | 'filled' | 'processing' | 'error';
  */
 export type PhoneInputErrorVariant = 'tryAgain' | 'unknown' | 'noNetwork';
 /** One selectable country in the dial-code dropdown. Runtime data, not copy —
- *  the host supplies its own list; `flag` is the emoji Figma draws (Core has no
- *  country-flag primitive — DEVIATIONS #PI-3). */
+ *  the host supplies its own list. The screen draws the flag from Core's
+ *  raster bank by `value` (`PrizmaCountryFlag`, DEVIATIONS #PI-3); `flag` is
+ *  only the emoji fallback for a country outside the bank. */
 export interface PhoneInputCountry {
     /** Stable value, e.g. an ISO 3166-1 alpha-2 code. */
     value: string;
@@ -37,7 +38,7 @@ export interface PhoneInputCountry {
     dialCode: string;
     /** Country name for the open menu row. */
     label: string;
-    /** Emoji flag, e.g. `🇷🇸`. */
+    /** Emoji fallback, e.g. `🇷🇸`, drawn only when the bank has no raster. */
     flag?: string;
 }
 export interface PhoneInputStrings {
@@ -102,6 +103,13 @@ export interface PhoneInputStrings {
         resendSeparator?: string;
         /** Second link — returns to phone entry. Emits `tertiary`. */
         changeNumberLabel?: string;
+        /**
+         * While the resend timer runs, the resend line is replaced by ONE disabled
+         * link: "Resend code in {{time}}s" (Figma `phoneNumber.OTP.typing`). The
+         * `{{time}}` placeholder is the SDK's own (`otp.resendCountdown`) and is
+         * filled with the screen's `resendIn` seconds.
+         */
+        resendCountdownLabel?: string;
         /** Primary CTA. */
         ctaLabel: string;
         /** Accessible / visible busy copy while the code is checked (`processing`). */

package/dist/PhoneInputVerifyScreen.js

@@ -3,6 +3,7 @@ import { jsx as _jsx, jsxs as _jsxs } from "react/jsx-runtime";
 import { forwardRef } from 'react';
 import { PrizmaTextField } from '@incodetech/prizma-core-web/text-field';
 import { PrizmaDropdown } from '@incodetech/prizma-core-web/dropdown';
+import { PrizmaCountryFlag } from '@incodetech/prizma-core-web/combined';
 import { PrizmaFormScreen } from './FormScreen';
 import './ScreenLayout.css';
 import './PhoneInputLayout.css';
@@ -43,10 +44,13 @@ export const PhoneInputVerifyScreen = forwardRef(({ strings, state = 'default',
     const options = countries.map((c) => ({
         value: c.value,
         // The open menu row reads flag + dial code + country name
-        // ("🇷🇸 +381 Serbia"); the closed field keeps only flag + dial code
-        // ("🇷🇸 +381") through Core's `fieldLabel`, exactly as Figma draws it.
-        label: [c.flag, c.dialCode, c.label].filter(Boolean).join(' '),
-        fieldLabel: [c.flag, c.dialCode].filter(Boolean).join(' '),
+        // ("+381 Serbia" after the flag); the closed field keeps only flag +
+        // dial code ("+381") through Core's `fieldLabel`, as Figma draws it.
+        // The flag is not text: it rides the leading slot below (DEVIATIONS
+        // #PI-3), so it is Core's raster on every OS instead of an emoji that
+        // Windows draws as the letters "RS".
+        label: [c.dialCode, c.label].join(' '),
+        fieldLabel: c.dialCode,
     }));
     // Figma treats the states as three distinct field treatments, not one:
     // `loading` greys BOTH fields (the request is in flight and the form is
@@ -64,7 +68,19 @@ export const PhoneInputVerifyScreen = forwardRef(({ strings, state = 'default',
         /* Figma's `loading` section swaps the CTA label for Core's spinner. */
         ctaLoading: busy, ctaDisabled: emptyError, ctaLoadingLabel: strings.verify.ctaLoadingLabel, verifiedLabel: strings.verifiedLabel, navLabel: strings.navLabel, screenId: screenId, overrides: overrides, onAction: onAction, ...shell, children: _jsxs("div", { className: "phone-input-combined", children: [_jsx(PrizmaDropdown, { className: "phone-input-combined__country", "aria-label": strings.verify.countryLabel, options: options, value: selected, searchable: true, searchPlaceholder: strings.verify.countrySearchPlaceholder, 
                     /* The `countryCode` section IS the open-menu spec state. */
-                    forceOpen: state === 'countryCode', disabled: busy }), _jsx(PrizmaTextField, { className: [
+                    forceOpen: state === 'countryCode', 
+                    /* Core's canonical flag raster in the closed field and every menu
+                       row, the WatchlistBusinessFormScreen precedent. 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: match.dialCode,
+                                flag: match.flag ?? '',
+                            } })) : null;
+                    }, disabled: busy }), _jsx(PrizmaTextField, { className: [
                         'phone-input-combined__number',
                         /* Core's own static-focus modifier — the same mechanism the
                            Dropdown exposes as `forceState`, which `PrizmaTextField` has

package/dist/QualifiedSignatureDocumentScreen.d.ts

@@ -35,16 +35,19 @@ export interface QualifiedSignatureDocumentScreenProps extends Omit<PrizmaListSc
  *
  * Archetype G is the fit: its `__list` middle is "content filling the space
  * between the title block and the CTA band", which is exactly what a document
- * page is, and both sections carry no CTA at all so the band never renders. The
+ * page is, and the band carries only the "Back" secondary (delta 1). The
  * body is allowed to scroll inside that middle — one module rule RELEASING an
  * overflow constraint, declaring no spacing or size, the same idiom as CURP's
  * taller-than-844 form (DEVIATIONS #CURP-1).
  *
  * THREE deltas from the frames:
- * 1. Both sections draw a back chevron at the nav's left. It is BUILT (owner
- *    call 2026-09-29): these are viewers the user opened from the accept
- *    screen, so they need a way back. It is Core's chevron through the opt-in
- *    `PrizmaScreenNav.backLabel`, emitting `back`; the logo stays centred.
+ * 1. Both sections draw a back chevron at the nav's left. These are viewers
+ *    the user opened from the accept screen, so they need a way back (owner
+ *    call 2026-09-29). It ships as a full-width SECONDARY "Back" button in the
+ *    CTA band instead, emitting `secondary` (owner call 2026-10-08): the person
+ *    reads and returns to sign, and a real button at the thumb is easier to
+ *    find than a chevron. "Back" over "Done" because nothing is finished here;
+ *    the signature still waits on the accept screen. The nav stays logo-only.
  *    `terms` replacing the logo row with a chevron + heading bar is still not
  *    followed — the title stays the archetype's H2 below the nav.
  * 2. `viewdoc` draws NO heading. GUIDELINES §4 is explicit that every screen has

package/dist/QualifiedSignatureDocumentScreen.js

@@ -19,16 +19,19 @@ import './QualifiedSignatureLayout.css';
  *
  * Archetype G is the fit: its `__list` middle is "content filling the space
  * between the title block and the CTA band", which is exactly what a document
- * page is, and both sections carry no CTA at all so the band never renders. The
+ * page is, and the band carries only the "Back" secondary (delta 1). The
  * body is allowed to scroll inside that middle — one module rule RELEASING an
  * overflow constraint, declaring no spacing or size, the same idiom as CURP's
  * taller-than-844 form (DEVIATIONS #CURP-1).
  *
  * THREE deltas from the frames:
- * 1. Both sections draw a back chevron at the nav's left. It is BUILT (owner
- *    call 2026-09-29): these are viewers the user opened from the accept
- *    screen, so they need a way back. It is Core's chevron through the opt-in
- *    `PrizmaScreenNav.backLabel`, emitting `back`; the logo stays centred.
+ * 1. Both sections draw a back chevron at the nav's left. These are viewers
+ *    the user opened from the accept screen, so they need a way back (owner
+ *    call 2026-09-29). It ships as a full-width SECONDARY "Back" button in the
+ *    CTA band instead, emitting `secondary` (owner call 2026-10-08): the person
+ *    reads and returns to sign, and a real button at the thumb is easier to
+ *    find than a chevron. "Back" over "Done" because nothing is finished here;
+ *    the signature still waits on the accept screen. The nav stays logo-only.
  *    `terms` replacing the logo row with a chevron + heading bar is still not
  *    followed — the title stays the archetype's H2 below the nav.
  * 2. `viewdoc` draws NO heading. GUIDELINES §4 is explicit that every screen has
@@ -48,7 +51,7 @@ import './QualifiedSignatureLayout.css';
  */
 export const QualifiedSignatureDocumentScreen = forwardRef(({ strings, variant = 'document', body, screenId = `qualified-signature-document-${variant}`, overrides, onAction, ...shell }, ref) => {
     const copy = variant === 'terms' ? strings.document.terms : strings.document.document;
-    return (_jsx(PrizmaListScreen, { ref: ref, title: copy.title, verifiedLabel: strings.verifiedLabel, navLabel: strings.navLabel, backLabel: strings.document.backLabel, screenId: screenId, overrides: overrides, onAction: onAction, ...shell, children: _jsx("div", { className: [
+    return (_jsx(PrizmaListScreen, { ref: ref, title: copy.title, verifiedLabel: strings.verifiedLabel, navLabel: strings.navLabel, secondaryCtaLabel: strings.document.backLabel, screenId: screenId, overrides: overrides, onAction: onAction, ...shell, children: _jsx("div", { className: [
                 'qualified-signature-document',
                 'qualified-signature-document--framed',
                 `qualified-signature-document--${variant}`,

package/dist/QualifiedSignatureResultScreen.d.ts

@@ -3,11 +3,16 @@ import { type PrizmaResultScreenProps } from './ResultScreen';
 import type { PrizmaScreenActionHandler, PrizmaScreenOverrides } from './types';
 import type { QualifiedSignatureResultVariant, QualifiedSignatureStrings } from './QualifiedSignatureStrings';
 import './ScreenLayout.css';
-export interface QualifiedSignatureResultScreenProps extends Omit<PrizmaResultScreenProps, 'status' | 'title' | 'subtitle' | 'glyph' | 'bandContent' | 'disclaimer' | 'ctaLabel' | 'secondaryCtaLabel' | 'verifiedLabel' | 'navLabel'> {
+export interface QualifiedSignatureResultScreenProps extends Omit<PrizmaResultScreenProps, 'status' | 'title' | 'subtitle' | 'glyph' | 'bandContent' | 'disclaimer' | 'ctaLabel' | 'secondaryCtaLabel' | 'progress' | 'verifiedLabel' | 'navLabel'> {
     /** Module copy — this screen reads the `result` slice its `variant` names. */
     strings: QualifiedSignatureStrings;
     /** Which verdict section to render. Default `signed`. */
     variant?: QualifiedSignatureResultVariant;
+    /** `signed` · `signedPartner` only — draw the "document downloaded" Snackbar,
+     *  the state after the person pressed the download control. HOST state, like
+     *  Error screens' `copied`: the host sets it on the `secondary` action and
+     *  clears it when its own timer runs out. Default `false`. */
+    downloaded?: boolean;
     screenId?: string;
     overrides?: PrizmaScreenOverrides;
     onAction?: PrizmaScreenActionHandler;
@@ -20,8 +25,10 @@ export interface QualifiedSignatureResultScreenProps extends Omit<PrizmaResultSc
  * nav → centred status mark + title block → CTA band → anchored tag — and differ
  * in status, copy and which actions exist:
  * - `signed`        — `QSign.success` (10196:67485): the positive mark over a
- *   `Button group` 124 tall = the "Continue" primary plus the "Download PDF"
- *   underlined link.
+ *   STACKED pair — "Continue" primary above a "Download PDF" OUTLINED
+ *   secondary. Figma draws the download as an underlined link; it ships as the
+ *   partner's secondary Button instead (owner call 2026-10-08, "make the
+ *   generic one look like Namirial"), so both success endings read alike.
  * - `signedPlain`   — `QSign.success` (10196:67494): the SAME mark and line
  *   with no actions at all, so the band never renders and the screen reads as
  *   the pure §6-C verdict.
@@ -50,16 +57,12 @@ export interface QualifiedSignatureResultScreenProps extends Omit<PrizmaResultSc
  * The owner rule settles the split in favour of keeping it (#PI-8, #F-30) so
  * nothing shifts between states.
  *
- * ONE reported delta: on `signed`, Figma puts "Download PDF" BELOW the primary,
- * at Core's `PrizmaButtonGroup` Spacing/12. Archetype F has no tertiary-link
- * slot — its only band opening above the buttons is `bandContent` — so Core's
- * own `tertiary-link` Button is composed there and lands ABOVE the primary at
- * the band's Spacing/32 (16 + 16). Ink, semantics and the distinct `secondary`
- * action are all correct (#PI-10); only the position moves. #GEO-1 fixes the
- * tertiary link's position PER ARCHETYPE and F has never declared one — the
- * archetype request is logged instead of a local override. `signedPartner` is
- * unaffected: its download control is a real outlined secondary Button, which
- * the archetype already places correctly.
+ * The download confirmation. Pressing "Download PDF" / "Download document"
+ * emits `secondary`; the host then sets `downloaded` and the screen raises a
+ * success Snackbar ("Document downloaded") in the archetype's `progress` slot,
+ * between the nav and the content, the same slot and component Error screens
+ * use for "link copied" (owner call 2026-10-08). Dismissal is the host's: the
+ * Snackbar is presentational (snackbar.md §9 item 6).
  */
 export declare const QualifiedSignatureResultScreen: React.ForwardRefExoticComponent<QualifiedSignatureResultScreenProps & React.RefAttributes<HTMLDivElement>>;
 export default QualifiedSignatureResultScreen;

package/dist/QualifiedSignatureResultScreen.js

@@ -1,7 +1,7 @@
 'use client';
 import { jsx as _jsx } from "react/jsx-runtime";
 import { forwardRef } from 'react';
-import { PrizmaButton } from '@incodetech/prizma-core-web/button';
+import { PrizmaSnackbar } from '@incodetech/prizma-core-web/snackbar';
 import { PrizmaResultScreen } from './ResultScreen';
 import './ScreenLayout.css';
 /**
@@ -12,8 +12,10 @@ import './ScreenLayout.css';
  * nav → centred status mark + title block → CTA band → anchored tag — and differ
  * in status, copy and which actions exist:
  * - `signed`        — `QSign.success` (10196:67485): the positive mark over a
- *   `Button group` 124 tall = the "Continue" primary plus the "Download PDF"
- *   underlined link.
+ *   STACKED pair — "Continue" primary above a "Download PDF" OUTLINED
+ *   secondary. Figma draws the download as an underlined link; it ships as the
+ *   partner's secondary Button instead (owner call 2026-10-08, "make the
+ *   generic one look like Namirial"), so both success endings read alike.
  * - `signedPlain`   — `QSign.success` (10196:67494): the SAME mark and line
  *   with no actions at all, so the band never renders and the screen reads as
  *   the pure §6-C verdict.
@@ -42,18 +44,14 @@ import './ScreenLayout.css';
  * The owner rule settles the split in favour of keeping it (#PI-8, #F-30) so
  * nothing shifts between states.
  *
- * ONE reported delta: on `signed`, Figma puts "Download PDF" BELOW the primary,
- * at Core's `PrizmaButtonGroup` Spacing/12. Archetype F has no tertiary-link
- * slot — its only band opening above the buttons is `bandContent` — so Core's
- * own `tertiary-link` Button is composed there and lands ABOVE the primary at
- * the band's Spacing/32 (16 + 16). Ink, semantics and the distinct `secondary`
- * action are all correct (#PI-10); only the position moves. #GEO-1 fixes the
- * tertiary link's position PER ARCHETYPE and F has never declared one — the
- * archetype request is logged instead of a local override. `signedPartner` is
- * unaffected: its download control is a real outlined secondary Button, which
- * the archetype already places correctly.
+ * The download confirmation. Pressing "Download PDF" / "Download document"
+ * emits `secondary`; the host then sets `downloaded` and the screen raises a
+ * success Snackbar ("Document downloaded") in the archetype's `progress` slot,
+ * between the nav and the content, the same slot and component Error screens
+ * use for "link copied" (owner call 2026-10-08). Dismissal is the host's: the
+ * Snackbar is presentational (snackbar.md §9 item 6).
  */
-export const QualifiedSignatureResultScreen = forwardRef(({ strings, variant = 'signed', screenId = `qualified-signature-result-${variant}`, overrides, onAction, ...shell }, ref) => {
+export const QualifiedSignatureResultScreen = forwardRef(({ strings, variant = 'signed', downloaded = false, screenId = `qualified-signature-result-${variant}`, overrides, onAction, ...shell }, ref) => {
     // One slice per frame — nothing is shared between variants, so the frames
     // can never collapse into each other visually.
     const signedCopy = variant === 'signed' ? strings.result.signed : undefined;
@@ -63,14 +61,15 @@ export const QualifiedSignatureResultScreen = forwardRef(({ strings, variant = '
         partnerCopy ??
         retryCopy ??
         (variant === 'error' ? strings.result.error : strings.result.signedPlain);
-    return (_jsx(PrizmaResultScreen, { ref: ref, status: variant === 'error' || variant === 'errorRetry' ? 'warning' : 'success', title: copy.title, subtitle: copy.subtitle, 
+    return (_jsx(PrizmaResultScreen, { ref: ref, status: variant === 'error' || variant === 'errorRetry' ? 'warning' : 'success', title: copy.title, subtitle: copy.subtitle, progress: downloaded && (signedCopy?.downloadLabel || partnerCopy) ? (_jsx(PrizmaSnackbar, { state: "success", contentResizing: "fill", children: strings.result.downloadedLabel })) : undefined, 
         /* "Continue" · "Done" · "Try again" — the archetype's own primary. */
         ctaLabel: signedCopy?.ctaLabel ?? partnerCopy?.ctaLabel ?? retryCopy?.ctaLabel, 
-        /* The partner's outlined "Download document", below the primary. */
-        secondaryCtaLabel: partnerCopy?.secondaryCtaLabel, 
+        /* The outlined download, below the primary: "Download PDF" on the
+           generic ending, "Download document" on the partner's. */
+        secondaryCtaLabel: signedCopy?.downloadLabel ?? partnerCopy?.secondaryCtaLabel, 
         /* The partner's "Signed by …" row — the band's centred text slot, which
            puts it above the button pair exactly as Figma draws it. */
-        disclaimer: partnerCopy?.signedByLabel, bandContent: signedCopy?.downloadLabel ? (_jsx(PrizmaButton, { variant: "tertiary-link", size: "L", onClick: () => onAction?.({ type: 'secondary', screenId }), children: signedCopy.downloadLabel })) : undefined, verifiedLabel: strings.verifiedLabel, navLabel: strings.navLabel, screenId: screenId, overrides: overrides, onAction: onAction, ...shell }));
+        disclaimer: partnerCopy?.signedByLabel, verifiedLabel: strings.verifiedLabel, navLabel: strings.navLabel, screenId: screenId, overrides: overrides, onAction: onAction, ...shell }));
 });
 QualifiedSignatureResultScreen.displayName = 'QualifiedSignatureResultScreen';
 export default QualifiedSignatureResultScreen;

package/dist/QualifiedSignatureStrings.d.ts

@@ -33,7 +33,8 @@ export type QualifiedSignatureDocumentVariant = 'document' | 'terms';
  * The FIVE verdict frames. Both purple parents draw success twice and error
  * twice, and each pair differs in what the signer can do next:
  * - `signed`        — `QSign.success` (10196:67485): the positive mark with
- *   "Continue" and a "Download PDF" underlined link
+ *   "Continue" primary above a "Download PDF" outlined secondary (was an
+ *   underlined link in Figma; owner call 2026-10-08, matches the partner)
  * - `signedPlain`   — `QSign.success` (10196:67494): the same mark and line
  *   with NO actions at all
  * - `signedPartner` — the `x Namirial` parent's own success frame (6086:40135),
@@ -154,9 +155,11 @@ export interface QualifiedSignatureStrings {
         terms: {
             title: string;
         };
-        /** Accessible name of the nav's back chevron on both document screens
+        /** The way back on both document screens
          *  ("Back") — they are opened from the accept screen, so they carry a way
-         *  back to it. Emits `back`. Omit to render the logo-only nav. */
+         *  back to it. It is the label of a full-width SECONDARY button in the CTA
+         *  band (owner call 2026-10-08, was the nav chevron) and emits
+         *  `secondary`. Omit it and no way back renders. */
         backLabel?: string;
     };
     /** The two in-flight screens. */
@@ -191,7 +194,8 @@ export interface QualifiedSignatureStrings {
             subtitle?: string;
             /** Primary CTA ("Continue"). */
             ctaLabel: string;
-            /** Underlined tertiary link ("Download PDF"). Emits `secondary`. */
+            /** OUTLINED secondary below the primary ("Download PDF"), the same
+             *  control as the partner's "Download document". Emits `secondary`. */
             downloadLabel?: string;
         };
         /** QSign.success drawn with no actions. */
@@ -216,6 +220,9 @@ export interface QualifiedSignatureStrings {
              *  `secondary`. A real Button, not `signed`'s underlined link. */
             secondaryCtaLabel: string;
         };
+        /** The success Snackbar raised after either download control was pressed
+         *  ("Document downloaded"). Shared by `signed` and `signedPartner`. */
+        downloadedLabel: string;
         /** QSign.AcceptSign.error ("Something went wrong"). Figma draws no button. */
         error: {
             title: string;