Refactor and optimize various components and files

- Removed deprecated `ccw-contentPattern-optimization-summary.md` and related files.
- Updated `A2UIPopupCard.tsx` to clarify comments on interaction handling.
- Enhanced `QueueListColumn.tsx` and `QueuePanel.tsx` to handle potential undefined values for `config`.
- Added `useEffect` in `QueuePanel.tsx` to load scheduler state on mount.
- Improved `SchedulerPanel.tsx` to handle potential undefined values for `sessionPool`.
- Introduced auto-initialization logic in `queueSchedulerStore.ts` to prevent multiple initialization calls.
- Updated `A2UIWebSocketHandler.ts` to refine selection handling logic.
- Enhanced `hooks-routes.ts` to support multi-question surfaces.
- Added submit and cancel buttons in `ask-question.ts` for better user interaction.
- Deleted `codex_prompt.md` and `contentPattern-library-options.md` as part of cleanup.
- Removed `status-reference.md` to streamline documentation.

.claude/skills/team-coordinate/roles/coordinator/commands/analyze-task.md

@@ -98,7 +98,6 @@ Apply merging rules to reduce role count:
 |------|-----------|--------|
 | Absorb trivial | Capability has exactly 1 task AND no explore needed | Merge into nearest related role |
 | Merge overlap | Two capabilities share >50% keywords from task description | Combine into single role |
-| Coordinator inline | Planner capability with 1 task, no explore | Coordinator handles inline, no separate role |
 | Cap at 5 | More than 5 roles after initial assignment | Merge lowest-priority pairs (priority: researcher > designer > developer > writer > analyst > planner > tester) |
 
 **Merge priority** (when two must merge, keep the higher-priority one as the role name):
@@ -108,9 +107,11 @@ Apply merging rules to reduce role count:
 3. writer (document generation has specific patterns)
 4. designer (design has specific outputs)
 5. analyst (analysis can be absorbed by reviewer pattern)
-6. planner (can be absorbed by coordinator)
+6. planner (planning can be merged with researcher or designer)
 7. tester (can be absorbed by developer or analyst)
 
+**IMPORTANT**: Even after merging, coordinator MUST spawn workers for all roles. Single-role tasks still use team architecture.
+
 ## Phase 4: Output
 
 Write `<session-folder>/task-analysis.json`:
@@ -165,6 +166,27 @@ Write `<session-folder>/task-analysis.json`:
 }
 ```
 
+## Complexity Interpretation
+
+**CRITICAL**: Complexity score is for **role design optimization**, NOT for skipping team workflow.
+
+| Complexity | Team Structure | Coordinator Action |
+|------------|----------------|-------------------|
+| Low (1-2 roles) | Minimal team | Generate 1-2 roles, create team, spawn workers |
+| Medium (2-3 roles) | Standard team | Generate roles, create team, spawn workers |
+| High (3-5 roles) | Full team | Generate roles, create team, spawn workers |
+
+**All complexity levels use team architecture**:
+- Single-role tasks still spawn worker via Skill
+- Coordinator NEVER executes task work directly
+- Team infrastructure provides session management, message bus, fast-advance
+
+**Purpose of complexity score**:
+- ✅ Determine optimal role count (merge vs separate)
+- ✅ Guide dependency graph design
+- ✅ Inform user about task scope
+- ❌ NOT for deciding whether to use team workflow
+
 ## Error Handling
 
 | Scenario | Resolution |
@@ -172,4 +194,4 @@ Write `<session-folder>/task-analysis.json`:
 | No capabilities detected | Default to single `general` role with TASK prefix |
 | Circular dependency in graph | Break cycle at lowest-tier edge, warn |
 | Task description too vague | Return minimal analysis, coordinator will AskUserQuestion |
-| All capabilities merge into one | Valid -- single-role execution, no team overhead |
+| All capabilities merge into one | Valid -- single-role execution via team worker |

.claude/skills/team-coordinate/roles/coordinator/role.md

@@ -32,6 +32,27 @@ Orchestrate the team-coordinate workflow: task analysis, dynamic role generation
 
 ---
 
+## Command Execution Protocol
+
+When coordinator needs to execute a command (analyze-task, dispatch, monitor):
+
+1. **Read the command file**: `roles/coordinator/commands/<command-name>.md`
+2. **Follow the workflow** defined in the command file (Phase 2-4 structure)
+3. **Commands are inline execution guides** - NOT separate agents or subprocesses
+4. **Execute synchronously** - complete the command workflow before proceeding
+
+Example:
+```
+Phase 1 needs task analysis
+  -> Read roles/coordinator/commands/analyze-task.md
+  -> Execute Phase 2 (Context Loading)
+  -> Execute Phase 3 (Task Analysis)
+  -> Execute Phase 4 (Output)
+  -> Continue to Phase 2
+```
+
+---
+
 ## Entry Router
 
 When coordinator is invoked, first detect the invocation type:
@@ -42,10 +63,24 @@ When coordinator is invoked, first detect the invocation type:
 | Status check | Arguments contain "check" or "status" | -> handleCheck |
 | Manual resume | Arguments contain "resume" or "continue" | -> handleResume |
 | Capability gap | Message contains "capability_gap" | -> handleAdapt |
-| New session | None of above | -> Phase 0 |
+| Interrupted session | Active/paused session exists in `.workflow/.team/TC-*` | -> Phase 0 (Resume Check) |
+| New session | None of above | -> Phase 1 (Task Analysis) |
 
 For callback/check/resume/adapt: load `commands/monitor.md` and execute the appropriate handler, then STOP.
 
+### Router Implementation
+
+1. **Load session context** (if exists):
+   - Scan `.workflow/.team/TC-*/team-session.json` for active/paused sessions
+   - If found, extract `session.roles[].name` for callback detection
+
+2. **Parse $ARGUMENTS** for detection keywords
+
+3. **Route to handler**:
+   - For monitor handlers: Read `commands/monitor.md`, execute matched handler section, STOP
+   - For Phase 0: Execute Session Resume Check below
+   - For Phase 1: Execute Task Analysis below
+
 ---
 
 ## Phase 0: Session Resume Check
@@ -96,6 +131,21 @@ For callback/check/resume/adapt: load `commands/monitor.md` and execute the appr
 
 **Success**: Task analyzed, capabilities detected, dependency graph built, roles designed.
 
+**CRITICAL - Team Workflow Enforcement**:
+
+Regardless of complexity score or role count, coordinator MUST:
+- ✅ **Always proceed to Phase 2** (generate roles)
+- ✅ **Always create team** and spawn workers
+- ❌ **NEVER execute task work directly**, even for single-role low-complexity tasks
+- ❌ **NEVER skip team workflow** based on complexity assessment
+
+**Single-role execution is still team-based** - just with one worker. The team architecture provides:
+- Consistent message bus communication
+- Session state management
+- Artifact tracking
+- Fast-advance capability
+- Resume/recovery mechanisms
+
 ---
 
 ## Phase 2: Generate Roles + Initialize Session