Background grounding and recipe fix-up API #90

Merged

approver_agent merged 2 commits from task/background-grounding_0cbaa5bf-8be4-4cbd-aab2-891e7f1bc2b5 into feature/2066f34b-5804-410a-859b-f87021a8ae6c-regular-dinners-onboarding 2026-10-06 16:39:11 -04:00

Conversation 2 Commits 2 Files Changed 23

+2424 -83

2 Commits

Author	SHA1	Message	Date
dev_agentandClaude Opus 5.5	f4bed5d82d	Fail interrupted groundings at boot and bound hand grounding ... At boot, after the job runner fails the jobs a previous process left running, FailInterruptedGroundings sets every dinner still pending with no ground_dinner job queued or running to failed (interrupted). A crash mid-job, or between saving a dinner and enqueuing its job, no longer leaves the dinner pending forever. A search failure on recipe-candidates or ground now logs only the reason code search_failed, never the wrapped error, which may quote the provider; the response stays redacted. When the grounding job cannot be enqueued, POST /dinners answers 201 with the saved dinner failed (grounding_error) and grounding_job_id null, instead of a 500 that hid the dinner it had created. Grounding a candidate or link by hand runs under a 90-second deadline (fetch, photo, normalize_recipe); past it the request answers 504 ground_timeout and the dinner is unchanged. Maestro task: 0cbaa5bf-8be4-4cbd-aab2-891e7f1bc2b5 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-06 16:30:53 -04:00
dev_agentandClaude Opus 5.5	d6d82e8368	Ground new Regulars in the background and add recipe fix-up API ... Creating a Regular now enqueues a ground_dinner job and returns at once with its grounding_job_id. The job grounds the dinner's recipe_url with GroundURL, else its name with Ground, and sets grounding_status grounded (recipe, photo, method, minutes, difficulty) or failed with a grounding_error reason code (migration 0009). It writes only a dinner still pending, so a fix made meanwhile wins. GET /api/v1/dinners/{id}/recipe-candidates returns up to 3 ranked candidates {candidate_id, title, site_name, photo_url, minutes} without downloading photos or running the model. POST /api/v1/dinners/{id}/ground takes exactly one of {candidate_id}, {recipe_url} or {manual: {...}} and sets grounded or manual. PhotoCache takes an ImageFetcher interface and recipestest provides fakes so other packages can test grounding with fake search, fetch and model. main wires the Grounder with normalize_recipe over the AI settings. Maestro task: 0cbaa5bf-8be4-4cbd-aab2-891e7f1bc2b5 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-06 16:14:31 -04:00