Cook from what I have screen (1i) (Feature 18, task 4)
Maestro task 62f7cfea-625a-464c-9941-62a897b8f693. The ingredients-on-hand screen: chip field with removable chips and an "Add ingredient…" input (Enter or comma adds), an "Any time | Quick only" segmented control and a dark "Find ideas" button disabled with fewer than one ingredient, skeleton cards that fill progressively while the job runs, and result cards carrying the server-computed summary line ("Uses all 5 · missing: 1 lime") with "Cook tonight" and "Add to Quest log".
"Quick only" re-requests with quick_only rather than filtering client-side — the quick definition is enforced in Go. A failed job shows the error banner with Retry and never placeholder ideas. "Cook tonight" turning the server's 409 no_plan into a "Plan this week" affordance is the case the next screen relies on.
Notes the developer left for the Quick dinners screen (1j): the add-to-Quest-log and cook-tonight hooks work for any ideas job; 1j needs its own result parser and job kind (quick_ideas carries kind, exclude, ideas, dropped and no summary line); quick_ideas keeps up to 6 ideas so its skeleton count differs; "Show me more" posts the names already shown as exclude and polls with the same hook; and the failure messages plus the 404-means-start-again rule currently live in this screen and would be worth sharing.
The developer reports typecheck, tests and build passing; no Go file changed.
## Cook from what I have screen (1i) (Feature 18, task 4)
Maestro task `62f7cfea-625a-464c-9941-62a897b8f693`. The ingredients-on-hand screen: chip field with removable chips and an "Add ingredient…" input (Enter or comma adds), an "Any time | Quick only" segmented control and a dark "Find ideas" button disabled with fewer than one ingredient, skeleton cards that fill progressively while the job runs, and result cards carrying the server-computed summary line ("Uses all 5 · missing: 1 lime") with "Cook tonight" and "Add to Quest log".
"Quick only" re-requests with `quick_only` rather than filtering client-side — the quick definition is enforced in Go. A failed job shows the error banner with Retry and never placeholder ideas. "Cook tonight" turning the server's 409 `no_plan` into a "Plan this week" affordance is the case the next screen relies on.
**Notes the developer left for the Quick dinners screen (1j):** the add-to-Quest-log and cook-tonight hooks work for any ideas job; 1j needs its own result parser and job kind (`quick_ideas` carries `kind`, `exclude`, `ideas`, `dropped` and no summary line); `quick_ideas` keeps up to 6 ideas so its skeleton count differs; "Show me more" posts the names already shown as `exclude` and polls with the same hook; and the failure messages plus the 404-means-start-again rule currently live in this screen and would be worth sharing.
The developer reports typecheck, tests and build passing; no Go file changed.
/cook-from-pantry lists the ingredients on hand as removable chips
(Enter or a comma adds one), with Any time | Quick only and a dark Find
ideas button. Find ideas starts an ideas_from_ingredients job and polls
it through useJob, showing ideas as the server grounds them with
skeleton cards for those still to come. Changing the filter after a
search asks the server again.
Each result card shows the server's summary line and its own Cook
tonight and Add to Quest log actions, enabled once the job has
succeeded; a 409 no_plan offers "Plan this week" linking to /plan.
Start failures, failed jobs, unknown jobs and unreadable results show
the ErrorBanner with Retry; no_ideas_found shows an empty state.
parsePlan is exported so Cook tonight can cache the plan it answers.
Maestro task 62f7cfea-625a-464c-9941-62a897b8f693.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A failed ideas job always shows the ErrorBanner with Retry and no cards,
no_ideas_found included. The failure messages and the 404-means-search-
again rule move to ideas/api.ts (ideasJobFailure, ideasJobLost) for the
Quick dinners screen to share.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Cook from what I have screen (1i) (Feature 18, task 4)
Maestro task
62f7cfea-625a-464c-9941-62a897b8f693. The ingredients-on-hand screen: chip field with removable chips and an "Add ingredient…" input (Enter or comma adds), an "Any time | Quick only" segmented control and a dark "Find ideas" button disabled with fewer than one ingredient, skeleton cards that fill progressively while the job runs, and result cards carrying the server-computed summary line ("Uses all 5 · missing: 1 lime") with "Cook tonight" and "Add to Quest log"."Quick only" re-requests with
quick_onlyrather than filtering client-side — the quick definition is enforced in Go. A failed job shows the error banner with Retry and never placeholder ideas. "Cook tonight" turning the server's 409no_planinto a "Plan this week" affordance is the case the next screen relies on.Notes the developer left for the Quick dinners screen (1j): the add-to-Quest-log and cook-tonight hooks work for any ideas job; 1j needs its own result parser and job kind (
quick_ideascarrieskind,exclude,ideas,droppedand no summary line);quick_ideaskeeps up to 6 ideas so its skeleton count differs; "Show me more" posts the names already shown asexcludeand polls with the same hook; and the failure messages plus the 404-means-start-again rule currently live in this screen and would be worth sharing.The developer reports typecheck, tests and build passing; no Go file changed.
Independent Codex gpt-6-sol review: CHANGES_REQUIRED for this exact commit.
Independent Codex gpt-6-sol review: APPROVED for this exact commit.