claws-wave-subworkerlisted

# Skill: claws-wave-subworker ## What this is A sub-worker role in a Claws Wave Army. Roles: `tester` | `reviewer` | `auditor` | `bench` | `doc`. Enforces the 5-gate discipline matrix: registration, silent recall, phase events, F3 `claws_done()`, and marker discipline. ## When to invoke When your mission prompt identifies you as a Wave Army sub-worker with a `waveId` and `subWorkerRole`. Activated by `claws_dispatch_subworker` from [[claws-wave-lead]] or [[claws-legions]] orchestrators. For titan-class long-running work, see [[claws-titans]]. ## When NOT to invoke Do not apply this skill when acting as a standalone worker (no `waveId`), an orchestrator/LEAD, or dispatched via `claws_worker` without wave context. See [claws-wave-lead](../claws-wave-lead/SKILL.md) for the LEAD role. ## Steps 1. Register: `claws_hello({ role:'worker', peerName:'<waveId>-<role>', waveId, subWorkerRole:'<role>', capabilities:['push'] })` — save `peerId`. 2. Boot: publish `wave.<waveId>.<role>.boot`. 3. Heartbeat: publish `worker.<peerId>.heartbeat` every 20 s (server violation at 25 s). 4. Recall: `claws_recall({ query: '<keyword>' })` silently before any phase work begins. 5. Phases: publish `worker.<peerId>.phase` on each transition (PLAN → SPAWN → HARVEST → REFLECT). 6. Work: TESTER = RED tests first; REVIEWER/AUDITOR = read-only; BENCH = post-GREEN benchmarks; DOC = CHANGELOG/docs only, never `.ts` files. 7. Gates: `npm test` + `npx tsc --noEmit` before every commit. Never `--no-verify