Renumber upcoming stories and add .ignore updates

Drop story 28, renumber 30-33 to 28-31, add story 31 (View Upcoming
Stories), and extend .ignore for .claude/ and .story_kit/ directories.

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

.ignore

@@ -1,2 +1,4 @@
-# Prevents cargo watch from restarting the server when frontend files change
+# Prevents cargo watch from restarting the server on non-Rust file changes
 frontend/
+.claude/
+.story_kit/

.story_kit/stories/upcoming/28_standardize_acceptance_tests_and_todos.md

@@ -1,16 +0,0 @@
-# Story 28: Standardize Acceptance Tests and TODO Flow
-
-## User Story
-As a user, I want a consistent acceptance test layout and TODO workflow, so acceptance criteria are translated into tests in a predictable, toolable way.
-
-## Acceptance Criteria
-- A single, documented folder structure exists for acceptance tests and story TODO files.
-- Each story must have a `tests/todo/story-XX.todo` file with one comment per Acceptance Criterion using the format `// AC: story-XX#N - ...`.
-- Acceptance tests and integration tests follow the standard Rust `tests/` layout.
-- The workflow requires consuming TODOs one at a time: write a failing test, delete the TODO line, make it pass, then refactor.
-- The test plan references the frameworks and commands in `specs/tech/STACK.md`.
-
-## Out of Scope
-- Building UI surfaces for TODO visibility.
-- Migrating existing tests to the new layout.
-- Introducing new test frameworks beyond those listed in `specs/tech/STACK.md`.

.story_kit/stories/upcoming/28_ui_show_test_todos.md

@@ -1,4 +1,4 @@
-# Story 30: Show Remaining Test TODOs in the UI
+# Story 28: Show Remaining Test TODOs in the UI
 
 ## User Story
 As a user, I want the UI to show the remaining test TODOs for the current story, so I can track which Acceptance Criteria are still untested.

.story_kit/stories/upcoming/29_directory_based_workflow_coordination.md

@@ -1,4 +1,4 @@
-# Story 31: Directory-Based Workflow Coordination and Locks
+# Story 29: Directory-Based Workflow Coordination and Locks
 
 ## User Story
 As a user, I want directory-based story workflow coordination with lock tracking, so multiple agents can pick up work with minimal context while keeping coordination in `master`.

.story_kit/stories/upcoming/30_worktree_agent_orchestration.md

@@ -1,4 +1,4 @@
-# Story 32: Worktree-Based Agent Orchestration
+# Story 30: Worktree-Based Agent Orchestration
 
 ## User Story
 As a user, I want to press a button in the frontend to spin up an agent that works on a story in its own git worktree, so that multiple stories can be worked on concurrently without branch conflicts.
@@ -40,7 +40,7 @@ prompt = "Read .story_kit/README.md, then pick up story {{story_id}}"
 Components are set up in order. Each `path` is relative to the worktree root.
 
 ## Out of Scope
-- Coordinating merges to master when multiple agents finish simultaneously (see Story 31).
-- Lock file implementation for multi-agent conflict prevention (see Story 31).
+- Coordinating merges to master when multiple agents finish simultaneously (see Story 29).
+- Lock file implementation for multi-agent conflict prevention (see Story 29).
 - Port management for dev servers within worktrees.
 - Agent-to-agent communication.

.story_kit/stories/upcoming/31_view_upcoming_stories.md

@@ -0,0 +1,19 @@
+---
+name: View Upcoming Stories
+test_plan: pending
+---
+
+# Story 31: View Upcoming Stories
+
+## User Story
+As a user, I want to see a list of upcoming stories in the UI so I can understand what work is planned next.
+
+## Acceptance Criteria
+- [ ] The UI displays a panel listing all stories from `.story_kit/stories/upcoming/`.
+- [ ] Each story shows its name (from front matter or filename).
+- [ ] The list refreshes when the user clicks a refresh button.
+
+## Out of Scope
+- Editing or reordering stories from the UI.
+- Showing story details or acceptance criteria inline.
+- Moving stories between upcoming/current/archived from the UI.