6 Commits

Include renames

Author	SHA1	Message	Date
dev_agentandClaude Opus 5.5	51bae14b7b	Require the household's name for a Regular added from a link (PR #97 review R4-F1) ... A pasted link may carry a personal token anywhere in its path, so no part of it can safely name a dinner: the slug heuristic always let some plain words through. POST /api/v1/dinners now takes {name} or {name, recipe_url}; a link without a name is 400 invalid_dinner, and nameFromURL is gone. The link is still kept only for grounding and for the recipe-link duplicate rule. Name-created Regulars, grounding, and the rename rules are unchanged. On the Regulars screen, pasting a link shows a "Dinner name" field, and Add stays disabled until it is filled. The optimistic row shows that name, never the link. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-06 21:16:16 -04:00
dev_agentandClaude Opus 5.5	c15c8ec284	Keep recipe_url out of dinner responses (Feature 12 review F1) ... A pasted recipe link may carry a personal token in its query, and the dinners API returned it from create, list, get, patch and ground, where other household clients and the PWA's cache of dinner reads could keep it. Drop recipe_url from the public Dinner shape so it stays in the database for grounding and dedupe only. TestCreateDinnerByURL and TestCreateDinnerByName now assert the field is absent; TestDinnerResponsesHideRecipeURL creates a Regular from a token-bearing link and checks neither the create nor the list response holds the link, host or token while the stored link remains. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-06 20:35:19 -04:00
orchestrator-agent	5dff7825d8	Integration fix 2: conditional recipe repairs and no pasted links in logs (Feature 12 review F1, F2) (#96) ... Co-authored-by: orchestrator-agent <20+orchestrator-agent@code.cubecraftcreations.com>	2026-10-06 20:26:56 -04:00
orchestrator-agent	cc7875c76c	Integration fix: Feature 12 feature-review findings F1-F8 (#95) ... Co-authored-by: orchestrator-agent <20+orchestrator-agent@code.cubecraftcreations.com>	2026-10-06 19:54:47 -04:00
dev_agentandClaude Opus 5.5	171c9c2d11	Fix stale Regular grounding and enforce three Regulars for onboarding ... A background grounding result now applies only while the dinner is still pending under the normalized name the job searched: GroundPendingDinner and FailPendingDinnerGrounding match normalized_name, so a rename makes the old job's success or failure a no-op. Renaming a dinner still pending enqueues a fresh grounding job for the new name; if that cannot be enqueued, the dinner's grounding is failed so it is not left pending with no job. Completing onboarding (PATCH /api/v1/settings/household with onboarding_completed true) is refused with 400 invalid_settings until the household has at least three Regulars (status regular; archived and Quest log dinners do not count), and onboarding_completed_at is set only then. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-06 18:47:41 -04:00
dev_agent	423b898f54	Background grounding and recipe fix-up API (#90) ... Co-authored-by: dev_agent <dev_agent@cubecraftlabs.com>	2026-10-06 16:39:10 -04:00