feat(cooking): endpoint GET /cooking-session (plan de cuisine optimisé) #10

Closed

kyuno wants to merge 1 commit from feat/cooking-session-api into feat/cooking-optimizer-engine

kyuno commented

2026-08-28 12:45:46 +02:00

Owner

Regroupée dans #11 (une seule PR pour tout le bloc « Commencer à cuisiner » : moteur + endpoint + page). Fermée.

kyuno added 1 commit 2026-08-28 12:45:46 +02:00

feat(cooking): endpoint GET /cooking-session (plan de cuisine optimise)

CI / test (push) Failing after 0s

Details

CI / lint (push) Successful in 2m37s

Details

CI / build (push) Successful in 2m45s

Details

CI / e2e (push) Failing after 4m19s

Details

CI / intent-service-test (push) Successful in 16m49s

Details

3bff58359e

Module cooking-session : charge le Planning couvrant ?date= (meme requete
"plage couvrante" + degradation "jamais null" que /shopping-list), mappe
chaque PlanningItem vers l'entree pure de optimizeCookingPlan (ingredients/
unites/techniques/ustensiles resolus via toIngredientView/toUnitView
reutilisees de recipe.service), renvoie OptimizedCookingPlanView.

- cookingSessionPlanningInclude reprend le sous-arbre steps de recipeInclude.
- Route requireAuth, contrat ?date= identique a /shopping-list.
- Monte /cooking-session dans app.ts.
- Tests d'integration Mocha (401, date invalide, plan vide sans foyer /
  sans planning, mutualisation d'une decoupe entre 2 recettes planifiees).
- specs/batch-cooking-architecture.md : module "Calcul batch-cooking" TODO
  -> v1 implementee ; nouvelle section dans backend-architecture.md.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>