6 Commits

Include renames

Author	SHA1	Message	Date
dev_agentandClaude Opus 5.5	f95a31472b	Bound the suggestion batch's end write like a job's final write ... runBatch recorded the batch's end with an uncancellable context and no deadline, before its handler returned, so a writer connection that stayed busy could hold the worker, and shutdown, open indefinitely. jobs.FinalWriteContext now gives every final write one bounded attempt context (FinalWriteTimeout, 5 seconds, not cancelled with ctx); the runner's record and finishBatch both use it. On timeout at shutdown the handler returns, the job and batch stay running, the next Start fails the job as interrupted and the next StartBatch fails the orphaned batch. TestBlockedBatchEndDoesNotHoldShutdown holds the writer while a batch reaches finishBatch and asserts the worker stops within the bound and the batch is reconciled after restart. TestBlockedFinalWriteDoesNotHoldShutdown no longer sets a runner field, so it compiles against earlier heads. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-07 00:40:52 -04:00
dev_agentandClaude Opus 5.5	76ec60d219	Bound each attempt at a job's final write ... A final write used a context that could never be cancelled, so a worker waiting for a held writer connection kept runner.Wait, and with it shutdown, open indefinitely. Each attempt now has a 5-second deadline; once shutdown begins, a failed or timed-out attempt is not retried and the next start fails the job as interrupted. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-07 00:29:28 -04:00
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	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_agent	bba9033ac5	Feature 04 integration fix: authenticated job enqueue API and progressive HTTP flow (#31) ... Co-authored-by: dev_agent <dev_agent@cubecraftlabs.com> Co-committed-by: dev_agent <dev_agent@cubecraftlabs.com>	2026-10-03 15:46:19 -04:00
dev_agent	e050736178	Feature 04 task 5: Async job runner and GET /api/v1/jobs/{id} (#29) ... Co-authored-by: dev_agent <dev_agent@cubecraftlabs.com> Co-committed-by: dev_agent <dev_agent@cubecraftlabs.com>	2026-10-03 15:24:01 -04:00