Maniacs_Mansion/MealQuest
11
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Photo backfill for failed dinners without a photo (Maestro 36c40130, Feature 23 task 1) #205

Merged
approver_agent merged 3 commits from task/photo-backfill-backend_36c40130-a69a-46ed-a047-2cdc5ee2d2e0 into feature/1e5f7fa3-5308-4ced-8c2d-1da1cc6256f9-meal-photos-manual-dinners 2026-10-11 21:44:56 -04:00
Conversation 2 Commits 3 Files Changed 12
+913 -3
3 Commits
Author SHA1 Message Date
dev_agentandClaude Opus 5.5 32453d552b Test photo backfill single-flight under simultaneous triggers
CI / ci (push) Successful in 9m54s
Details
CI / ci (pull_request) Successful in 9m55s
Details 
TestStartPhotoBackfillIsSingleFlight now releases eight
StartPhotoBackfill calls together behind a start gate, both while the
pass is queued and while it runs, and asserts they all return the one
job id with a single backfill job stored. The restart case closes the
store and reopens it from the data directory before triggering again.

Maestro task 36c40130-a69a-46ed-a047-2cdc5ee2d2e0 (review finding F23-1-T).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
 2026-10-11 21:34:09 -04:00
dev_agentandClaude Opus 5.5 7c0eb5cc3a Make photo backfill single-flight and fail on unrecorded writes
CI / ci (pull_request) Successful in 10m6s
Details
CI / ci (push) Successful in 10m10s
Details 
Task 36c40130-a69a-46ed-a047-2cdc5ee2d2e0, remediation of review
findings F23-1 and F23-2 (PR #205).

F23-1: StartPhotoBackfill now checks, in the same write transaction
that enqueues, for a full backfill_dinner_photos job already queued or
running (new GetActivePhotoBackfillJob query) and returns its id instead
of enqueuing another, as plan.StartDraft does with GetActiveDraftJob.
The claim is the stored job row, so it holds across restarts; a job left
running by a stopped process is failed at boot and no longer blocks.

F23-2: a dinner whose outcome write fails is still reported failed with
grounding_error and the remaining dinners still run, but the job then
fails (internal_error, as a ground_dinner job's failed write does) with
the per-dinner outcomes published as its result, so it never reports
success for state it did not store.

Tests: overlapping triggers while queued, after a restart and while
running return the one job; a refused dinner write fails the job.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
 2026-10-11 21:16:13 -04:00
dev_agentandClaude Opus 5.5 ec718024a1 Add photo backfill for failed dinners without a photo
CI / ci (pull_request) Failing after 10m12s
Details
CI / ci (push) Successful in 11m35s
Details 
Task 36c40130-a69a-46ed-a047-2cdc5ee2d2e0 (Feature 23, task 1 of 2).

A backfill_dinner_photos job grounds, by name with the existing
recipes.Grounder.Ground, every unarchived dinner whose grounding failed
and that has no photo and no pasted recipe_url. Ground already tries the
ranked candidates best first and keeps the first whose photo caches and
whose ingredients normalize, reusing stored recipes and photos. Success
records the recipe and photo as grounded; a failure leaves the dinner
failed with the new grounding_error for the fix-recipe flow, without
stopping its siblings. Writes are guarded on status, photo and
grounding_revision, so grounded, manual, pending, renamed and archived
dinners are never touched.

POST /api/v1/settings/photo-backfill starts a full pass and answers 202
with the job id; the kind is service-only.

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