story-kit: done 254_story_add_refactor_work_item_type

.story_kit/work/5_done/254_story_add_refactor_work_item_type.md

@@ -0,0 +1,23 @@
+---
+name: "Add refactor work item type"
+merge_failure: "merge_agent_work tool returned empty output on two attempts. The merge-queue branch (merge-queue/254_story_add_refactor_work_item_type) was created with squash merge commit 27d24b2, and the merge workspace worktree exists at .story_kit/merge_workspace, but the pipeline never completed (no success/failure logged after MERGE-DEBUG calls). The stale merge workspace worktree may be blocking completion. Possibly related to bug 250 (merge pipeline cherry-pick fails with bad revision on merge-queue branch). Human intervention needed to: 1) clean up the merge-queue worktree and branch, 2) investigate why the merge pipeline hangs after creating the squash merge commit, 3) retry the merge."
+---
+
+# Story 254: Add refactor work item type
+
+## User Story
+
+As a project owner, I want a refactor work item type so that I can track and assign code restructuring tasks separately from features and bugs.
+
+## Acceptance Criteria
+
+- [ ] create_refactor MCP tool creates a refactor file in work/1_upcoming/ with deterministic filename (e.g. 254_refactor_split_agents_rs.md)
+- [ ] Refactor files use the naming convention {id}_refactor_{slug}.md
+- [ ] Refactor items flow through the same pipeline as stories and bugs (upcoming → current → qa → merge → done → archived)
+- [ ] list_refactors MCP tool lists open refactors in upcoming
+- [ ] Frontend displays refactor items distinctly from stories and bugs (different label/color)
+- [ ] Watcher recognizes refactor files and auto-commits moves like stories and bugs
+
+## Out of Scope
+
+- TBD