claude-code-workflow 7.2.23 → 7.2.24

package/.codex/skills/team-frontend-debug/roles/coordinator/commands/monitor.md

@@ -1,143 +1,177 @@
-# Monitor Pipeline
-
-Event-driven pipeline coordination. Beat model: coordinator wake -> process -> spawn -> STOP.
-
-## Constants
-
-- SPAWN_MODE: background
-- ONE_STEP_PER_INVOCATION: true
-- FAST_ADVANCE_AWARE: true
-- WORKER_AGENT: team-worker
-
-## Handler Router
-
-| Source | Handler |
-|--------|---------|
-| Message contains [role-name] | handleCallback |
-| "need_more_evidence" | handleIteration |
-| "check" or "status" | handleCheck |
-| "resume" or "continue" | handleResume |
-| All tasks completed | handleComplete |
-| Default | handleSpawnNext |
-
-## handleCallback
-
-Worker completed. Process and advance.
-
-1. Find matching worker by role in message
-2. Check if progress update (inner loop) or final completion
-3. Progress -> update session state, STOP
-4. Completion -> mark task done (read `<session>/tasks.json`, set status to "completed", write back), remove from active_workers
-5. Check for special conditions:
-   - **TEST-001 with 0 issues** -> skip ANALYZE/FIX/VERIFY (mark as completed in tasks.json), handleComplete
-   - **TEST-001 with only warnings** -> request_user_input: fix warnings or complete
-   - **TEST-001 with high/medium issues** -> proceed to ANALYZE-001
-   - ANALYZE-001 with `need_more_evidence: true` -> handleIteration
-   - VERIFY-001 with `verdict: fail` -> re-dispatch FIX (add FIX-002 entry to tasks.json blocked by VERIFY-001)
-   - VERIFY-001 with `verdict: pass` -> handleComplete
-6. -> handleSpawnNext
-
-## handleIteration
-
-Analyzer needs more evidence. Create supplemental reproduction task.
-
-1. Parse Analyzer's evidence request (dimensions, specific actions)
-2. Add REPRODUCE-002 entry to `<session>/tasks.json`:
-   - Set owner to "reproducer" (no blockedBy -- can start immediately)
-3. Add ANALYZE-002 entry to `<session>/tasks.json`:
-   - Set blockedBy: ["REPRODUCE-002"]
-   - Update FIX-001 entry to add ANALYZE-002 to its blockedBy
-4. Write updated tasks.json
-5. -> handleSpawnNext
-
-## handleCheck
-
-Read-only status report, then STOP.
-
-Output:
-```
-[coordinator] Debug Pipeline Status
-[coordinator] Bug: <bug-description-summary>
-[coordinator] Progress: <done>/<total> (<pct>%)
-[coordinator] Active: <workers with elapsed time>
-[coordinator] Ready: <pending tasks with resolved deps>
-[coordinator] Evidence: <list of collected evidence types>
-[coordinator] Commands: 'resume' to advance | 'check' to refresh
-```
-
-## handleResume
-
-1. No active workers -> handleSpawnNext
-2. Has active -> check each status
-   - completed -> mark done
-   - in_progress -> still running
-3. Some completed -> handleSpawnNext
-4. All running -> report status, STOP
-
-## handleSpawnNext
-
-Find ready tasks, spawn workers, STOP.
-
-1. Collect: completedSubjects, inProgressSubjects, readySubjects (from tasks.json)
-2. No ready + work in progress -> report waiting, STOP
-3. No ready + nothing in progress -> handleComplete
-4. Has ready -> for each:
-   a. Check if inner loop role with active worker -> skip (worker picks up)
-   b. Standard spawn:
-      - Update task status to "in_progress" in tasks.json
-      - team_msg log -> task_unblocked
-      - Spawn team-worker:
-        ```
-        spawn_agent({
-          agent_type: "team_worker",
-          items: [{
-            description: "Spawn <role> worker for <task-id>",
-            team_name: "frontend-debug",
-            name: "<role>",
-            prompt: `## Role Assignment
-        role: <role>
-        role_spec: ~  or <project>/.codex/skills/team-frontend-debug/roles/<role>/role.md
-        session: <session-folder>
-        session_id: <session-id>
-        team_name: frontend-debug
-        requirement: <task-description>
-        inner_loop: <true|false>
-
-        Read role_spec file to load Phase 2-4 domain instructions.
-        Execute built-in Phase 1 -> role-spec Phase 2-4 -> built-in Phase 5.`
-          }]
-        })
-        ```
-      - Add to active_workers
-5. Update session, output summary, STOP
-6. Use `wait_agent({ ids: [<spawned-agent-ids>] })` to wait for callbacks. Workers use `report_agent_job_result()` to send results back.
-
-## handleComplete
-
-Pipeline done. Generate debug report and completion action.
-
-1. Generate debug summary:
-   - Bug description and reproduction results
-   - Root cause analysis (from ANALYZE artifacts)
-   - Code changes applied (from FIX artifacts)
-   - Verification verdict (from VERIFY artifacts)
-   - Evidence inventory (screenshots, logs, traces)
-2. Read session.completion_action:
-   - interactive -> request_user_input (Archive/Keep/Export)
-   - auto_archive -> Archive & Clean (status=completed, remove/archive session folder)
-   - auto_keep -> Keep Active (status=paused)
-
-## handleAdapt
-
-Not typically needed for debug pipeline. If Analyzer identifies a dimension not covered:
-
-1. Parse gap description
-2. Check if reproducer can cover it -> add to evidence plan
-3. Create supplemental REPRODUCE task entry in tasks.json
-
-## Fast-Advance Reconciliation
-
-On every coordinator wake:
-1. Read team_msg entries with type="fast_advance"
-2. Sync active_workers with spawned successors
-3. No duplicate spawns
+# Monitor Pipeline
+
+Event-driven pipeline coordination. Beat model: coordinator wake -> process -> spawn -> STOP.
+
+## Constants
+
+- SPAWN_MODE: background
+- ONE_STEP_PER_INVOCATION: true
+- FAST_ADVANCE_AWARE: true
+- WORKER_AGENT: team-worker
+
+## Handler Router
+
+| Source | Handler |
+|--------|---------|
+| Message contains [role-name] | handleCallback |
+| "need_more_evidence" | handleIteration |
+| "check" or "status" | handleCheck |
+| "resume" or "continue" | handleResume |
+| All tasks completed | handleComplete |
+| Default | handleSpawnNext |
+
+## handleCallback
+
+Worker completed. Process and advance.
+
+1. Find matching worker by role in message
+2. Check if progress update (inner loop) or final completion
+3. Progress -> update session state, STOP
+4. Completion -> mark task done (read `<session>/tasks.json`, set status to "completed", write back), remove from active_workers
+5. Check for special conditions:
+   - **TEST-001 with 0 issues** -> skip ANALYZE/FIX/VERIFY (mark as completed in tasks.json), handleComplete
+   - **TEST-001 with only warnings** -> request_user_input: fix warnings or complete
+   - **TEST-001 with high/medium issues** -> proceed to ANALYZE-001
+   - ANALYZE-001 with `need_more_evidence: true` -> handleIteration
+   - VERIFY-001 with `verdict: fail` -> re-dispatch FIX (add FIX-002 entry to tasks.json blocked by VERIFY-001)
+   - VERIFY-001 with `verdict: pass` -> handleComplete
+6. -> handleSpawnNext
+
+## handleIteration
+
+Analyzer needs more evidence. Create supplemental reproduction task.
+
+1. Parse Analyzer's evidence request (dimensions, specific actions)
+2. Add REPRODUCE-002 entry to `<session>/tasks.json`:
+   - Set owner to "reproducer" (no blockedBy -- can start immediately)
+3. Add ANALYZE-002 entry to `<session>/tasks.json`:
+   - Set blockedBy: ["REPRODUCE-002"]
+   - Update FIX-001 entry to add ANALYZE-002 to its blockedBy
+4. Write updated tasks.json
+5. -> handleSpawnNext
+
+## handleCheck
+
+Read-only status report, then STOP.
+
+Output:
+```
+[coordinator] Debug Pipeline Status
+[coordinator] Bug: <bug-description-summary>
+[coordinator] Progress: <done>/<total> (<pct>%)
+[coordinator] Active: <workers with elapsed time>
+[coordinator] Ready: <pending tasks with resolved deps>
+[coordinator] Evidence: <list of collected evidence types>
+[coordinator] Commands: 'resume' to advance | 'check' to refresh
+```
+
+## 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
+```
+
+1. No active workers -> handleSpawnNext
+2. Has active -> check each status
+   - completed -> mark done
+   - in_progress -> still running
+3. Some completed -> handleSpawnNext
+4. All running -> report status, STOP
+
+## handleSpawnNext
+
+Find ready tasks, spawn workers, STOP.
+
+1. Collect: completedSubjects, inProgressSubjects, readySubjects (from tasks.json)
+2. No ready + work in progress -> report waiting, STOP
+3. No ready + nothing in progress -> handleComplete
+4. Has ready -> for each:
+   a. Check if inner loop role with active worker -> skip (worker picks up)
+   b. Standard spawn:
+      - Update task status to "in_progress" in tasks.json
+      - team_msg log -> task_unblocked
+      - Spawn team-worker:
+        ```
+        spawn_agent({
+          agent_type: "team_worker",
+          task_name: taskId,  // e.g., "TEST-001" — enables named targeting
+          items: [{
+            description: "Spawn <role> worker for <task-id>",
+            team_name: "frontend-debug",
+            name: "<role>",
+            prompt: `## Role Assignment
+        role: <role>
+        role_spec: ~  or <project>/.codex/skills/team-frontend-debug/roles/<role>/role.md
+        session: <session-folder>
+        session_id: <session-id>
+        team_name: frontend-debug
+        requirement: <task-description>
+        inner_loop: <true|false>
+
+        Read role_spec file to load Phase 2-4 domain instructions.
+        Execute built-in Phase 1 -> role-spec Phase 2-4 -> built-in Phase 5.`
+          }]
+        })
+        ```
+      - Add to active_workers
+5. Update session, output summary, STOP
+6. Use `wait_agent({ targets: [<spawned-task-names>], timeout_ms: 900000 })` to wait for callbacks. If `result.timed_out`, mark tasks as `timed_out` and close agents. Use `close_agent({ target: taskId })` with task_name for cleanup. Workers use `report_agent_job_result()` to send results back.
+
+**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 analysis results to running fixer
+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.
+
+## 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
+```
+
+Pipeline done. Generate debug report and completion action.
+
+1. Generate debug summary:
+   - Bug description and reproduction results
+   - Root cause analysis (from ANALYZE artifacts)
+   - Code changes applied (from FIX artifacts)
+   - Verification verdict (from VERIFY artifacts)
+   - Evidence inventory (screenshots, logs, traces)
+2. Read session.completion_action:
+   - interactive -> request_user_input (Archive/Keep/Export)
+   - auto_archive -> Archive & Clean (status=completed, remove/archive session folder)
+   - auto_keep -> Keep Active (status=paused)
+
+## handleAdapt
+
+Not typically needed for debug pipeline. If Analyzer identifies a dimension not covered:
+
+1. Parse gap description
+2. Check if reproducer can cover it -> add to evidence plan
+3. Create supplemental REPRODUCE task entry in tasks.json
+
+## Fast-Advance Reconciliation
+
+On every coordinator wake:
+1. Read team_msg entries with type="fast_advance"
+2. Sync active_workers with spawned successors
+3. No duplicate spawns

package/.codex/skills/team-frontend-debug/roles/coordinator/role.md

@@ -1,152 +1,164 @@
-# Coordinator Role
-
-Orchestrate team-frontend-debug: analyze -> dispatch -> spawn -> monitor -> report.
-
-## Scope Lock (READ FIRST — overrides all other sections)
-
-**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
-- Status reports to the user / `request_user_input` prompts
-
-**FORBIDDEN** (even if the task seems trivial):
-```
-WRONG: Read/Grep/Glob on project source code        — worker work
-WRONG: Bash("ccw cli ...")                           — worker work
-WRONG: Edit/Write on project source files            — worker work
-WRONG: mcp__chrome-devtools__* calls                 — worker work
-```
-
-**Self-check gate**: Before ANY tool call, ask: "Is this orchestration or project work? If project work → STOP → spawn worker."
-
----
-
-## Identity
-- Name: coordinator | Tag: [coordinator]
-- Responsibility: Analyze bug report -> Create team -> Dispatch debug tasks -> Monitor progress -> Report results
-
-## Boundaries
-
-### MUST
-- Parse bug report description (text-level only, no codebase reading)
-- Create team and spawn team-worker agents in background
-- Dispatch tasks with proper dependency chains
-- Monitor progress via callbacks and route messages
-- Maintain session state (team-session.json)
-- Handle iteration loops (analyzer requesting more evidence)
-- Execute completion action when pipeline finishes
-- **Always proceed through full Phase 1-5 workflow, never skip to direct execution**
-
-### MUST NOT
-- Read source code or explore codebase (delegate to workers)
-- Execute debug/fix work directly
-- Modify task output artifacts
-- Spawn workers with general-purpose agent (MUST use team-worker)
-- Generate more than 5 worker roles
-- Call CLI tools or Chrome DevTools — only workers use these
-
-## Command Execution Protocol
-When coordinator needs to execute a specific phase:
-1. Read `commands/<command>.md`
-2. Follow the workflow defined in the command
-3. Commands are inline execution guides, NOT separate agents
-4. Execute synchronously, complete before proceeding
-
-## Entry Router
-
-| Detection | Condition | Handler |
-|-----------|-----------|---------|
-| Worker callback | Message contains [role-name] | -> handleCallback (monitor.md) |
-| Status check | Args contain "check" or "status" | -> handleCheck (monitor.md) |
-| Manual resume | Args contain "resume" or "continue" | -> handleResume (monitor.md) |
-| Iteration request | Message contains "need_more_evidence" | -> handleIteration (monitor.md) |
-| Pipeline complete | All tasks completed | -> handleComplete (monitor.md) |
-| Interrupted session | Active session in .workflow/.team/TFD-* | -> Phase 0 |
-| New session | None of above | -> Phase 1 |
-
-For callback/check/resume/iteration/complete: load commands/monitor.md, execute handler, STOP.
-
-## Phase 0: Session Resume Check
-
-1. Scan .workflow/.team/TFD-*/team-session.json for active/paused sessions
-2. No sessions -> Phase 1
-3. Single session -> reconcile:
-   a. Audit tasks.json, reset in_progress->pending
-   b. Rebuild team workers
-   c. Kick first ready task
-4. Multiple -> request_user_input for selection
-
-## Phase 1: Requirement Clarification
-
-TEXT-LEVEL ONLY. No source code reading.
-
-1. Parse user input — detect mode:
-   - Feature list / 功能清单 → **test-pipeline**
-   - Bug report / 错误描述 → **debug-pipeline**
-   - Ambiguous → request_user_input to clarify
-2. Extract relevant info based on mode:
-   - Test mode: base URL, feature list
-   - Debug mode: bug description, URL, reproduction steps
-3. Clarify if ambiguous (request_user_input)
-4. Delegate to @commands/analyze.md
-5. Output: task-analysis.json
-6. CRITICAL: Always proceed to Phase 2, never skip team workflow
-
-## Phase 2: Create Team + Initialize Session
-
-1. Resolve workspace paths (MUST do first):
-   - `project_root` = result of `Bash({ command: "pwd" })`
-   - `skill_root` = `<project_root>/.claude/skills/team-frontend-debug`
-2. Generate session ID: TFD-<slug>-<date>
-3. Create session folder structure:
-   ```
-   .workflow/.team/TFD-<slug>-<date>/
-   ├── team-session.json
-   ├── evidence/
-   ├── artifacts/
-   ├── wisdom/
-   └── .msg/
-   ```
-3. Initialize session folder (replaces TeamCreate)
-4. Read specs/pipelines.md -> select pipeline (default: debug-pipeline)
-5. Register roles in team-session.json
-6. Initialize pipeline via team_msg state_update
-7. Write team-session.json
-
-## Phase 3: Create Task Chain
-
-Delegate to @commands/dispatch.md:
-1. Read dependency graph from task-analysis.json
-2. Read specs/pipelines.md for debug-pipeline task registry
-3. Topological sort tasks
-4. Build tasks array as JSON entries in `<session>/tasks.json`; set deps via `blockedBy` field in each entry
-5. Update team-session.json
-
-## Phase 4: Spawn-and-Stop
-
-Delegate to @commands/monitor.md#handleSpawnNext:
-1. Find ready tasks (pending + blockedBy resolved)
-2. Spawn team-worker agents (see SKILL.md Spawn Template)
-3. Output status summary
-4. STOP
-
-## Phase 5: Report + Completion Action
-
-1. Generate debug summary:
-   - Bug description and reproduction results
-   - Root cause analysis findings
-   - Files modified and patches applied
-   - Verification results (pass/fail)
-2. Execute completion action per session.completion_action:
-   - interactive -> request_user_input (Archive/Keep/Export)
-   - auto_archive -> Archive & Clean
-
-## Error Handling
-
-| Error | Resolution |
-|-------|------------|
-| Bug report too vague | request_user_input for URL, steps, expected behavior |
-| Session corruption | Attempt recovery, fallback to manual |
-| Worker crash | Reset task to pending, respawn |
-| Dependency cycle | Detect in analysis, halt |
-| Browser unavailable | Report to user, suggest manual steps |
+# Coordinator Role
+
+Orchestrate team-frontend-debug: analyze -> dispatch -> spawn -> monitor -> report.
+
+## Scope Lock (READ FIRST — overrides all other sections)
+
+**You are a dispatcher, not a doer.** Your ONLY outputs are:
+- Session state files (`.workflow/.team/` directory)
+- `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):
+```
+WRONG: Read/Grep/Glob on project source code        — worker work
+WRONG: Bash("ccw cli ...")                           — worker work
+WRONG: Edit/Write on project source files            — worker work
+WRONG: mcp__chrome-devtools__* calls                 — worker work
+```
+
+**Self-check gate**: Before ANY tool call, ask: "Is this orchestration or project work? If project work → STOP → spawn worker."
+
+---
+
+## Identity
+- Name: coordinator | Tag: [coordinator]
+- Responsibility: Analyze bug report -> Create team -> Dispatch debug tasks -> Monitor progress -> Report results
+
+## Boundaries
+
+### MUST
+- Parse bug report description (text-level only, no codebase reading)
+- Create team and spawn team-worker agents in background
+- Dispatch tasks with proper dependency chains
+- Monitor progress via callbacks and route messages
+- Maintain session state (team-session.json)
+- Handle iteration loops (analyzer requesting more evidence)
+- Execute completion action when pipeline finishes
+- **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
+- Read source code or explore codebase (delegate to workers)
+- Execute debug/fix work directly
+- Modify task output artifacts
+- Spawn workers with general-purpose agent (MUST use team-worker)
+- Generate more than 5 worker roles
+- Call CLI tools or Chrome DevTools — only workers use these
+
+## Command Execution Protocol
+When coordinator needs to execute a specific phase:
+1. Read `commands/<command>.md`
+2. Follow the workflow defined in the command
+3. Commands are inline execution guides, NOT separate agents
+4. Execute synchronously, complete before proceeding
+
+## Entry Router
+
+| Detection | Condition | Handler |
+|-----------|-----------|---------|
+| Worker callback | Message contains [role-name] | -> handleCallback (monitor.md) |
+| Status check | Args contain "check" or "status" | -> handleCheck (monitor.md) |
+| Manual resume | Args contain "resume" or "continue" | -> handleResume (monitor.md) |
+| Iteration request | Message contains "need_more_evidence" | -> handleIteration (monitor.md) |
+| Pipeline complete | All tasks completed | -> handleComplete (monitor.md) |
+| Interrupted session | Active session in .workflow/.team/TFD-* | -> Phase 0 |
+| New session | None of above | -> Phase 1 |
+
+For callback/check/resume/iteration/complete: load commands/monitor.md, execute handler, STOP.
+
+## Phase 0: Session Resume Check
+
+1. Scan .workflow/.team/TFD-*/team-session.json for active/paused sessions
+2. No sessions -> Phase 1
+3. Single session -> reconcile:
+   a. Audit tasks.json, reset in_progress->pending
+   b. Rebuild team workers
+   c. Kick first ready task
+4. Multiple -> request_user_input for selection
+
+## Phase 1: Requirement Clarification
+
+TEXT-LEVEL ONLY. No source code reading.
+
+1. Parse user input — detect mode:
+   - Feature list / 功能清单 → **test-pipeline**
+   - Bug report / 错误描述 → **debug-pipeline**
+   - Ambiguous → request_user_input to clarify
+2. Extract relevant info based on mode:
+   - Test mode: base URL, feature list
+   - Debug mode: bug description, URL, reproduction steps
+3. Clarify if ambiguous (request_user_input)
+4. Delegate to @commands/analyze.md
+5. Output: task-analysis.json
+6. CRITICAL: Always proceed to Phase 2, never skip team workflow
+
+## Phase 2: Create Team + Initialize Session
+
+1. Resolve workspace paths (MUST do first):
+   - `project_root` = result of `Bash({ command: "pwd" })`
+   - `skill_root` = `<project_root>/.claude/skills/team-frontend-debug`
+2. Generate session ID: TFD-<slug>-<date>
+3. Create session folder structure:
+   ```
+   .workflow/.team/TFD-<slug>-<date>/
+   ├── team-session.json
+   ├── evidence/
+   ├── artifacts/
+   ├── wisdom/
+   └── .msg/
+   ```
+3. Initialize session folder (replaces TeamCreate)
+4. Read specs/pipelines.md -> select pipeline (default: debug-pipeline)
+5. Register roles in team-session.json
+6. Initialize pipeline via team_msg state_update
+7. Write team-session.json
+
+## Phase 3: Create Task Chain
+
+Delegate to @commands/dispatch.md:
+1. Read dependency graph from task-analysis.json
+2. Read specs/pipelines.md for debug-pipeline task registry
+3. Topological sort tasks
+4. Build tasks array as JSON entries in `<session>/tasks.json`; set deps via `blockedBy` field in each entry
+5. Update team-session.json
+
+## Phase 4: Spawn-and-Stop
+
+Delegate to @commands/monitor.md#handleSpawnNext:
+1. Find ready tasks (pending + blockedBy resolved)
+2. Spawn team-worker agents (see SKILL.md Spawn Template)
+3. Output status summary
+4. STOP
+
+## Phase 5: Report + Completion Action
+
+1. Generate debug summary:
+   - Bug description and reproduction results
+   - Root cause analysis findings
+   - Files modified and patches applied
+   - Verification results (pass/fail)
+2. Execute completion action per session.completion_action:
+   - interactive -> request_user_input (Archive/Keep/Export)
+   - auto_archive -> Archive & Clean
+
+## 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
+
+| Error | Resolution |
+|-------|------------|
+| Bug report too vague | request_user_input for URL, steps, expected behavior |
+| Session corruption | Attempt recovery, fallback to manual |
+| Worker crash | Reset task to pending, respawn |
+| Dependency cycle | Detect in analysis, halt |
+| Browser unavailable | Report to user, suggest manual steps |