Cost a restaurant's menu dishes from recipes with trim yields and unit conversions, and build the week's supplier order in whole cases

# Cost a restaurant's menu dishes from recipes with trim yields and unit conversions, and build the week's supplier order in whole cases Inputs: `ingredients.csv` (ingredient, case_size, case_unit, case_price, yield_pct, on_hand), `recipes.json` (each dish's menu_price and recipe lines of ingredient, qty, unit), `forecast.csv` (dish, portions for next week) and `order-rules.json` (safety_pct). All data is synthetic; amounts are in dollars. These rules are the kitchen's policy; where `chef-note.txt` disagrees, the rules win. Rules: - Units: 1 kg = 1000 g and 1 L = 1000 ml; each is a count. A recipe line's qty is the usable amount after trimming; case_size and on_hand are in the ingredient's case_unit. - Plate cost: a recipe line costs (qty converted to the case_unit) / (yield_pct / 100) × case_price / case_size. A dish's plate cost is the exact sum of its lines, rounded half-up to the cent once (don't round line by line). - Food cost: food_cost_pct = the dish's rounded plate cost / menu_price × 100, rounded half-up to one decimal place. - Ordering: an ingredient's purchase need for the week is the sum over dishes of portions × qty (in the case_unit) / (yield_pct / 100), plus safety_pct percent of that sum. Order the smallest whole number of cases that brings on_hand up to at least the purchase need, or 0 if on_hand already covers it. - Order total: the sum of cases × case_price over all ingredients. - Write `out/kitchen.json`: `{"dishes": {"<dish>": {"plate_cost": <dollars>, "food_cost_pct": <percent>}, ...}, "orders": {"<ingredient>": <cases>, ...}, "order_total": <dollars>}` with every ingredient in `orders`, including those needing 0 cases. ## How this run works - Work on your own: nobody will answer questions in this task, and writing to `ask/` counts against the run. - Write only under `out/`. Create `out/` if it is missing. Inputs are synthetic; don't fetch anything from the network. - Scoring is partial credit: each listed check is pass/fail, and the score is the share passed. Numbers are compared to within 0.005 unless the task says otherwise.