4 Commits

Include renames

Author	SHA1	Message	Date
dev_agentandClaude Opus 5.5	1f548c9f1d	Refuse draft_week jobs on the generic jobs endpoint ... A kind can now be made service-only: Runner.Enqueue, and so POST /api/v1/jobs, refuses it with 400 service_only_kind, and only its typed Kind enqueues it. draft_week is service-only, so StartDraft and its one-draft-in-flight-per-week rule is the only way to start a draft; a confirmed draft_week posted to /api/v1/jobs can no longer run beside the week's unconfirmed draft. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-07 06:57:53 -04:00
dev_agentandClaude Opus 5.5	45fcd71d27	Keep one draft in flight per week ... A confirmed draft asked for while the week's draft job was asked for without confirm no longer enqueues a second job. With two job workers the two drafts ran at once, and whichever stored second failed plan_changed, so the household's confirmed draft could fail. StartDraft now refuses it with ErrDraftRunning, 409 draft_running, and enqueues nothing; the household asks again once the running draft finishes. Every other draft joins the week's queued or running job, so a week has at most one. The plan tests run the job runner with two workers, as cmd/server does, and a confirmed draft during a running unconfirmed one is refused while only the running job drafts. Maestro task ea48e650-d510-49cc-8485-0f07174ee731. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-07 06:46:13 -04:00
dev_agentandClaude Opus 5.5	7e6e49f6b1	Guard plan drafts against swaps and keep confirm on single-flight ... Return the draft job id as jobId, as the plan API contract specifies. Add a week_plans revision (migration 0013) that every swap and stored draft raises. A draft_week job reads the revision before draft_week runs and stores its week only while the plan still has it; a plan edited while the AI ran is left as it is and the job fails plan_changed, so a draft never erases the household's swap. A confirmed draft now joins only a confirmed queued or running job, so a job asked for without confirm can no longer fail it with confirm_required after the plan was synced. Test simultaneous drafts, a swap during a draft, a confirmed draft while an unconfirmed one runs, impossible calendar dates and start_by across the end of daylight saving time. Maestro task ea48e650-d510-49cc-8485-0f07174ee731. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-07 06:32:51 -04:00
dev_agentandClaude Opus 5.5	75d6ad4e19	Add plan service and weekly plan API ... Add internal/plan: a draft_week job that drafts the week through the harness from every Regular and the Quest log dinners no other current or later plan holds, given the household context and last week's dinners, and stores it as the week's plan; plan reads with the week label, is_new and each crock-pot dinner's start_by (dinner time minus minutes_total, computed on read); and day swaps that recompute is_new and move a synced plan to changed. Drafting over a synced or changed plan needs confirm, at enqueue and again when the job stores the week; a redraft keeps each day's calendar event id. Serve GET /api/v1/plans/{weekStart}, POST /api/v1/plans/{weekStart}/draft (202 {job_id}, single-flight per week) and PUT /api/v1/plans/{weekStart}/days/{date}; a weekStart that is not a Monday is 400 invalid_week. Maestro task ea48e650-d510-49cc-8485-0f07174ee731. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-07 06:18:09 -04:00