story-kit: create 295_bug_stories_stuck_in_qa_when_qa_agent_is_busy

.story_kit/work/1_backlog/294_story_rename_app_title_from_story_kit_to_storkit.md

@@ -1,18 +0,0 @@
----
-name: "Rename app title from Story Kit to Storkit"
----
-
-# Story 294: Rename app title from Story Kit to Storkit
-
-## User Story
-
-As a user, I want the application title to say "Storkit" instead of "Story Kit", so that the branding reflects the new name.
-
-## Acceptance Criteria
-
-- [ ] The top title in the web UI header displays "Storkit" instead of "Story Kit"
-- [ ] Any other visible references to "Story Kit" in the UI are updated to "Storkit"
-
-## Out of Scope
-
-- TBD

.story_kit/work/1_backlog/295_bug_stories_stuck_in_qa_when_qa_agent_is_busy.md

@@ -0,0 +1,30 @@
+---
+name: "Stories stuck in QA when QA agent is busy"
+---
+
+# Bug 295: Stories stuck in QA when QA agent is busy
+
+## Description
+
+When multiple stories pass coding gates simultaneously and move to QA, only the first one gets a QA agent assigned. The others fail with "Agent 'qa' is already running" and are never retried when the QA agent becomes free. Stories get stuck in QA with no agent indefinitely.
+
+## How to Reproduce
+
+1. Have 3 stories in current with coders running
+2. All 3 coders finish within seconds of each other
+3. Server tries to start QA agent on all 3 — first succeeds, other 2 fail
+4. After first QA completes, the other 2 stories remain in QA with no agent
+
+## Actual Result
+
+Stories 293 and 294 stuck in QA with no agent after 292's QA agent was busy.
+
+## Expected Result
+
+When a QA agent finishes a story, auto-assign should check for other stories waiting in QA and pick them up.
+
+## Acceptance Criteria
+
+- [ ] When an agent completes, auto-assign scans for unassigned stories in all active stages and assigns free agents
+- [ ] Stories that failed agent assignment due to busy agents are retried when agents become available
+- [ ] Server logs when a story is queued for retry vs permanently failed