feat: migrate all codex team skills from spawn_agents_on_csv to spawn_agent + wait_agent architecture

- Delete 21 old team skill directories using CSV-wave pipeline pattern (~100+ files)
- Delete old team-lifecycle (v3) and team-planex-v2
- Create generic team-worker.toml and team-supervisor.toml (replacing tlv4-specific TOMLs)
- Convert 19 team skills from Claude Code format (Agent/SendMessage/TaskCreate)
  to Codex format (spawn_agent/wait_agent/tasks.json/request_user_input)
- Update team-lifecycle-v4 to use generic agent types (team_worker/team_supervisor)
- Convert all coordinator role files: dispatch.md, monitor.md, role.md
- Convert all worker role files: remove run_in_background, fix Bash syntax
- Convert all specs/pipelines.md references
- Final state: 20 team skills, 217 .md files, zero Claude Code API residuals

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

.codex/skills/team-ultra-analyze/roles/explorer/role.md

@@ -0,0 +1,74 @@
+---
+role: explorer
+prefix: EXPLORE
+inner_loop: false
+message_types:
+  success: exploration_ready
+  error: error
+---
+
+# Codebase Explorer
+
+Explore codebase structure through cli-explore-agent, collecting structured context (files, patterns, findings) for downstream analysis. One explorer per analysis perspective.
+
+## Phase 2: Context & Scope Assessment
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Task description | From task subject/description | Yes |
+| Session path | Extracted from task description | Yes |
+
+1. Load debug specs: Run `ccw spec load --category debug` for known issues and root-cause notes
+2. Extract session path, topic, perspective, dimensions from task description:
+
+| Field | Pattern | Default |
+|-------|---------|---------|
+| sessionFolder | `session:\s*(.+)` | required |
+| topic | `topic:\s*(.+)` | required |
+| perspective | `perspective:\s*(.+)` | "general" |
+| dimensions | `dimensions:\s*(.+)` | "general" |
+
+2. Determine exploration number from task subject (EXPLORE-N)
+3. Build exploration strategy by perspective:
+
+| Perspective | Focus | Search Depth |
+|-------------|-------|-------------|
+| general | Overall codebase structure and patterns | broad |
+| technical | Implementation details, code patterns, feasibility | medium |
+| architectural | System design, module boundaries, interactions | broad |
+| business | Business logic, domain models, value flows | medium |
+| domain_expert | Domain patterns, standards, best practices | deep |
+
+## Phase 3: Codebase Exploration
+
+Use CLI tool for codebase exploration:
+
+```javascript
+Bash({
+  command: `ccw cli -p "PURPOSE: Explore codebase for <topic> from <perspective> perspective; success = structured findings with relevant files and patterns
+TASK: • Run module depth analysis • Search for topic-related patterns • Identify key files and their relationships • Extract architectural insights
+MODE: analysis
+CONTEXT: @**/* | Memory: Session <session-folder>, perspective <perspective>
+EXPECTED: JSON output with: relevant_files (path, relevance, summary), patterns, key_findings, module_map, questions_for_analysis, _metadata (perspective, search_queries, timestamp)
+CONSTRAINTS: Focus on <perspective> angle - <strategy.focus> | Write to <session>/explorations/exploration-<num>.json
+" --tool gemini --mode analysis --rule analysis-analyze-code-patterns`,
+})
+```
+
+**ACE fallback** (when CLI produces no output):
+```javascript
+mcp__ace-tool__search_context({ project_root_path: ".", query: "<topic> <perspective>" })
+```
+
+## Phase 4: Result Validation
+
+| Check | Method | Action on Failure |
+|-------|--------|-------------------|
+| Output file exists | Read output path | Create empty result, run ACE fallback |
+| Has relevant_files | Array length > 0 | Trigger ACE supplementary search |
+| Has key_findings | Array length > 0 | Note partial results, proceed |
+
+Write validated exploration to `<session>/explorations/exploration-<num>.json`.
+
+Update `<session>/wisdom/.msg/meta.json` under `explorer` namespace:
+- Read existing -> merge `{ "explorer": { perspective, file_count, finding_count } }` -> write back