Splitting up the editor and diff stories

.story_kit/stories/upcoming/33_worktree_diff_and_editor_integration.md

@@ -1,24 +1,20 @@
 ---
-name: Worktree Diff Inspection and Editor Integration
+name: Worktree Diff Inspection
 test_plan: pending
 ---
-# Story 33: Worktree Diff Inspection and Editor Integration
+# Story 33: Worktree Diff Inspection
 
 ## User Story
 **As a** supervisor coordinating agents across worktrees,
-**I want to** view diffs of in-progress agent work and open worktrees in my editor,
+**I want to** view diffs of in-progress agent work and open worktrees in my diff utility,
 **So that** I can review changes, catch problems early, and intervene when needed.
 
 ## Acceptance Criteria
 - [ ] API endpoint (or CLI command) returns `git diff` output for a given worktree path.
 - [ ] API endpoint returns `git diff --stat` summary for a quick overview.
 - [ ] API endpoint can return diff against the base branch (e.g., `git diff main...HEAD`).
-- [ ] A "open in editor" action launches the configured editor (e.g., `zed`) pointed at a worktree directory.
-- [ ] Editor preference is configurable (stored in app settings, defaults to `$EDITOR` or `zed`).
-- [ ] Frontend can trigger "open in editor" for any listed worktree/agent.
 - [ ] Frontend can display a diff view for any worktree with syntax-highlighted changes.
 
 ## Out of Scope
 - Full code review workflow (comments, approvals).
 - Automatic merge or conflict resolution.
-- Editor plugin integration (just launching the editor at the worktree path is sufficient).

.story_kit/stories/upcoming/37_editor_command_for_worktrees.md

@@ -0,0 +1,24 @@
+---
+name: Editor Command for Worktrees
+test_plan: pending
+---
+
+# Story 37: Editor Command for Worktrees
+
+## User Story
+
+As a user supervising multiple agents working in worktrees, I want to configure my preferred editor (e.g. Zed, VS Code, Cursor) so that agents can give me a ready-to-paste command like `zed ~/workspace/foo/bar/story-45-worktree` to quickly open a worktree in my editor.
+
+## Acceptance Criteria
+
+- [ ] User can configure a preferred editor command (e.g. `zed`, `code`, `cursor`) via the API
+- [ ] Editor preference is persisted across server restarts
+- [ ] API endpoint returns a formatted open-in-editor command for a given worktree path
+- [ ] The UI displays a copy-paste-ready editor command for each active worktree
+- [ ] Agents can retrieve the editor command for a worktree they're working in
+
+## Out of Scope
+
+- Actually launching the editor from the server (just provide the command string)
+- Editor plugin/extension integration
+- Detecting installed editors automatically