blueprintlisted

# blueprint — Full-Product Blueprint (Flow-First) Maintain the **whole product's** desired end state under `docs/blueprint/`. The blueprint is product-wide and permanent — not feature-specific. It is organized by **process**: the primary unit is the **flow** (a user or system journey to an observable outcome), and flows are the goal-traceability spine — product goal → flow → the entities, API operations, screens, and jobs the flow needs. Entities are **supporting data contracts** the flows stand on. The doc units: - **Flow** — `docs/blueprint/flows/<project>/<NNN>-<flow>/`, one uniform depth for UI and non-UI projects alike. The folder holds **`index.md`** — the platform-agnostic contract (purpose, trigger, steps, diagram, jobs, acceptance; **no screens**) — plus **one `<platform>.md` per implemented platform** (`mobile` | `tablet` | `desktop` | `web` | `auto`) carrying only that platform's Screens + Components. A non-UI flow is `index.md` alone. Flows are **grouped by their primary registry project** — the project that owns the journey (the UI project of its Screens; for a UI-less flow, the service/worker whose trigger starts it; ambiguous → ask, never guess). Since format 15 the platform lives in the **filename**, so there is no `device:` key and **one number line per project**. `<NNN>` is **designated** per `${CLAUDE_PLUGIN_ROOT}/assets/standard-flows.md`: `010` splash, `020` signin, `030` recover-account, `040` onboarding, **`100` home** (the an