fix: unblock_task returns to todo and clears stale claims#25
Merged
Conversation
unblock_task checked started_at to decide status, always returning to in_progress for tasks that had been worked on. It also preserved stale claim fields, which suppressed the task.next trigger's claim guard. Now always returns to todo and clears claim_owner/lease so the task.next event fires and workers can pick up the task. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
unblock_tasknow always transitions totodoinstead of checkingstarted_atto decide betweenin_progress/todoclaim_owner,claim_claimed_at,claim_lease_expires_at) on unblock so thetask.nextSQLite trigger fires correctlytask.nextevent was emittedRoot cause
unblock_taskcheckedstarted_at.is_some()to decide the target status. Since agents setstarted_atwhen they begin work, unblocking always returned toin_progress. Additionally, stale claim fields were preserved, so even manually cycling throughdraft → todocouldn't triggertask.next— the trigger's claim guard suppressed it:✻ Clauded...