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`). ## Prerequisites - An **iGrant.io Organisation Wallet Suite (OWS) API key**. Get it from [support@igrant.io](mailto:support@igrant.io). Keep it on the server, in an environment variable or a secret manager. The browser never sees it. - The **OWS environment** the key belongs to. The default is **demo** (`https://demo-api.igrant.io`). Use **staging** (`https://staging-api.igrant.io`) only when the integrator asks for it. A key works only in its own environment. ## Ask the integrator first Ask one question at a time. Wait for the answer. Give the recommended default with each question. Look up facts in the project (framework, environment variables, an existing backend) instead of asking for them. Record the answers before you write code. 1. **Environment** - demo or staging? _Default demo (`https://demo-api.igran