Accept story 50: migrate to unified .story_kit/current/, add stories 55-59

- Move stories/current/ → .story_kit/current/
- Archive story 50
- Add story 55: Live Story Panel Updates
- Add story 57: Live Test Gate Updates
- Add story 58: Live Agent Panel Updates
- Add story 59: Current Work Panel

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

.story_kit/stories/current/49_deterministic_bug_lifecycle_management.md

@@ -1,25 +0,0 @@
----
-name: Deterministic Bug Lifecycle Management
-test_plan: pending
----
-
-# Story 49: Deterministic Bug Lifecycle Management
-
-## User Story
-
-As a developer running autonomous agents, I want all bug file mutations to happen through server MCP/REST tools that auto-commit to master, so that the bug tracker is always consistent, always committed, and agents never edit bug files directly.
-
-## Acceptance Criteria
-
-- [ ] New MCP tool `create_bug(name, description, steps_to_reproduce, actual_result, expected_result, acceptance_criteria)` creates a bug file in `.story_kit/bugs/` with a deterministic filename and auto-commits to master
-- [ ] Bug file template includes sections: Description, How to Reproduce, Actual Result, Expected Result, Acceptance Criteria
-- [ ] New MCP tool `list_bugs()` returns all open bugs (files in `.story_kit/bugs/` excluding `archive/`)
-- [ ] New MCP tool `close_bug(bug_id)` moves a bug from `.story_kit/bugs/` to `.story_kit/bugs/archive/` and auto-commits to master
-- [ ] `start_agent` supports bug IDs (e.g. `bug-5-description`) — no move needed since bugs don't have upcoming/current
-- [ ] All auto-commits use deterministic commit messages (e.g. "story-kit: create bug bug-6-fix-foo", "story-kit: close bug bug-5")
-- [ ] Agents never need to edit bug markdown files directly — all mutations go through server tools
-
-## Out of Scope
-
-- Bug severity/priority fields (can be a follow-up)
-- Linking bugs to stories

.story_kit/stories/current/50_unified_current_work_directory.md

@@ -1,30 +0,0 @@
----
-name: Unified Current Work Directory
-test_plan: approved
----
-
-# Story 50: Unified Current Work Directory
-
-## User Story
-
-As a developer, I want a single `.story_kit/current/` directory (outside of `stories/`) that holds whatever work items agents are actively working on — stories, bugs, or spikes — so I can always see at a glance what coders are doing.
-
-## Acceptance Criteria
-
-- [ ] New top-level `.story_kit/current/` directory replaces `.story_kit/stories/current/`
-- [ ] `start_agent` moves work items into `.story_kit/current/` regardless of type (story, bug, spike)
-- [ ] `accept_story` moves from `.story_kit/current/` to `.story_kit/stories/archived/`
-- [ ] `close_bug` moves from `.story_kit/current/` to `.story_kit/bugs/archive/`
-- [ ] All existing references to `.story_kit/stories/current/` are updated (server code, tests, MCP tools)
-- [ ] Migrate any files currently in `.story_kit/stories/current/` to `.story_kit/current/`
-- [ ] Auto-commits use deterministic messages for all moves
-- [ ] Integration test: full story lifecycle — create_story → start_agent (moves to current/) → check_criterion → accept_story (moves to stories/archived/)
-- [ ] Integration test: full bug lifecycle — create_bug → start_agent (moves to current/) → close_bug (moves to bugs/archive/)
-- [ ] Integration test: full spike lifecycle — start_agent (moves to current/) → completion (moves back or archives)
-- [ ] All deterministic MCP tools (`create_story`, `accept_story`, `close_bug`, `check_criterion`, `set_test_plan`, `start_agent`) resolve paths correctly against the new directory layout
-- [ ] `list_current` MCP tool (or update `list_agents`) shows all items in `.story_kit/current/` with their type (story/bug/spike)
-- [ ] All agent prompts in `.story_kit/project.toml` (supervisor, coders) updated to reference correct directory paths and workflow steps
-
-## Out of Scope
-
-- UI changes to display current work items