7 Commits

Include renames

Author	SHA1	Message	Date
dev_agentandClaude Opus 5.5	1dd53767f7	Guard recipe repairs against same-normalized renames and member edits ... F1-1: GroundDinner also compares the observed raw name, so renaming "Grandma's stew" to "Easy Grandma's stew" (same normalized_name) while a link is grounding is ErrGroundConflict, not attached to the renamed dinner. F1-2: A method, minutes_total or difficulty no longer as observed before grounding is kept over the recipe's value, as GroundPendingDinner keeps values a member set while a dinner was pending. F2-1: Failing to record a grounded candidate or link on the dinner (or to read it back after a rejected write) wraps ErrGroundFailed, so the API logs reason=ground_failed with the dinner id, never the database error. Maestro task 8741cedb-1849-4e3f-8d05-f5648c77c7ee. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-06 20:11:32 -04:00
dev_agentandClaude Opus 5.5	5c4c507ee6	Make recipe repairs conditional and keep pasted links out of logs ... F1: A candidate or link repair now writes the dinner only if it is still unarchived and as observed before grounding (normalized_name, grounding_status, grounding_revision and recipe_id). A dinner renamed or grounded some other way meanwhile is ErrGroundConflict (409 ground_conflict); one archived, before or during the repair, is ErrArchived (409 dinner_archived). Manual repairs reject archived dinners too. F2: Any failure grounding a candidate or link by hand wraps ErrGroundFailed, which the API logs as reason=ground_failed with the dinner id only, never the pasted link or dependency error text. GroundURL no longer formats the link into its error. Maestro task 8741cedb-1849-4e3f-8d05-f5648c77c7ee. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-06 20:03:05 -04:00
orchestrator-agent	cc7875c76c	Integration fix: Feature 12 feature-review findings F1-F8 (#95) ... Co-authored-by: orchestrator-agent <20+orchestrator-agent@code.cubecraftcreations.com>	2026-10-06 19:54:47 -04:00
dev_agentandClaude Opus 5.5	171c9c2d11	Fix stale Regular grounding and enforce three Regulars for onboarding ... A background grounding result now applies only while the dinner is still pending under the normalized name the job searched: GroundPendingDinner and FailPendingDinnerGrounding match normalized_name, so a rename makes the old job's success or failure a no-op. Renaming a dinner still pending enqueues a fresh grounding job for the new name; if that cannot be enqueued, the dinner's grounding is failed so it is not left pending with no job. Completing onboarding (PATCH /api/v1/settings/household with onboarding_completed true) is refused with 400 invalid_settings until the household has at least three Regulars (status regular; archived and Quest log dinners do not count), and onboarding_completed_at is set only then. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-06 18:47:41 -04:00
dev_agent	423b898f54	Background grounding and recipe fix-up API (#90) ... Co-authored-by: dev_agent <dev_agent@cubecraftlabs.com>	2026-10-06 16:39:10 -04:00
dev_agent	729c5bd0fe	Dinners API for Regulars (#89) ... Co-authored-by: dev_agent <dev_agent@cubecraftlabs.com>	2026-10-06 15:57:13 -04:00
dev_agent	17a69f4de7	Feature 02 task 4: sqlc configuration and core queries (#13) ... Co-authored-by: dev_agent <dev_agent@cubecraftlabs.com> Co-committed-by: dev_agent <dev_agent@cubecraftlabs.com>	2026-10-03 09:15:40 -04:00