claws-wave-leadlisted

## What this is The LEAD role in a Claws Wave Army. Owns the diff, commits, PIAFEUR loop, and final lifecycle call. Dispatches sub-workers via `claws_dispatch_subworker`, monitors them per-worker (not per-wave), and drives the wave to completion. ## When to invoke - Mission identifies you as LEAD or wave orchestrator. - Fan out ≥2 parallel sub-workers and aggregate results. - An auto-engine or titan escalates to a wave army (see [[claws-auto-engine]], [[claws-titans]]). ## When NOT to invoke - You are a sub-worker — use [[claws-wave-subworker]] instead. - Task is single-worker — use `/claws-do` or `claws_worker` directly. - Inside a titan's internal wave — the titan owns its LEAD. ## Steps **Boot:** 1. `claws_hello({ role:'orchestrator', peerName:'<waveId>-lead', waveId, subWorkerRole:'lead' })` 2. `claws_wave_create({ waveId, manifest:[roles...] })` 3. Publish `wave.<waveId>.lead.boot` **Dispatch + Monitor — lock-step, never batch:** ``` r1 = claws_dispatch_subworker({ waveId, role:'tester', mission:'...' }) Monitor(command=r1.monitor_arm_command, timeout_ms=3600000, persistent=false) r2 = claws_dispatch_subworker({ waveId, role:'reviewer', mission:'...' }) Monitor(command=r2.monitor_arm_command, timeout_ms=3600000, persistent=false) ``` Arm Monitor immediately after each dispatch — never batch-dispatch then arm. Use `claws_dispatch_subworker`, never manual `claws_create + claws_send` chains. **PIAFEUR:** Plan → Implement → Audit → Fix → Evaluate → Update → Repeat