ui-architecture-preflightlisted

# Architecture Preflight — UI You are performing an Architecture Preflight for a UI feature. Determine the feature name from the user's request; if it is not provided, ask before proceeding. Read the following before proceeding: Feature specs: - `features/<feature_name>/nfrs.md` - `features/<feature_name>/acceptance.feature` - `features/<feature_name>/eval_criteria.yaml` Architecture standards: - `docs/ui/architecture/MVVM_CONTRACT.md` - `docs/ui/architecture/*/COMPONENT_CONVENTIONS.md` - `docs/ui/architecture/*/STATE_MANAGEMENT.md` - `docs/ui/evaluation/eval_criteria.md` - All accepted ADRs in `docs/ui/architecture/ADR/` --- Produce `features/<feature_name>/architecture_preflight.md` for this feature covering: ## 1. MVVM Layer Impact Which layers does this feature touch? For each: - View (components): what new components are required? - ViewModel (hooks/store): what server state and client state is needed? - Model (API): what backend endpoints are consumed? ## 2. Backend Contract Analysis - Which backend API endpoints does this feature consume? - Are those endpoints already available or do they need to be built first? - If a new contract is required from the backend team, flag it — this blocks UI implementation until the contract is accepted ## 2.5 Repository Scope Analysis Before proceeding to component and state management decisions, validate repository scope. See: `docs/REPO_SCOPE_ANALYSIS_GUIDANCE.md` Verify the "Repository Scope" section in `features/<featu