Compare commits

..
Author SHA1 Message Date
dev_agentandClaude Opus 5.5 cf8046060a Name the dinners.Dinner responses that carry photo_backfill_eligible (F23-1)
CI / ci (pull_request) Successful in 9m49s
CI / ci (push) Successful in 9m53s
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 23:19:07 -04:00
dev_agentandClaude Opus 5.5 886aa5e9c2 Narrow photo_backfill_eligible doc to the responses that carry it (F23-1)
CI / ci (push) Successful in 9m41s
CI / ci (pull_request) Successful in 9m40s
docs/ARCHITECTURE.md said every dinner response carries
photo_backfill_eligible, but GET /api/v1/dinners/{id} returns Detail,
which has no such field. Name the responses that carry it instead.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 23:06:38 -04:00
orchestrator-agent e8ec2dac22 Photo backfill UI: fix-recipe failures and trigger (Maestro 7a468d2d, Feature 23 task 2) (#206)
CI / ci (push) Successful in 9m44s
CI / ci (pull_request) Successful in 9m41s
Co-authored-by: orchestrator-agent <20+orchestrator-agent@code.cubecraftcreations.com>
2026-10-11 22:55:33 -04:00
+6 -3
View File
@@ -276,9 +276,12 @@ automatic** (D-021).
`grounded`, `failed` (with its reason) or `skipped`. A dinner whose write
fails is `failed` with `grounding_error` and left as it was; the others
still run, then the job fails with `internal_error`, keeping that result.
Every dinner response carries `photo_backfill_eligible`, whether the
backfill grounds that dinner, computed by the same condition it lists
dinners by, so a client offers a search only where one runs.
The responses returning a `dinners.Dinner` representation (the list; the
create, update, archive, favorite and grounding responses; the idea
responses) carry `photo_backfill_eligible`, and
`GET /api/v1/dinners/{id}` does not; it says whether the backfill grounds
that dinner, computed by the same condition it lists dinners by, so a
client offers a search only where one runs.
`GET /api/v1/dinners/{id}/recipe-candidates`
searches for the dinner's name and returns `{candidates: [{candidate_id,
title, site_name, photo_url, minutes}]}`, at most 3, ranked as `Ground`