Add priority ordering to enhancement backlog

docs/enhancements.md

@@ -4,50 +4,74 @@
 
 ---
 
+## Priority Order
+
+### P1 — Profile & Identity *(most broken; foundational for subsequent UX work)*
+1. **Profile creation flow** (#211) — must come first; everything else in identity builds on it
+2. **New landing/home page** (#214) — makes profile creation the clear entry point
+3. **User profile page** (#213) — depends on profile creation flow
+
+### P2 — Gameplay & Performance *(high value, independent of identity work)*
+4. **Pre-generated puzzle pool** (#220) — fixes slow/timing-out new game endpoint
+5. **Difficulty-based scoring** (#219) — domain change; game stats page depends on this
+6. **Hint system** (#218) — independent gameplay feature
+7. **Game stats page** (#215) — depends on difficulty-based scoring (#219)
+
+### P3 — Quality & Polish
+8. **End-to-end tests** (#222) — Playwright config already exists; relatively quick to activate
+9. **Convert Sudoku.React to PWA** (#216) — mobile installability
+10. **Mobile-responsive layout audit** (#223) — best done alongside or after PWA
+
+### P4 — Deferred *(complex or low user-facing value short-term)*
+11. **Passwordless profile locking** (#212) — WebAuthn/FIDO2 complexity; defer until profile flow is stable
+12. **Add VNet to infrastructure** (#210) — no user-facing benefit short-term
+
+---
+
 ## Infrastructure & Deployment
 
 - [x] **Deploy Sudoku.React to Static Web App** — Add the React frontend to the existing Azure deployment pipeline, alongside the Blazor app. A spec for this already exists at `docs/specs/setup-deployment-react-static-web-app.md`.
-- [ ] **Add VNet to infrastructure** — Integrate a Virtual Network into the Bicep infrastructure (`infra/main.bicep`) to secure communication between the API, storage, and frontends.
+- [ ] **[P4]** **Add VNet to infrastructure** — Integrate a Virtual Network into the Bicep infrastructure (`infra/main.bicep`) to secure communication between the API, storage, and frontends.
 
 ---
 
 ## User Profiles & Identity
 
-- [ ] **Profile creation flow** — Replace the auto-generated alias with an explicit "create your profile" onboarding step when a user first visits the app. The user picks their own alias/display name.
-- [ ] **Passwordless profile locking** — Secure profiles without traditional passwords. Options to explore: a device-bound passkey (WebAuthn/FIDO2), a one-time magic link sent to email, or a PIN stored in a signed/encrypted browser token. Goal: prevent another user from claiming or hijacking an existing alias.
-- [ ] **User profile page** — A dedicated page where users can view and edit their alias/display name, see their profile info, and manage their identity across sessions.
+- [ ] **[P1]** **Profile creation flow** — Replace the auto-generated alias with an explicit "create your profile" onboarding step when a user first visits the app. The user picks their own alias/display name.
+- [ ] **[P4]** **Passwordless profile locking** — Secure profiles without traditional passwords. Options to explore: a device-bound passkey (WebAuthn/FIDO2), a one-time magic link sent to email, or a PIN stored in a signed/encrypted browser token. Goal: prevent another user from claiming or hijacking an existing alias.
+- [ ] **[P1]** **User profile page** — A dedicated page where users can view and edit their alias/display name, see their profile info, and manage their identity across sessions.
 
 ---
 
 ## Navigation & UX
 
-- [ ] **New landing/home page** — Replace the current entry point with a proper home screen offering clear navigation to: Manage Profile, View Game Stats, Start a New Game, and Browse Game List.
-- [ ] **Game stats page** — Surface per-user statistics: games played, win rate, average solve time by difficulty, best times, streaks, etc.
+- [ ] **[P1]** **New landing/home page** — Replace the current entry point with a proper home screen offering clear navigation to: Manage Profile, View Game Stats, Start a New Game, and Browse Game List.
+- [ ] **[P2]** **Game stats page** — Surface per-user statistics: games played, win rate, average solve time by difficulty, best times, streaks, etc.
 
 ---
 
 ## Progressive Web App (PWA)
 
-- [ ] **Convert Sudoku.React to PWA** — Add a Web App Manifest, service worker, and offline caching strategy so the React app can be installed on mobile/desktop and played without a connection.
-- [ ] **Convert Sudoku.Blazor to PWA** — Add PWA support to the Blazor Server app. Note: Blazor Server relies on a live SignalR connection, so offline play may be limited — consider caching the shell and showing a graceful offline message.
+- [ ] **[P3]** **Convert Sudoku.React to PWA** — Add a Web App Manifest, service worker, and offline caching strategy so the React app can be installed on mobile/desktop and played without a connection.
+- [ ] **[P3]** **Convert Sudoku.Blazor to PWA** — Add PWA support to the Blazor Server app. Note: Blazor Server relies on a live SignalR connection, so offline play may be limited — consider caching the shell and showing a graceful offline message.
 
 ---
 
 ## Gameplay Enhancements
 
-- [ ] **Hint system** — Allow users to request a hint (reveal one correct cell) with a configurable limit per game.
-- [ ] **Difficulty-based scoring** — Award points based on difficulty, solve time, and hints used.
+- [ ] **[P2]** **Hint system** — Allow users to request a hint (reveal one correct cell) with a configurable limit per game.
+- [ ] **[P2]** **Difficulty-based scoring** — Award points based on difficulty, solve time, and hints used.
 
 ---
 
 ## Performance
 
-- [ ] **Pre-generated puzzle pool** — Run a background `IHostedService` that continuously generates puzzles for each difficulty and queues them in memory (or a distributed cache like Redis). When a player requests a new game, dequeue a ready puzzle instead of generating one on-demand. The service refills the pool asynchronously in the background. This turns a multi-second blocking generation into a near-instant lookup and eliminates the timeout on the "new game" endpoint.
+- [ ] **[P2]** **Pre-generated puzzle pool** — Run a background `IHostedService` that continuously generates puzzles for each difficulty and queues them in memory (or a distributed cache like Redis). When a player requests a new game, dequeue a ready puzzle instead of generating one on-demand. The service refills the pool asynchronously in the background. This turns a multi-second blocking generation into a near-instant lookup and eliminates the timeout on the "new game" endpoint.
 
 ---
 
 ## Quality & Polish
 
-- [ ] **Feature flag / shared feature contract** — Define a shared list of features that both Blazor and React must implement, so parity gaps are caught early (could be a simple checklist in this file or a lightweight config).
-- [ ] **End-to-end tests** — Add Playwright or Cypress tests covering the main user flows (new game, solve, profile creation) for both frontends.
-- [ ] **Mobile-responsive layout audit** — Review both frontends on small screens now that PWA is a goal; fix any layout issues.
+- [ ] **[P3]** **Feature flag / shared feature contract** — Define a shared list of features that both Blazor and React must implement, so parity gaps are caught early (could be a simple checklist in this file or a lightweight config).
+- [ ] **[P3]** **End-to-end tests** — Add Playwright or Cypress tests covering the main user flows (new game, solve, profile creation) for both frontends.
+- [ ] **[P3]** **Mobile-responsive layout audit** — Review both frontends on small screens now that PWA is a goal; fix any layout issues.