story-kit: commit work pipeline files and package-lock

Commit untracked work pipeline files (stories, bugs in various stages)
and package-lock.json that were present on the filesystem but not yet
tracked by git.

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

.story_kit/work/3_qa/245_bug_chat_history_persistence_lost_on_page_refresh_story_145_regression.md

@@ -0,0 +1,32 @@
+---
+name: "Chat history persistence lost on page refresh (story 145 regression)"
+---
+
+# Bug 245: Chat history persistence lost on page refresh (story 145 regression)
+
+## Description
+
+Story 145 implemented localStorage persistence for chat history across page reloads. This is no longer working — refreshing the page loses all conversation context. This is a regression of the feature delivered in story 145.
+
+## How to Reproduce
+
+1. Open the web UI and have a conversation with the agent
+2. Refresh the page (F5 or Cmd+R)
+
+## Actual Result
+
+Chat history is gone after refresh — the UI shows a blank conversation.
+
+## Expected Result
+
+Chat history is restored from localStorage on page load, as implemented in story 145.
+
+## Acceptance Criteria
+
+- [ ] Chat messages survive a full page refresh
+- [ ] Chat messages are restored from localStorage on component mount
+- [ ] Behaviour matches the original acceptance criteria from story 145
+
+## Investigation Notes
+
+**Use `git bisect` to find the commit that broke this.** Story 145 delivered working localStorage persistence — something after that regressed it. Find the breaking commit, understand the root cause, and fix it there. Do NOT layer on a new implementation. Revert or surgically fix the regression.

.story_kit/work/3_qa/249_story_agent_assignment_via_story_front_matter.md

@@ -0,0 +1,21 @@
+---
+name: "Agent assignment via story front matter"
+---
+
+# Story 249: Agent assignment via story front matter
+
+## User Story
+
+As a project owner, I want to specify which agent should work on a story via a front matter field (e.g. agent: coder-opus) so that complex stories get assigned to the right coder automatically.
+
+## Acceptance Criteria
+
+- [ ] Story files support an optional agent front matter field (e.g. agent: coder-opus)
+- [ ] When the pipeline auto-assigns a coder to a story, it uses the agent specified in front matter if present
+- [ ] If the specified agent is busy, the story waits rather than falling back to a different coder
+- [ ] If no agent is specified in front matter, the existing default assignment behaviour is used
+- [ ] The supervisor agent respects the front matter assignment when starting coders
+
+## Out of Scope
+
+- TBD