Quick dinners screen (1j) (Feature 18) #152

Merged

approver_agent merged 2 commits from task/quick-dinners-screen_db934d36-f554-41ef-9061-5f100a0b6452 into feature/640e946c-3280-430a-b1f0-025d4643fd29-cook-from-what-i-have-and-quick-dinners

2026-10-09 08:58:42 -04:00

Author	SHA1	Message	Date
dev_agentandClaude Opus 5.5	c28d55681c	Keep Quick dinners start failures and adds across tab switches CI / ci (push) Successful in 6m7s Details CI / ci (pull_request) Successful in 5m50s Details A search that could not start is now the tab's startError in the per-tab cache, set by the mutation's own onError, so it survives the panel unmounting. The first page is no longer asked for again by itself, and the ErrorBanner with Retry stays until Retry clears it. An add to the Quest log now marks the row added from the mutation's own onSuccess, which runs even when the row has unmounted, so the check is there when the tab is shown again. Review findings F1 and F2 on PR #152; task db934d36-f554-41ef-9061-5f100a0b6452. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-09 08:09:08 -04:00
dev_agentandClaude Opus 5.5	60b90323a5	Add the Quick dinners screen (1j) (Feature 18) CI / ci (push) Successful in 6m31s Details CI / ci (pull_request) Successful in 5m46s Details /quick now renders mock 1j: a grape zap header, Crock pot \| 30 min or less tabs with a helper line each, and rows of grounded quick_ideas (64 px washed photo, Bagel name, "25 min · Medium" or "Crock pot · 6 hr · Easy", the time left off when the recipe has none) with a teal "+" that adds the idea to the Quest log and becomes a check. Each tab is its own POST /api/v1/ideas/quick search, polled with useJob and filled as the server grounds ideas. A tab's pages, the job finding its next page and the ideas added are kept in the query cache for the session, so switching tabs or leaving the screen keeps them. "Show me more" asks for the same kind excluding every name shown; no_ideas_found on a later page ends the tab honestly. Failures use the ErrorBanner and Retry, as Cook from what I have does. The App bootstrap tests that used /quick as a placeholder route now use /settings/notifications. Maestro task db934d36-f554-41ef-9061-5f100a0b6452. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-09 07:53:57 -04:00

Author

SHA1

Message

Date

dev_agentandClaude Opus 5.5

c28d55681c

Keep Quick dinners start failures and adds across tab switches

CI / ci (push) Successful in 6m7s

Details

CI / ci (pull_request) Successful in 5m50s

Details

A search that could not start is now the tab's startError in the per-tab
cache, set by the mutation's own onError, so it survives the panel
unmounting. The first page is no longer asked for again by itself, and
the ErrorBanner with Retry stays until Retry clears it.

An add to the Quest log now marks the row added from the mutation's own
onSuccess, which runs even when the row has unmounted, so the check is
there when the tab is shown again.

Review findings F1 and F2 on PR #152; task db934d36-f554-41ef-9061-5f100a0b6452.

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

2026-10-09 08:09:08 -04:00

dev_agentandClaude Opus 5.5

60b90323a5

Add the Quick dinners screen (1j) (Feature 18)

CI / ci (push) Successful in 6m31s

Details

CI / ci (pull_request) Successful in 5m46s

Details

/quick now renders mock 1j: a grape zap header, Crock pot | 30 min or
less tabs with a helper line each, and rows of grounded quick_ideas
(64 px washed photo, Bagel name, "25 min · Medium" or "Crock pot · 6 hr
· Easy", the time left off when the recipe has none) with a teal "+"
that adds the idea to the Quest log and becomes a check.

Each tab is its own POST /api/v1/ideas/quick search, polled with useJob
and filled as the server grounds ideas. A tab's pages, the job finding
its next page and the ideas added are kept in the query cache for the
session, so switching tabs or leaving the screen keeps them. "Show me
more" asks for the same kind excluding every name shown; no_ideas_found
on a later page ends the tab honestly. Failures use the ErrorBanner and
Retry, as Cook from what I have does.

The App bootstrap tests that used /quick as a placeholder route now use
/settings/notifications.

Maestro task db934d36-f554-41ef-9061-5f100a0b6452.

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

2026-10-09 07:53:57 -04:00