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

Feature 23 review fix: narrow the eligibility doc claim #208

Merged
approver_agent merged 2 commits from task/f23-doc-fix into feature/1e5f7fa3-5308-4ced-8c2d-1da1cc6256f9-meal-photos-manual-dinners 2026-10-11 23:31:34 -04:00
Conversation 2 Commits 2 Files Changed 1
+6 -3
1 changed files with 6 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/ARCHITECTURE.md
+6 -3
View File
@@ -276,9 +276,12 @@ 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 responses returning a `dinners.Dinner` representation (the list; the
backfill grounds that dinner, computed by the same condition it lists create, update, archive, favorite and grounding responses; the idea
dinners by, so a client offers a search only where one runs. 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` `GET /api/v1/dinners/{id}/recipe-candidates`
searches for the dinner's name and returns `{candidates: [{candidate_id, searches for the dinner's name and returns `{candidates: [{candidate_id,
title, site_name, photo_url, minutes}]}`, at most 3, ranked as `Ground` title, site_name, photo_url, minutes}]}`, at most 3, ranked as `Ground`