Merge story-32: Multi-Instance Worktree Support

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

# Conflicts:
#	.story_kit/stories/archived/32_multi_instance_worktree_support.md
#	.story_kit/stories/current/30_worktree_agent_orchestration.md
#	.story_kit/stories/current/32_multi_instance_worktree_support.md
#	.story_kit/stories/current/36_enforce_story_front_matter.md
#	.story_kit/stories/upcoming/29_directory_based_workflow_coordination.md
#	.story_kit/stories/upcoming/32_worktree_agent_orchestration.md
#	.story_kit/stories/upcoming/33_worktree_diff_and_editor_integration.md
#	.story_kit/stories/upcoming/34_agent_configuration_and_roles.md
#	.story_kit/stories/upcoming/35_agent_security_and_sandboxing.md

.story_kit/stories/current/30_worktree_agent_orchestration.md

@@ -1,8 +1,7 @@
 ---
 name: Worktree-Based Agent Orchestration
-test_plan: approved
+test_plan: pending
 ---
-
 # Story 30: Worktree-Based Agent Orchestration
 
 ## User Story

.story_kit/stories/current/36_enforce_story_front_matter.md

@@ -2,7 +2,6 @@
 name: Enforce Front Matter on All Story Files
 test_plan: pending
 ---
-
 # Story 36: Enforce Front Matter on All Story Files
 
 ## User Story
@@ -13,3 +12,4 @@ As a user, I want the system to validate that every story file has valid front m
 - [ ] Existing story files are updated to include valid front matter.
 - [ ] The TODO panel displays the story name from front matter instead of falling back to the file stem.
 - [ ] A CLI or API command can check all stories for front matter compliance.
+- [ ] A `POST /workflow/stories/create` endpoint creates a new story file with valid front matter (name, test_plan) and story scaffold, so agents never need to manually construct the file format.

.story_kit/stories/upcoming/29_directory_based_workflow_coordination.md

@@ -2,7 +2,6 @@
 name: Directory-Based Workflow Coordination and Locks
 test_plan: pending
 ---
-
 # Story 29: Directory-Based Workflow Coordination and Locks
 
 ## User Story
@@ -17,4 +16,4 @@ As a user, I want directory-based story workflow coordination with lock tracking
 ## Out of Scope
 - Implementing the lock mechanism or agents in code.
 - Enforcing locks at runtime.
-- Multi-agent orchestration beyond documenting the workflow.
+- Multi-agent orchestration beyond documenting the workflow.

.story_kit/stories/upcoming/33_worktree_diff_and_editor_integration.md

@@ -2,7 +2,6 @@
 name: Worktree Diff Inspection and Editor Integration
 test_plan: pending
 ---
-
 # Story 33: Worktree Diff Inspection and Editor Integration
 
 ## User Story

.story_kit/stories/upcoming/34_agent_configuration_and_roles.md

@@ -2,7 +2,6 @@
 name: Per-Project Agent Configuration and Role Definitions
 test_plan: pending
 ---
-
 # Story 34: Per-Project Agent Configuration and Role Definitions
 
 ## User Story

.story_kit/stories/upcoming/35_agent_security_and_sandboxing.md

@@ -2,8 +2,7 @@
 name: Agent Security and Sandboxing
 test_plan: pending
 ---
-
-# Story 35: Agent Security and Sandboxing
+# Story 34: Agent Security and Sandboxing
 
 ## User Story
 **As a** supervisor orchestrating multiple autonomous agents,