docs: Sprint 11 — wire the dead "Generate Meal Plan" CTA across all 6 running docs

Sprint 11 (commit 41154e9) wires the previously-dead
"Generate Meal Plan" empty-state CTA on the Dashboard to two
existing endpoints (POST /api/meals + POST /api/meals/{id}/fill-
empty-slots). No backend changes; no new dependencies. The
handler lives on the client for now; future F8 (Spoonacular) +
F9 (Ollama) will swap the fillEmptySlots call for an LLM call
without changing the DOM. F8 + F9 remain in the §Future backlog.

This commit updates the 6 running docs that track the sprint:

- .agent/plan.md — Sprint 11 section (S11.1-S11.3) added.
- .agent/context.md — Sprint 11 (D1-D6, Q1-Q3) added; file:line
  references; key takeaways.
- Review/sprint11-verification.md — new file: 4-step browser
  smoke + race test + 2 API curls + a11y check + risks + future
  work section.
- Review/ui-nielsen-audit.md — Sprint 11 status block (T5.1-T5.3)
  at the top, after the Sprint 10 block.
- fix-ui-audit.md — Sprint 11 section (T5.1-T5.5) added after the
  Sprint 10 section.
- Review/handoff-ui-audit.md — Batch G added to the deploy
  instructions; Sprint 11 section added after Sprint 10; TL;DR
  table row 11 added; Last-updated footer updated.
- docs/HANDOFF.md — Sprint 11 section added after the Sprint 10
  section, with a path-forward paragraph for F8/F9.

All 6 docs now reflect Sprint 11. §Future backlog remaining: F8
(Spoonacular) + F9 (Ollama) proposals, both full backend work.

.agent/plan.md

@@ -285,4 +285,58 @@ User reported post-deploy: "The tour window looks great, but Clicking the X nor
 - A "Manage blocked recipes" page.
 - Bulk unblock.
 - Touch-device gesture for the card overlay (the focus state already surfaces the button on tap).
+
+---
+
+## Sprint 11 — Wire the dead "Generate Meal Plan" CTA (Dashboard.tsx:499-504)
+
+**User direction (2026-06-05):** "Proceed." Selected from the question menu as the smallest §Future item. F1 (Sprint 9) is shipped, F8 (Spoonacular) + F9 (Ollama) are full backend proposals, and the dead `Generate Meal Plan` CTA at `Dashboard.tsx:503` is the final remaining item. The button is rendered with `onClick: () => {}` — clicking it does nothing. Wired to existing endpoints, no backend changes, no new dependencies.
+
+**Root cause:** the user lands on the Dashboard with no meal plan and sees a "Generate Meal Plan" button. Clicking it does nothing. The backend already has the two endpoints needed (`POST /api/meals` to create a plan + `POST /api/meals/{id}/fill-empty-slots` to fill it from the recipe library), and the `fillEmptySlots` partial-success report pattern is already in production for the existing `Plan Week` menu (`handlePlanWeek` at `Dashboard.tsx:366-392`). The wiring is a 25-line client-side glue function that calls both in sequence.
+
+### S11.1 — `handleGenerateFirstPlan()` in `Dashboard.tsx`
+
+- [ ] Add a new handler next to `handlePlanWeek` (line 366) that:
+  1. Reads `weekStart` (already in scope).
+  2. `POST /api/meals` with `{ week_start_date: weekStart, status: 'draft' }` to create an empty plan.
+  3. On success, `POST /api/meals/{newId}/fill-empty-slots` with `{ meal_types: ['breakfast', 'lunch', 'dinner'] }`.
+  4. Invalidate `['mealPlan', weekStart]`.
+  5. Toast: reuse the same partial-success pattern as `handlePlanWeek` (`"Planned N of M meals — K failed"`).
+- [ ] Wire `onClick` of the `EmptyState.action` (line 503) to call `handleGenerateFirstPlan()`.
+- [ ] Track a `generatingFirstPlan` state for the loading spinner; swap the button label to `"Generating…"` while in-flight.
+- [ ] Handle the `"Meal plan for this week already exists"` 400 from `meals.create` (race condition with another tab) by calling `fillEmptySlots` directly with the existing plan's id — refetch the plan from `getPlanned(weekStart)` to get the id.
+
+### S11.2 — Verify
+
+- [ ] `npm run build` green (tsc 0 errors, vite 0 errors).
+- [ ] Browser smoke (4 steps) on `http://100.108.208.56:8082/`:
+  1. Log in as a family with no meal plan for the current week. Land on `/`.
+  2. Confirm `EmptyState` shows "Generate Meal Plan" button.
+  3. Click the button. Confirm: button label flips to "Generating…", toast appears with "Planned N of M meals", empty state disappears, plan grid renders.
+  4. Refresh the page. Confirm the plan persists.
+- [ ] Race test: open two tabs, both click "Generate Meal Plan" at the same moment. Second tab should still succeed (handled by the `meals.create` 400 → fall-through to `fillEmptySlots` path).
+- [ ] No regression in Sprints 1-10.
+
+### S11.3 — Docs (all 6 running docs updated)
+
+- [ ] `Review/ui-nielsen-audit.md` — Sprint 11 status block at the top.
+- [ ] `fix-ui-audit.md` — Sprint 11 plan section (T5.1-T5.3).
+- [ ] `Review/handoff-ui-audit.md` — Sprint 11 entry in the "How to take over" section + TL;DR row.
+- [ ] `docs/HANDOFF.md` — Sprint 11 section.
+- [ ] `.agent/plan.md` — this section.
+- [ ] `.agent/context.md` — Sprint 11 decisions + file:line references.
+- [ ] `Review/sprint11-verification.md` — written (4-step browser smoke + race test).
+
+### Done when (Sprint 11)
+
+- All boxes above ticked.
+- `npm run build` green.
+- `Review/sprint11-verification.md` exists.
+- All 6 doc files have a Sprint 11 status block.
+
+### Out of scope (Sprint 11)
+
+- LLM-powered generation (F8 Spoonacular, F9 Ollama) — separate backend proposals, future sprints. Sprint 11 only wires the existing recipe-library-based fill.
+- A "what would you like for dinner?" prompt before generation — the existing flow generates from the library with no user input.
+- A "regenerate" button after the plan exists — the existing `Plan Week` menu at `Dashboard.tsx:366-392` already handles this case.
 - F8 Spoonacular + F9 Ollama + dead `Generate Meal Plan` CTA — separate.