From 05db012aafd1cf831951c27b83aee87d7c24a28f Mon Sep 17 00:00:00 2001 From: dave Date: Sat, 28 Mar 2026 09:08:02 +0000 Subject: [PATCH] storkit: done 422_story_unblock_command_to_reset_blocked_stories --- ...mer_on_rate_limit_to_resume_after_reset.md | 22 ------------------- ...nblock_command_to_reset_blocked_stories.md | 22 +++++++++++++++++++ 2 files changed, 22 insertions(+), 22 deletions(-) delete mode 100644 .storkit/work/1_backlog/423_story_auto_schedule_timer_on_rate_limit_to_resume_after_reset.md create mode 100644 .storkit/work/5_done/422_story_unblock_command_to_reset_blocked_stories.md diff --git a/.storkit/work/1_backlog/423_story_auto_schedule_timer_on_rate_limit_to_resume_after_reset.md b/.storkit/work/1_backlog/423_story_auto_schedule_timer_on_rate_limit_to_resume_after_reset.md deleted file mode 100644 index 80a9aa9c..00000000 --- a/.storkit/work/1_backlog/423_story_auto_schedule_timer_on_rate_limit_to_resume_after_reset.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -name: "Auto-schedule timer on rate limit to resume after reset" ---- - -# Story 423: Auto-schedule timer on rate limit to resume after reset - -## User Story - -As a ..., I want ..., so that ... - -## Acceptance Criteria - -- [ ] When a rate_limit_event with a hard block (not just allowed_warning) is received from the PTY stream, parse the reset time from rate_limit_info -- [ ] Automatically create a timer (via TimerStore from story 421) for the blocked story at the parsed reset time -- [ ] If a timer already exists for that story, update it to the later reset time rather than creating a duplicate -- [ ] Log the auto-scheduled timer with story ID, agent name, and scheduled resume time -- [ ] Notify chat transports that the story was rate-limited and will auto-resume at the scheduled time -- [ ] When the timer fires and restarts the agent, the existing worktree and committed work are preserved - -## Out of Scope - -- TBD diff --git a/.storkit/work/5_done/422_story_unblock_command_to_reset_blocked_stories.md b/.storkit/work/5_done/422_story_unblock_command_to_reset_blocked_stories.md new file mode 100644 index 00000000..66e4bef1 --- /dev/null +++ b/.storkit/work/5_done/422_story_unblock_command_to_reset_blocked_stories.md @@ -0,0 +1,22 @@ +--- +name: "Unblock command to reset blocked stories" +--- + +# Story 422: Unblock command to reset blocked stories + +## User Story + +As a ..., I want ..., so that ... + +## Acceptance Criteria + +- [ ] Bot command `unblock ` clears blocked flag and resets retry_count to 0 on the story front matter +- [ ] Replies with confirmation including story ID and name +- [ ] Returns clear error if story is not found or not blocked +- [ ] Works from all transports (Matrix, WhatsApp, Slack) +- [ ] Exposed as an MCP tool so agents can unblock stories programmatically +- [ ] Works as a slash command in the web UI + +## Out of Scope + +- TBD