diff --git a/.story_kit/work/1_upcoming/4_bug_run_button_does_not_start_agent.md b/.story_kit/work/1_upcoming/4_bug_run_button_does_not_start_agent.md
deleted file mode 100644
index f0c288b..0000000
--- a/.story_kit/work/1_upcoming/4_bug_run_button_does_not_start_agent.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-name: Run button does not start agent
----
-
-# Bug 4: Run Button Does Not Start Agent
-
-## Symptom
-
-Clicking the "Run" button in the AgentPanel does not visibly start an agent. No feedback is shown to the user.
-
-## Root Cause
-
-When multiple agents are configured in `project.toml` (e.g. supervisor, coder-1, coder-2), `handleRunClick` shows a role-selector dropdown instead of starting an agent directly. The dropdown may not be visible due to layout/positioning issues, or the click handler may be swallowed.
-
-## Reproduction Steps
-
-1. Start the server and open the web UI
-2. Expand a story in the Agent panel
-3. Click the "Run" button
-4. Observe: nothing visible happens (no agent starts, no dropdown appears)
-
-## Proposed Fix
-
-Investigate whether the role-selector dropdown is rendering but hidden (z-index, overflow, positioning), or whether the click event is not reaching `handleRunClick`. If the dropdown is the issue, consider starting the default agent directly and offering role selection separately.