4 Commits

Include renames

Author	SHA1	Message	Date
dev_agentandClaude Opus 5.5	d5cd47a775	Retry a job's final status write until it lands ... A worker whose final SucceedJob or FailJob write failed logged it and moved on, leaving the job running. For a suggestion batch whose own end write had also failed, both rows stayed running, so orphan reconciliation kept treating the batch as active and it blocked manual and replenish batches until a restart. The runner now retries the final write with the claim backoff until it lands; on shutdown a failed attempt is left for the next Start to fail as interrupted. Document that orphaned batches are reconciled each time a batch is started, before the active batch is selected, not at boot. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-07 00:12:52 -04:00
dev_agentandClaude Opus 5.5	a6643aaa94	Fail the batch job when recording its end fails, and reconcile orphans ... finishBatch now returns its error, and treats a batch that is no longer running as one, so a batch job never ends succeeded with its batch still running. A batch left pending or running with its job ended (process stopped, or the final status write failed) is failed inside startBatch, before the active batch is read, so it never blocks a manual or replenish batch. This replaces the boot-only FailInterruptedBatches. Document suggestions.name in the architecture schema summary. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-06 23:59:40 -04:00
dev_agentandClaude Opus 5.5	4e2773703b	Keep Pass history immutable and replenish atomic with decisions ... Fixes the three review findings on 50399b6 (pull request #102): - A batch now rereads every declined name inside its storing transaction, so a Pass committed after the batch read its input but before it stores can no longer let the passed dish into the deck (SQ-01). - A decision that leaves the deck under five creates the replenish batch and its job in the decision's own transaction, so a decision is never recorded without the replenish it calls for; when they cannot be written, neither is the decision, and a retry decides again (SQ-02). StartBatch commits the batch with its job the same way, replacing the mutex and the fail-on-enqueue cleanup. jobs gains Kind.EnqueueTx and Kind.Wake for this. - Migration 0012 gives each suggestion the name its dish was suggested under; declined names for batches and the household context's passed list read it instead of the dinner's mutable name, so renaming a passed dinner no longer erases it from dedupe (SQ-03). Task: b4f2558c-227f-4627-852b-be5aa190242a Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-06 23:47:45 -04:00
dev_agentandClaude Opus 5.5	50399b6329	Add Side quest suggestion batches, deck and Try it / Pass API ... POST /api/v1/suggestions/batches enqueues a suggestion_batch job that runs suggest_side_quests through the harness, grounds the survivors with recipes.Grounder.GroundMany (dropping those no recipe grounds) and stores each as a dinner (status suggested, origin side_quest) with a pending suggestion holding its reason and cited_regular_ids. Only one batch is pending or running at a time; a POST while one is active returns it. GET /api/v1/suggestions/deck lists pending suggestions oldest first with the dinner's name, photo, difficulty and the reason. POST /api/v1/suggestions/{id}/accept moves the dinner to the Quest log; /decline records the Pass and archives the dinner, whose name every later batch reads as declined. Both are idempotent and 409 on the opposite decision. A decision leaving fewer than 5 in the deck starts a replenish batch unless one is already pending or running. Batches left unfinished by a restart are failed at boot so they never block the next. Task: b4f2558c-227f-4627-852b-be5aa190242a Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-06 23:28:11 -04:00