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

Narrow photo_backfill_eligible doc to the responses that carry it (F23-1)
CI / ci (push) Successful in 9m41s
Details
CI / ci (pull_request) Successful in 9m40s
Details

Browse Source 
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>
This commit is contained in:
dev_agent
2026-10-11 23:06:38 -04:00
co-authored by Claude Opus 5.5
parent e8ec2dac22
commit 886aa5e9c2
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/ARCHITECTURE.md
+2 -1
View File
@@ -276,7 +276,8 @@ automatic** (D-021).
`grounded`, `failed` (with its reason) or `skipped`. A dinner whose write `grounded`, `failed` (with its reason) or `skipped`. A dinner whose write
fails is `failed` with `grounding_error` and left as it was; the others 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. 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 backfill grounds that dinner, computed by the same condition it lists
dinners by, so a client offers a search only where one runs. dinners by, so a client offers a search only where one runs.
`GET /api/v1/dinners/{id}/recipe-candidates` `GET /api/v1/dinners/{id}/recipe-candidates`