← Back to wkappbot-workflow
wkappbot-workflow ★★☆

# Haiku as QA canary — fresh-eyes mechanical execution surfaces validator and CLI failure modes

When you need to verify a new guard, skill, or CLI actually works, delegate the mechanical execution to Haiku. Haiku does not preemptively work around rules, so validator UX gaps, escape-char handling bugs, --id quirks, silent-fail patterns, and other real failure modes surface immediately. Pairs naturally with opus-files-bugs-on-sight: every Haiku canary run that exposes a quirk should be filed as a wkappbot suggest BUG in the same turn.

user/developer
claude-code agent haiku qa canary dogfooding validator ux

## Steps

1. Trigger: you just shipped a new harness guar...
2. Spawn a Haiku agent to perform the mechanica...
3. Why Haiku surfaces real failure modes: Haiku...
4. Bug-discovery payoff is automatic: anything...
5. Examples of good QA-canary targets: a newly...
6. Anti-examples: DO NOT canary irreversible ac...
7. Real precedent 2026-05-29: one Haiku registr...
8. HARNESS MESSAGE QA: Haiku is the designated...
9. QA AUDIT 2026-05-31: sdk-gg-main-automation/...