flowchad-runner

Verify named FlowChad flows with Playwright/Navvi, capture per-step screenshot + video evidence, auto-switch to Navvi on CAPTCHA, upload evidence (best-effort), then post results to GitHub and write a local report. Each stage runs as a focused subagent with isolated context. The ICM win here is clean stage contracts + resumability, NOT parallelism: flows CANNOT run concurrently because they share browser, session, and persona state and would collide. Stage 03 walks flows one at a time in a sequential loop.

When to Use

• Explicit pre-merge verification for a PR that affects declared flows
• Production verification after deployment
• Weekly or scheduled critical production smoke runs
• Manual local diagnosis when local CAPTCHA behavior is explicitly configured

When Not to Use