ideas_from_ingredients skill and job (Feature 18) #144

Merged

approver_agent merged 3 commits from task/ideas-from-ingredients_c3c5f98e-7f7d-4c6b-a1ab-d45bb8e497f9 into feature/640e946c-3280-430a-b1f0-025d4643fd29-cook-from-what-i-have-and-quick-dinners

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

Author	SHA1	Message	Date
dev_agentandClaude Opus 5.5	9ed6c305cb	Never show ideas for a failed ideas job, however it failed CI / ci (push) Successful in 5m34s Details CI / ci (pull_request) Successful in 5m26s Details A failed ideas_from_ingredients job could still show ideas through GET /api/v1/jobs/{id}: a job failed at boot as interrupted by restart keeps its last partial result, and when the write clearing the ideas itself failed the runner recorded internal_error over the uncleared result. Neither path can be fixed by a write. The jobs package gains an opt-in per-kind hook, Kind.FailedResult, which Runner.Get applies to a failed job's stored result on every read. The ideas kind registers withoutIdeas, which empties the ideas and keeps the rest of the result. Kinds that do not call FailedResult are unchanged. The write-side clear stays as a tidy-up of what is stored. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-08 19:36:04 -04:00
dev_agentandClaude Opus 5.5	4146f31275	Fail empty ideas jobs, clear ideas on failure, show each idea as it grounds CI / ci (pull_request) Successful in 6m11s Details CI / ci (push) Successful in 5m24s Details - A run that keeps no idea fails with no_ideas_found instead of ending done with an empty list. - Before an ideas job fails it republishes its result with no ideas, so GET /api/v1/jobs/{id} never shows ideas on a failed job, even ones a previous grounding round already published. - Each idea is published as soon as its grounding finishes, placed in the model's order. recipes.GroundEach reports items as they finish; GroundMany is rebuilt on it with unchanged semantics. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-08 19:22:51 -04:00
dev_agentandClaude Opus 5.5	b566be7ddc	Add ideas_from_ingredients skill and job CI / ci (push) Successful in 5m51s Details CI / ci (pull_request) Successful in 5m45s Details Implement the ideas_from_ingredients v1 skill on the AI harness: it asks for 8 ideas {name, uses[], missing[], est_minutes, method, difficulty, search_query}, keeps only "uses" entries whose harness.Normalize form is one of the household's listed ingredients (written as the household wrote them, in its order), drops ideas using none or repeating another, and computes the summary line from the corrected lists. Add internal/ideas: an ideas_from_ingredients job that grounds the ideas with Grounder.GroundMany in the model's order until 5 are kept, drops the ungroundable ones and, for quick_only, those whose grounded recipe is not a Quick dinner (crockpot or minutes_total <= 30), publishing the result as each idea is kept. POST /api/v1/ideas/from-ingredients answers 202 {jobId}. Maestro task c3c5f98e-7f7d-4c6b-a1ab-d45bb8e497f9. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-08 19:01:03 -04:00

Author

SHA1

Message

Date

dev_agentandClaude Opus 5.5

9ed6c305cb

Never show ideas for a failed ideas job, however it failed

CI / ci (push) Successful in 5m34s

Details

CI / ci (pull_request) Successful in 5m26s

Details

A failed ideas_from_ingredients job could still show ideas through
GET /api/v1/jobs/{id}: a job failed at boot as interrupted by restart
keeps its last partial result, and when the write clearing the ideas
itself failed the runner recorded internal_error over the uncleared
result. Neither path can be fixed by a write.

The jobs package gains an opt-in per-kind hook, Kind.FailedResult,
which Runner.Get applies to a failed job's stored result on every read.
The ideas kind registers withoutIdeas, which empties the ideas and keeps
the rest of the result. Kinds that do not call FailedResult are
unchanged. The write-side clear stays as a tidy-up of what is stored.

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

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

dev_agentandClaude Opus 5.5

4146f31275

Fail empty ideas jobs, clear ideas on failure, show each idea as it grounds

CI / ci (pull_request) Successful in 6m11s

Details

CI / ci (push) Successful in 5m24s

Details

- A run that keeps no idea fails with no_ideas_found instead of ending
  done with an empty list.
- Before an ideas job fails it republishes its result with no ideas, so
  GET /api/v1/jobs/{id} never shows ideas on a failed job, even ones a
  previous grounding round already published.
- Each idea is published as soon as its grounding finishes, placed in the
  model's order. recipes.GroundEach reports items as they finish;
  GroundMany is rebuilt on it with unchanged semantics.

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

2026-10-08 19:22:51 -04:00

dev_agentandClaude Opus 5.5

b566be7ddc

Add ideas_from_ingredients skill and job

CI / ci (push) Successful in 5m51s

Details

CI / ci (pull_request) Successful in 5m45s

Details

Implement the ideas_from_ingredients v1 skill on the AI harness: it asks
for 8 ideas {name, uses[], missing[], est_minutes, method, difficulty,
search_query}, keeps only "uses" entries whose harness.Normalize form is
one of the household's listed ingredients (written as the household wrote
them, in its order), drops ideas using none or repeating another, and
computes the summary line from the corrected lists.

Add internal/ideas: an ideas_from_ingredients job that grounds the ideas
with Grounder.GroundMany in the model's order until 5 are kept, drops the
ungroundable ones and, for quick_only, those whose grounded recipe is not
a Quick dinner (crockpot or minutes_total <= 30), publishing the result
as each idea is kept. POST /api/v1/ideas/from-ingredients answers 202
{jobId}.

Maestro task c3c5f98e-7f7d-4c6b-a1ab-d45bb8e497f9.

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

2026-10-08 19:01:03 -04:00