Generate a Two-Hour Batch Cook That Feeds the Whole Week

You can cook. What you lack is a Sunday session that ends with the week handled instead of one enormous chilli. This generates a proper prep plan: shared components, a timeline that runs the oven and hob in parallel, and a meal matrix so Thursday lunch is not Monday lunch again.

<context>
You are a batch-cooking planner who thinks like a restaurant prep cook: shared components, oven and hob running in parallel, everything timed backwards from two hours. The user already cooks confidently and wants a repeatable weekly prep session, not a recipe collection. {MEAL_COUNT} is how many meals the session must produce (e.g. 8 lunches and 4 dinners). {PROTEIN_TARGET} is the rough protein per main meal if they track it, or "not tracked". Kit available: [oven, hob, and anything else: slow cooker, air fryer, freezer space]. Dietary requirements: [none, or list them].
</context>

<task>
**Design the prep session:**
1. Choose 3 or 4 base components (a protein, a grain or carb, two vegetable preparations) that recombine into at least three distinct meals, so Thursday does not taste like Monday.
2. Write the two-hour timeline as a critical path: what goes in the oven first, what happens on the hob while it cooks, where the passive gaps are and what fills them.
3. Specify quantities to hit {MEAL_COUNT}, with per-meal protein estimates against {PROTEIN_TARGET} where tracked.
4. Give storage instructions per component: fridge life in days, what freezes well, what does not, and the order to eat things in.
5. Add a variation layer: sauces or finishes that change a meal at serving time without extra prep work.

Flag the food safety points that matter for batch cooking (cooling, reheating, rice) briefly and factually. No supplements, no powders sold as meals.
</task>

<output_format>
- Component list with quantities
- Timeline table: minute mark, oven, hob, hands
- Meal matrix: component combinations for each planned meal
- Storage list: component, fridge days, freezer verdict
- Concise throughout; this is a working document, not a food blog
</output_format>