igrantio-holder-frontendlisted

# iGrant.io holder frontend (wallet portal) ## When to use Build the holder-side portal a customer's users see: the organisation's wallet that receives, holds, and presents credentials. Ships the complete flow logic and reference views so an integrator scaffolds a working portal first and restyles it after. Depends on `igrantio-frontend-client` (vendored at `src/lib/ows/`) and an `igrantio-holder-backend` deployment; the exact endpoint contract is in `igrantio-api-holder` and `igrantio-holder-backend/references/holder-api-reference.md`. Issuer and verifier UIs are separate skills. ## 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.igrant.io`); a switch later is a configuration change._ 2. **API key** - do