storkit: done 464_bug_timer_rejects_backlog_stories_should_move_to_current_on_fire

.storkit/work/5_done/464_bug_timer_rejects_backlog_stories_should_move_to_current_on_fire.md

@@ -0,0 +1,33 @@
+---
+name: "Timer rejects backlog stories — should move to current on fire"
+---
+
+# Bug 464: Timer rejects backlog stories — should move to current on fire
+
+## Description
+
+The `timer` bot command requires stories to be in `work/2_current/` before scheduling. When a user tries to schedule a backlog story (e.g. `timer 463 12:45`), it returns:
+
+"Story **463_story_...** is not in `work/2_current/`. Move it to current before scheduling a timer."
+
+The timer should accept backlog stories. When the timer fires, it should move the story from backlog to current and let auto-assign start an agent.
+
+## How to Reproduce
+
+1. Have a story in backlog (e.g. 463)
+2. Run `timer 463 12:45`
+3. Observe rejection message
+
+## Actual Result
+
+Timer command rejects stories not in `work/2_current/`.
+
+## Expected Result
+
+Timer command accepts backlog stories. When the timer fires, it moves the story to current and auto-assign picks it up.
+
+## Acceptance Criteria
+
+- [ ] Timer bot command accepts stories in backlog or current
+- [ ] Timer tick loop calls move_story_to_current before start_agent for backlog stories
+- [ ] Unit tests cover scheduling and firing for backlog stories