igrantio-usecase-uilisted

# iGrant.io use-case UI (default look and feel) ## When to use The default chrome for any iGrant.io frontend (`igrantio-issuer-frontend`, `igrantio-verifier-frontend`, or a bespoke use-case UI). Reach for it whenever the user has not specified their own UI or layout. It gives you the iGrant.io navbar, footer, theme, and a small set of primitives so a flow looks on-brand with zero design work. If the user brings their own design system, skip this. Intentionally minimal: a theme, a shell, a few primitives, strings-driven i18n. No component-library sprawl, and no runtime deps beyond what `igrantio-frontend-client` already uses (React peer plus `qrcode`). **Before you build**: run the integrator intake in `igrantio-ows-overview` - environment, API key, tenancy, backend host, webhooks, frontend - one question at a time, a recommended default with each. ## What it provides (`references/`) - **`assets/`** - vendored brand assets: `iGrant_210_55_BW.svg` (the white iGrant.io logo) and `whatsapp.png`. - **`ui/theme.css`** - the single source of truth for every token and use-case style, at exact iGrant.io values: typography (Plus Jakarta Sans body, **Byrd** headings - copy the woff2 files from an iGrant.io deployment's `/assets/fonts/` into `ui/fonts/`, otherwise it falls back to Plus Jakarta Sans), palette, buttons, split layout, stepper cards with the offset-shadow number box, heading scale, content card, step navigation, form fields, QR box, status stages, and the n