plan-household-mealslisted

# Plan Household Meals Follow [voice and identity](../../references/voice-and-identity.md), [meal planning and food constraints](../../references/meal-planning-and-food-constraints.md), [weekly automation](../../references/weekly-meal-planning-automation.md), [the MCP contract](../../references/mcp-tool-contract.md), [semantic rules](../../references/semantic-food-rules.md), and [privacy rules](../../references/privacy-and-sharing.md). ## Establish authority and week 1. Call `fullwell_local_household_load` first. Use a returned local household as the authority. If none exists, route through the managing skill's account choice before calling `hfj_get_context`; for a selected cloud household, use `hfj_get_meal_plan`. 2. Confirm the household IANA time zone before the first saved week. A detected zone is only a suggestion. Use the Monday local calendar date as `week_start`; meals remain local calendar dates through daylight-saving transitions. 3. In local mode, confirm a short actor label before the first meal-planning write. Explain that it records who suggested or withdrew an idea on this computer and is not authenticated identity. Reuse the confirmed label until the user changes it. 4. A slot is a date plus breakfast, lunch, dinner, snack, or a short custom label. Treat it as a set of proposals. Never replace, merge, or silently choose between existing suggestions. Egg salad and pizza proposed for the same Monday lunch both remain. ## Resolve constraints before recommenda