story-kit: accept 241_story_help_slash_command

.story_kit/work/6_archived/241_story_help_slash_command.md

@@ -0,0 +1,24 @@
+---
+name: "/help Slash Command"
+---
+
+# Story 241: /help Slash Command
+
+## User Story
+
+As a user, I want to type /help in the chat input so that I can see a list of available slash commands and what they do.
+
+## Acceptance Criteria
+
+- [ ] User can type /help in the chat input
+- [ ] A help overlay or panel displays all available slash commands with brief descriptions
+- [ ] The overlay can be dismissed with Escape, Enter, or Space
+- [ ] The slash command detection and dispatch mechanism is shared across all slash commands (reuse the same parser/router used by /btw and other slash commands — do not duplicate detection logic)
+
+## Out of Scope
+
+- TBD
+
+## Rejection Notes
+
+**2026-03-14:** Previous implementation was rejected. The frontend did nothing when the user typed `/help` — the slash command was not wired up in the UI at all. Ensure the full end-to-end flow works: typing `/help` in the chat input must visibly display the help overlay with slash command descriptions.

.story_kit/work/6_archived/243_bug_replace_pnpm_with_npm.md

@@ -0,0 +1,28 @@
+---
+name: "Replace pnpm with npm"
+---
+
+# Bug 243: Replace pnpm with npm
+
+## Description
+
+pnpm's reflink-based package import frequently fails with ERR_PNPM_ENOENT when running in git worktrees (.story_kit/merge_workspace), causing merge quality gates to fail repeatedly. No pnpm-specific features are in use.
+
+## How to Reproduce
+
+Move any story to merge. The mergemaster runs pnpm install in the merge worktree and it fails with ERR_PNPM_ENOENT reflink errors.
+
+## Actual Result
+
+pnpm install fails in merge worktrees, blocking all merges.
+
+## Expected Result
+
+Package installation works reliably in all worktree contexts.
+
+## Acceptance Criteria
+
+- [ ] pnpm-lock.yaml is removed and package-lock.json is generated
+- [ ] All pnpm references in project.toml are replaced with npm equivalents
+- [ ] npm install and npm run build succeed in a clean worktree
+- [ ] No other pnpm references remain in project configuration

.story_kit/work/6_archived/247_story_human_qa_gate_with_rejection_flow.md

@@ -0,0 +1,25 @@
+---
+name: "Human QA gate with rejection flow"
+---
+
+# Story 247: Human QA gate with rejection flow
+
+## User Story
+
+As the project owner, I want stories to require my manual approval after machine QA before they can be merged, so that features that compile and pass tests but do not actually work correctly are caught before reaching master.
+
+## Acceptance Criteria
+
+- [ ] Story files support a manual_qa front matter field (defaults to true)
+- [ ] After machine QA passes in 3_qa, stories with manual_qa: true wait for human approval before moving to 4_merge
+- [ ] The UI shows a clear way to launch the app from the worktree for manual testing (single button click), with automatic port conflict handling via .story_kit_port
+- [ ] Frontend and backend are pre-compiled during machine QA so the app is ready to run instantly for manual testing
+- [ ] Only one QA app instance runs at a time — do not automatically spin up multiple instances
+- [ ] Human can approve a story from 3_qa to move it to 4_merge
+- [ ] Human can reject a story from 3_qa back to 2_current with notes about what is broken
+- [ ] Rejection notes are written into the story file so the coder can see what needs fixing
+- [ ] Stories with manual_qa: false skip the human gate and proceed directly from machine QA to 4_merge
+
+## Out of Scope
+
+- TBD

.story_kit/work/6_archived/248_bug_chat_does_not_auto_scroll_to_new_messages.md

@@ -0,0 +1,27 @@
+---
+name: "Chat does not auto-scroll to new messages"
+---
+
+# Bug 248: Chat does not auto-scroll to new messages
+
+## Description
+
+The chat UI does not automatically scroll to the bottom when new assistant messages stream in. The user has to manually scroll down to see the response, making it appear as if the bot stopped responding.
+
+## How to Reproduce
+
+1. Send a message in the chat UI
+2. Wait for the assistant to respond with a long message or multi-turn tool use
+3. Observe that the viewport does not scroll to follow the new content
+
+## Actual Result
+
+The viewport stays at the current scroll position. New messages appear below the fold, invisible to the user.
+
+## Expected Result
+
+The chat viewport should auto-scroll to the bottom as new content streams in, keeping the latest message visible.
+
+## Acceptance Criteria
+
+- [ ] Bug is fixed and verified