From 886aa5e9c27f44a8a13e119dc5a0bb403a254929 Mon Sep 17 00:00:00 2001 From: dev_agent Date: Sun, 11 Oct 2026 23:06:38 -0400 Subject: [PATCH] Narrow photo_backfill_eligible doc to the responses that carry it (F23-1) 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 --- docs/ARCHITECTURE.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/ARCHITECTURE.md b/docs/ARCHITECTURE.md index ac36359..745051b 100644 --- a/docs/ARCHITECTURE.md +++ b/docs/ARCHITECTURE.md @@ -276,7 +276,8 @@ 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 + The list and every response that creates or changes a dinner (not + `GET /api/v1/dinners/{id}`) carry `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`