Run Flow Guide

Execute an existing guide from write-flow-guide against the product app in a real browser. The deliverable is the run file — every case ID accounted for with quoted screen evidence and, when the case touches server-owned state, a server-side probe that actually ran. A chat summary is not the deliverable.

The Iron Law

NO CASE IS TICKED ON THE SCREEN ALONE
A HUMAN TICK IS RECORDED, NEVER A VERDICT

If the case's Expect (or backend) touches state the server owns, the run block carries both saw (quoted UI) and server (probe + result) before verdict: pass; pure presentation records server: none — presentational. (Rationalizations below name every excuse for skipping this; Red Flags name the Chrome-ticking trap.) Probe ladder (strongest first): the UI's own request/response → read-back through the app's API → store peek (DB/file/cache) → reload/restart for durability. A red console error or 5xx fails the case even when the screen looks right — never invent a probe result you did not run.

CLI (required for progress)

Resolve the write-flow-guide skill root (skills/acceptance/write-flow-guide in this monorepo, else the installed package path). Every subcommand takes the one run file — cases and verdicts live in it together: