Meals in a plan can now be checked off as cooked, so the active plan shows at a glance what's been made and what's still ahead.
Cooked check-offs
- Every meal card on an active or completed plan gets a Complete button — tap to mark it cooked ("Completed ✓", the card dims), tap again to undo. The plan header counts along: "5 meals · 2 cooked · active".
- Check-offs follow the plan's lifecycle: revising a plan keeps the check-off for meals that survive the revision (same recipe, same meal type — mirroring how grocery items keep their checked state); completing a plan keeps them as history; reactivating a completed plan ("Cook it again") starts a fresh run with everything unchecked.
- Upcoming plans don't show Complete buttons — nothing's been cooked from a queued plan.
Snappier recipe cards
Recipe cards no longer expand into an accordion with a second "Open recipe" step — tapping a card goes straight to the recipe.
MCP
Additive only, no breaking changes: every plan-reading tool (get_active_meal_plan, get_meal_plan, list_meal_plans, and push_meal_plan results) now includes mealId and cookedAt on each meal, so the agent can answer "what's left to cook this week?". Check-offs happen in the app UI; restart your MCP client (e.g. LibreChat) after upgrading so it picks up the refreshed push_meal_plan tool description.
Upgrading
Back up ./data/, then docker compose pull && docker compose up -d. The database migrates automatically on boot — a single added column, no table rebuilds.