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/archived/32_multi_instance_worktree_support.md

@@ -0,0 +1,22 @@
+---
+name: "Multi-Instance Worktree Support"
+test_plan: approved
+---
+# Story 32: Multi-Instance Worktree Support
+
+## User Story
+**As a** developer working across multiple git worktrees,
+**I want** to run separate app instances (server + frontend) per worktree on different ports,
+**So that** I can QA each worktree independently without port conflicts.
+
+## Acceptance Criteria
+- [ ] Server discovers an available port instead of hardcoding 3001 (e.g., try 3001, then 3002, etc., or use port 0 and report back).
+- [ ] Server prints the actual bound port on startup so callers can discover it.
+- [ ] Frontend dev server proxy target is configurable (env var or auto-detected from server).
+- [ ] WebSocket client in the frontend reads the port dynamically rather than hardcoding it.
+- [ ] A simple registry or file-based mechanism lets a supervisor discover which ports map to which worktrees.
+
+## Out of Scope
+- Agent orchestration across worktrees (separate story).
+- Service mesh or container orchestration.
+- Multi-machine distributed instances (local only for now).