Dinner detail API (Feature 15) #143

Merged

approver_agent merged 3 commits from task/dinner-detail-api_099e9952-7f98-4700-8369-241c589a1e9d into feature/293a89c5-bd98-4de4-9afd-5ca371e5e679-recipe-detail-and-kitchen-reading-mode

2026-10-08 19:46:32 -04:00

Author	SHA1	Message	Date
dev_agentandClaude Opus 5.5	58047059f9	Withhold a site name that could be the recipe link's host CI / ci (push) Successful in 5m51s Details CI / ci (pull_request) Successful in 5m1s Details A page that names no site is stored under its host, which may be the pasted link's (a token in a subdomain) or a redirect's. The dinner detail now returns source.site_name only when the stored name could not be a host: the link's own host, an IP address or a dotted host name is withheld as null, so "Recipe from {site}" shows only real attribution. The extractor's host fallback is shared as recipes.HostSiteName. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-08 19:15:42 -04:00
dev_agentandClaude Opus 5.5	d37a784190	Hide the recipe link, pick the creating suggestion, refuse duplicate positions CI / ci (push) Successful in 6m27s Details CI / ci (pull_request) Successful in 6m11s Details Dinner detail review fixes for GET /api/v1/dinners/{id}: - source is now {site_name} with no url. A stored source_url may be a pasted or offered link carrying a personal token, and nothing can show a stored link is free of one; the candidate flow keeps every page URL on the server for the same reason, so the detail does too. - why_picked comes from GetDinnerSuggestionReasons, which reads only pending or accepted suggestions: a suggestion is only ever created with a new dinner and declining one archives that dinner, so a declined row never created a live dinner. More than one candidate row is an error rather than a guess. sqlc regenerated. - Two recipe ingredients or steps at one position leave recipe order unknown, so the read fails rather than ordering them by id. Maestro task 099e9952-7f98-4700-8369-241c589a1e9d. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-08 19:00:40 -04:00
dev_agentandClaude Opus 5.5	2217f4e5ad	Add GET /api/v1/dinners/{id} dinner detail CI / ci (push) Successful in 6m25s Details CI / ci (pull_request) Successful in 5m12s Details Returns a dinner with its recipe for the recipe detail screen and Kitchen reading mode: photo URLs at both cached sizes (400/1200) or null, ingredients and steps in recipe position order, the source page for a fetched recipe, grounding status and error, and why_picked, the reason of the suggestion that created the dinner (null when none). Unknown and archived dinners are 404. Read in one transaction. Adds the GetDinnerSuggestionReason query (sqlc regenerated). The dinners test env now serves photos from the grounder's own store and data directory so photo URLs can be fetched in tests. Maestro task 099e9952-7f98-4700-8369-241c589a1e9d. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-08 18:50:18 -04:00

Author

SHA1

Message

Date

dev_agentandClaude Opus 5.5

58047059f9

Withhold a site name that could be the recipe link's host

CI / ci (push) Successful in 5m51s

Details

CI / ci (pull_request) Successful in 5m1s

Details

A page that names no site is stored under its host, which may be the
pasted link's (a token in a subdomain) or a redirect's. The dinner
detail now returns source.site_name only when the stored name could not
be a host: the link's own host, an IP address or a dotted host name is
withheld as null, so "Recipe from {site}" shows only real attribution.
The extractor's host fallback is shared as recipes.HostSiteName.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-08 19:15:42 -04:00

dev_agentandClaude Opus 5.5

d37a784190

Hide the recipe link, pick the creating suggestion, refuse duplicate positions

CI / ci (push) Successful in 6m27s

Details

CI / ci (pull_request) Successful in 6m11s

Details

Dinner detail review fixes for GET /api/v1/dinners/{id}:

- source is now {site_name} with no url. A stored source_url may be a
  pasted or offered link carrying a personal token, and nothing can show
  a stored link is free of one; the candidate flow keeps every page URL
  on the server for the same reason, so the detail does too.
- why_picked comes from GetDinnerSuggestionReasons, which reads only
  pending or accepted suggestions: a suggestion is only ever created with
  a new dinner and declining one archives that dinner, so a declined row
  never created a live dinner. More than one candidate row is an error
  rather than a guess. sqlc regenerated.
- Two recipe ingredients or steps at one position leave recipe order
  unknown, so the read fails rather than ordering them by id.

Maestro task 099e9952-7f98-4700-8369-241c589a1e9d.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-08 19:00:40 -04:00

dev_agentandClaude Opus 5.5

2217f4e5ad

Add GET /api/v1/dinners/{id} dinner detail

CI / ci (push) Successful in 6m25s

Details

CI / ci (pull_request) Successful in 5m12s

Details

Returns a dinner with its recipe for the recipe detail screen and
Kitchen reading mode: photo URLs at both cached sizes (400/1200) or
null, ingredients and steps in recipe position order, the source page
for a fetched recipe, grounding status and error, and why_picked, the
reason of the suggestion that created the dinner (null when none).
Unknown and archived dinners are 404. Read in one transaction.

Adds the GetDinnerSuggestionReason query (sqlc regenerated). The
dinners test env now serves photos from the grounder's own store and
data directory so photo URLs can be fetched in tests.

Maestro task 099e9952-7f98-4700-8369-241c589a1e9d.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-08 18:50:18 -04:00