Regular dinners management screen #93

2 Commits
Author SHA1 Message Date
dev_agentandClaude Opus 5.5 b2e02223c6 Require method and minutes for a typed-in recipe; pause refresh on every save
CI / ci (push) Successful in 2m19s
CI / ci (pull_request) Successful in 2m17s
The manual recipe form now enables Save only once method and minutes are
set, as POST /api/v1/dinners/{id}/ground requires, and always sends both.

useRegulars watches the Regulars changes in flight with useIsMutating, so
the grounding refresh pauses while an edit or a recipe fix is being saved,
not only while an add or favorite changes the list, and resumes after.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-06 18:21:05 -04:00
dev_agentandClaude Opus 5.5 e3332aba35 Add the Regular dinners settings screen
CI / ci (push) Successful in 2m22s
CI / ci (pull_request) Successful in 2m17s
/settings/regulars lists the household's Regulars with photo, name,
"method · minutes", the favorite heart and a grounding badge ("Finding
recipe…", "Recipe found", "Needs a recipe"). The add field takes a name
or a pasted recipe link. Tapping a Regular opens an edit sheet (rename,
method, minutes, difficulty, remove with confirmation); a Regular that
needs a recipe opens "Fix recipe": pick one of up to three candidates,
paste a link, or type the ingredients and steps in. The list is read
again every 3 seconds while any Regular is still finding its recipe.

The dinners client now parses the full dinner and adds edit, favorite,
ground and recipe-candidate calls; onboarding shares its refusal
tracking through useRefusals.

Maestro task: fa8f88ae-5ade-430e-a069-274aec112f26

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-06 18:10:53 -04:00