refactor: deep Codex v4 API conversion for all 20 team skills

Upgrade all team-* skills from mechanical v3→v4 API renames to deep
v4 tool integration with skill-adaptive patterns:

- list_agents: health checks in handleResume, cleanup verification in
  handleComplete, added to allowed-tools and coordinator toolbox
- Named targeting: task_name uses task-id (e.g. EXPLORE-001) instead
  of generic <role>-worker, enabling send_message/assign_task by name
- Message semantics: send_message for supplementary cross-agent context
  vs assign_task for triggering work, with skill-specific examples
- Model selection: per-role reasoning_effort guidance matching each
  skill's actual roles (not generic boilerplate)
- timeout_ms: added to all wait_agent calls, timed_out handling in
  all 18 monitor.md files
- Skill-adaptive v4 sections: ultra-analyze N-parallel coordination,
  lifecycle-v4 supervisor assign_task/send_message distinction,
  brainstorm ideator parallel patterns, iterdev generator-critic loops,
  frontend-debug iterative debug assign_task, perf-opt benchmark
  context sharing, executor lightweight trimmed v4, etc.

60 files changed across 20 team skills (SKILL.md, monitor.md, role.md)

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

.codex/skills/team-roadmap-dev/roles/coordinator/commands/monitor.md

@@ -261,6 +261,7 @@ Ready tasks found?
 ```
 spawn_agent({
   agent_type: "team_worker",
+  task_name: taskId,  // e.g., "PLAN-101" — enables named targeting
   items: [{
     description: "Spawn <role> worker for <subject>",
     team_name: "roadmap-dev",
@@ -286,7 +287,22 @@ Execute built-in Phase 1 -> role-spec Phase 2-4 -> built-in Phase 5.`
 })
 ```
 
-Workers report results via `report_agent_job_result()`. Coordinator receives results via `wait_agent({ ids })`.
+Workers report results via `report_agent_job_result()`. Coordinator receives results via `wait_agent({ targets: [taskId], timeout_ms: 900000 })`. If `result.timed_out`, mark tasks as `timed_out` and close agents. Use `close_agent({ target: taskId })` with task_name for cleanup.
+
+**Cross-Agent Supplementary Context** (v4):
+
+When spawning workers in a later pipeline phase, send upstream results as supplementary context to already-running workers:
+
+```
+// Example: Send planning results to running executor
+send_message({
+  target: "<running-agent-task-name>",
+  items: [{ type: "text", text: `## Supplementary Context\n${upstreamFindings}` }]
+})
+// Note: send_message queues info without interrupting the agent's current work
+```
+
+Use `send_message` (not `assign_task`) for supplementary info that enriches but doesn't redirect the agent's current task.
 
 ---
 
@@ -330,6 +346,16 @@ Then STOP.
 
 ### Handler: handleResume
 
+**Agent Health Check** (v4):
+```
+// Verify actual running agents match session state
+const runningAgents = list_agents({})
+// For each active_agent in tasks.json:
+//   - If agent NOT in runningAgents -> agent crashed
+//   - Reset that task to pending, remove from active_agents
+// This prevents stale agent references from blocking the pipeline
+```
+
 Check active worker completion, process results, advance pipeline. Also handles resume from paused state.
 
 ```
@@ -354,6 +380,14 @@ Check coordinates.status:
 
 ### Handler: handleComplete
 
+**Cleanup Verification** (v4):
+```
+// Verify all agents are properly closed
+const remaining = list_agents({})
+// If any team agents still running -> close_agent each
+// Ensures clean session shutdown
+```
+
 All phases done. Generate final project summary and finalize session.
 
 ```

.codex/skills/team-roadmap-dev/roles/coordinator/role.md

@@ -6,7 +6,7 @@ Orchestrate the roadmap-driven development workflow: init prerequisites -> roadm
 
 **You are a dispatcher, not a doer.** Your ONLY outputs are:
 - Session state files (`.workflow/.team/` directory)
-- `spawn_agent` / `wait_agent` / `close_agent` / `send_input` calls
+- `spawn_agent` / `wait_agent` / `close_agent` / `send_message` / `assign_task` calls
 - Status reports to the user / `request_user_input` prompts
 
 **FORBIDDEN** (even if the task seems trivial):
@@ -41,6 +41,8 @@ WRONG: Edit/Write on project source files            — worker work
 - Monitor progress via worker callbacks and route messages
 - Maintain session state persistence
 - **Always proceed through full Phase 1-5 workflow, never skip to direct execution**
+- Use `send_message` for supplementary context (non-interrupting) and `assign_task` for triggering new work
+- Use `list_agents` for session resume health checks and cleanup verification
 
 ### MUST NOT
 
@@ -135,6 +137,7 @@ For callback/check/resume/complete: load `@commands/monitor.md` and execute matc
 | `report_agent_job_result` | Worker communication | workers | Report results to coordinator |
 | `mcp__ccw-tools__team_msg` | Message bus | coordinator | Log all communications |
 | `Read/Write` | File operations | coordinator | Session state management |
+| `list_agents` | System | coordinator | Runtime agent discovery and health check |
 
 ---
 
@@ -262,7 +265,7 @@ mcp__ccw-tools__team_msg({
 
 **Design**: Spawn-and-Stop + Callback pattern.
 - Spawn workers with `spawn_agent()` -> immediately return
-- Worker completes -> report_agent_job_result() -> coordinator receives via wait_agent() -> auto-advance
+- Worker completes -> report_agent_job_result() -> coordinator receives via wait_agent({ timeout_ms: 900000 }) -> auto-advance
 - User can use "check" / "resume" to manually advance
 - Coordinator does one operation per invocation, then STOPS
 
@@ -304,6 +307,16 @@ Delegate to `@commands/monitor.md`:
 
 ---
 
+## v4 Coordination Patterns
+
+### Message Semantics
+- **send_message**: Queue supplementary info to a running agent. Does NOT interrupt current processing. Use for: sharing upstream results, context enrichment, FYI notifications.
+- **assign_task**: Assign new work and trigger processing. Use for: waking idle agents, redirecting work, requesting new output.
+
+### Agent Lifecycle Management
+- **list_agents({})**: Returns all running agents. Use in handleResume to reconcile session state with actual running agents. Use in handleComplete to verify clean shutdown.
+- **Named targeting**: Workers spawned with `task_name: "<task-id>"` can be addressed by name in send_message, assign_task, and close_agent calls.
+
 ## Error Handling
 
 | Scenario | Resolution |