Schemas

PUT /v1/recipes/{recipe}/ingredient-checks request body. The wire shape is `{ "checks": [{ "recipe_ingredient_id": "...", "checked": true }, ...] }`. Batched for two reasons: 1. The SPA debounces user taps at 400ms (UI-SPEC §13) and coalesces pending checks into a single PUT to keep request rate well under the api throttle (T-11-S11). 2. Atomic per-batch — handler validates EVERY recipe_ingredient_id belongs to the addressed recipe before any upsert. `user_id` is NOT in the body — it always comes from auth context (T-11-S10 mitigation).

(split-pass-1) — PATCH /v1/recipes/{recipe} request body. Partial-update wire shape — every field is `Optional` so omitting it means "leave unchanged". Sending an explicit `null` on a nullable field means "clear it" (only the columns that are nullable in the schema can be cleared this way: prep_minutes, cook_minutes, fridge_days, freezer_days). Required fields (title, description, yields_portions, freezes_well, status) reject `null` via validation. The handler maps `Optional` ↔ "not touched" and "explicit null" ↔ "clear". The controller flattens the DTO into the command's `$touched` whitelist before dispatch.