4 Commits

Include renames

Author	SHA1	Message	Date
dev_agentandClaude Opus 5.5	9616941b73	Report the Supply run outcome after Push to Calendar ... The push client parsed only the plan from POST /plans/{weekStart}/push-calendar and dropped supply_run, so a Supply run that was not made was shown as a successful push (F17-01). Parse supply_run as the server sends it and tell the household every outcome on the Plan: made, left as it was in the Supply archive, or not made, with its recovery: push again for plan_changed (reading the edited plan again first), or make the shopping list again through the existing generate endpoint for supply_run_failed. A push whose Supply run failed stays in the mutation cache like a failed push, so leaving the week before it settles still shows it on coming back. Read the week's Supply run again when the push answers, using the Supply run screen's supplyRunKey, so a cached 404 or the earlier list is not shown for the freshness window (F17-02). Maestro task e75db0f0-817f-4eef-84b2-266e793c018a. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-08 13:36:13 -04:00
orchestrator-agent	5d7906ae0d	Build the Supply run screen at /plan/shopping (Feature 17) (#136) ... Co-authored-by: orchestrator-agent <20+orchestrator-agent@code.cubecraftcreations.com>	2026-10-08 09:49:26 -04:00
orchestrator-agent	7003ff92ec	Feature 16: Google Calendar Sync (#130) ... Co-authored-by: orchestrator-agent <20+orchestrator-agent@code.cubecraftcreations.com>	2026-10-08 03:13:21 -04:00
orchestrator-agent	1862f450db	Feature 14: Weekly Plan Builder (#121) ... Co-authored-by: orchestrator-agent <20+orchestrator-agent@code.cubecraftcreations.com>	2026-10-07 16:53:23 -04:00