Mobile recipe detail (1k) (Feature 15) #145

Merged

approver_agent merged 2 commits from task/mobile-recipe-detail_70a903ef-107c-444e-b3b0-fb3d37e8fb7d into feature/293a89c5-bd98-4de4-9afd-5ca371e5e679-recipe-detail-and-kitchen-reading-mode

2026-10-08 20:36:48 -04:00

Author	SHA1	Message	Date
dev_agentandClaude Opus 5.5	57fa849ab4	Keep the recipe action bar at the bottom and pause polling offline CI / ci (push) Successful in 5m38s Details CI / ci (pull_request) Successful in 5m4s Details The detail page now fills the shell's scroll area (min-height: 100% of a stretched flex item) and the sheet grows into the room left, so on a short or failed recipe Add to this week and the heart rest at the bottom of the screen; over a long recipe the bar still sticks there. useDinnerDetail reads through apiRead and keeps whether the answer was the service worker's saved copy. A pending dinner is polled only while the network status says the server can be reached and the last answer was not a saved copy; a saved pending copy is read again once the connection comes back. TanStack Query clears the interval on unmount. The credit stays plain text. source.url is parsed when present (https, no userinfo, query or fragment, else the read fails) and makes "Recipe from {site}" a new-tab link; today's API never sends it. Maestro task 70a903ef-107c-444e-b3b0-fb3d37e8fb7d. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-08 20:10:26 -04:00
dev_agentandClaude Opus 5.5	6d7c57eced	Build the mobile recipe detail screen (mock 1k) CI / ci (push) Successful in 5m9s Details CI / ci (pull_request) Successful in 5m4s Details Replace the /dinner/:id placeholder with DinnerDetailPage, reading GET /api/v1/dinners/{id} through useDinnerDetail: a 250 px full-bleed washed photo (striped placeholder without one) with a round back button that goes Home from a deep link; a sheet overlapping by 28 px with the Regular or Side quest, difficulty and time tags, the 28 px Bagel title, the teal "Why it was picked" box, ingredients in recipe order with quantities right-aligned (raw_text when a line has no name), numbered steps and "Recipe from {site}" when the server names a site. The API sends no source link, so the credit is text, not a link. A dinner whose recipe was not found links to Settings -> Regular dinners instead of showing a recipe; a pending one says it is still searching and is read again until it lands. A 404 is a "Dinner not found" state; other failures retry. The sticky bar renders "Add to this week" and the heart (showing is_favorite) unavailable until task 07423ba7 wires them. IconButton gains a 52 px size for the heart. Maestro task 70a903ef-107c-444e-b3b0-fb3d37e8fb7d. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-08 19:53:52 -04:00

Author

SHA1

Message

Date

dev_agentandClaude Opus 5.5

57fa849ab4

Keep the recipe action bar at the bottom and pause polling offline

CI / ci (push) Successful in 5m38s

Details

CI / ci (pull_request) Successful in 5m4s

Details

The detail page now fills the shell's scroll area (min-height: 100% of
a stretched flex item) and the sheet grows into the room left, so on a
short or failed recipe Add to this week and the heart rest at the
bottom of the screen; over a long recipe the bar still sticks there.

useDinnerDetail reads through apiRead and keeps whether the answer was
the service worker's saved copy. A pending dinner is polled only while
the network status says the server can be reached and the last answer
was not a saved copy; a saved pending copy is read again once the
connection comes back. TanStack Query clears the interval on unmount.

The credit stays plain text. source.url is parsed when present (https,
no userinfo, query or fragment, else the read fails) and makes "Recipe
from {site}" a new-tab link; today's API never sends it.

Maestro task 70a903ef-107c-444e-b3b0-fb3d37e8fb7d.

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

2026-10-08 20:10:26 -04:00

dev_agentandClaude Opus 5.5

6d7c57eced

Build the mobile recipe detail screen (mock 1k)

CI / ci (push) Successful in 5m9s

Details

CI / ci (pull_request) Successful in 5m4s

Details

Replace the /dinner/:id placeholder with DinnerDetailPage, reading
GET /api/v1/dinners/{id} through useDinnerDetail: a 250 px full-bleed
washed photo (striped placeholder without one) with a round back button
that goes Home from a deep link; a sheet overlapping by 28 px with the
Regular or Side quest, difficulty and time tags, the 28 px Bagel title,
the teal "Why it was picked" box, ingredients in recipe order with
quantities right-aligned (raw_text when a line has no name), numbered
steps and "Recipe from {site}" when the server names a site. The API
sends no source link, so the credit is text, not a link.

A dinner whose recipe was not found links to Settings -> Regular
dinners instead of showing a recipe; a pending one says it is still
searching and is read again until it lands. A 404 is a "Dinner not
found" state; other failures retry. The sticky bar renders "Add to this
week" and the heart (showing is_favorite) unavailable until task
07423ba7 wires them. IconButton gains a 52 px size for the heart.

Maestro task 70a903ef-107c-444e-b3b0-fb3d37e8fb7d.

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

2026-10-08 19:53:52 -04:00