From 7652bbba9c88f7f219da44c7f07a20eec09aa209 Mon Sep 17 00:00:00 2001 From: dave Date: Sat, 28 Mar 2026 09:50:07 +0000 Subject: [PATCH] storkit: done 423_story_auto_schedule_timer_on_rate_limit_to_resume_after_reset --- ...mer_on_rate_limit_to_resume_after_reset.md | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 .storkit/work/5_done/423_story_auto_schedule_timer_on_rate_limit_to_resume_after_reset.md diff --git a/.storkit/work/5_done/423_story_auto_schedule_timer_on_rate_limit_to_resume_after_reset.md b/.storkit/work/5_done/423_story_auto_schedule_timer_on_rate_limit_to_resume_after_reset.md new file mode 100644 index 00000000..80a9aa9c --- /dev/null +++ b/.storkit/work/5_done/423_story_auto_schedule_timer_on_rate_limit_to_resume_after_reset.md @@ -0,0 +1,22 @@ +--- +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