storkit: done 421_story_timer_command_for_deferred_agent_start
This commit is contained in:
@@ -0,0 +1,24 @@
|
||||
---
|
||||
name: "Timer command for deferred agent start"
|
||||
---
|
||||
|
||||
# Story 421: Timer command for deferred agent start
|
||||
|
||||
## User Story
|
||||
|
||||
As a ..., I want ..., so that ...
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ] Bot command `timer <story_id> <HH:MM>` schedules a one-shot deferred start for the given story at the next occurrence of that time (server-local timezone)
|
||||
- [ ] Bot command `timer list` shows all pending timers with story ID and scheduled time
|
||||
- [ ] Bot command `timer cancel <story_id>` removes the pending timer for that story
|
||||
- [ ] Timers are persisted to .storkit/timers.json so they survive server restarts
|
||||
- [ ] A 30s tick loop (tokio task, same pattern as watchdog) checks for due timers and calls start_agent when triggered
|
||||
- [ ] When a timer fires, the story must already be in current — timer does not move stories between stages
|
||||
- [ ] Fired timers are removed after execution (one-shot, not recurring)
|
||||
- [ ] Multiple timers for the same time are supported and respect agent slot contention via auto-assign
|
||||
|
||||
## Out of Scope
|
||||
|
||||
- TBD
|
||||
Reference in New Issue
Block a user