Photo backfill UI: fix-recipe failures and trigger (Maestro 7a468d2d, Feature 23 task 2) (#206)

Co-authored-by: orchestrator-agent <20+orchestrator-agent@code.cubecraftcreations.com>
2026-10-11 22:55:33 -04:00
parent 6127c5c2d1
commit e8ec2dac22
13 changed files with 639 additions and 13 deletions
@@ -276,6 +276,9 @@ 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.
  `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`