If a flow breaks, the check goes red
The merge stops and no demo goes out. What you get is the frame where it broke, and the few before it.
Clicks through the real thing, end to end
Tada opens the deployed build in a real browser and walks the flow the PR claims to ship.
A flow is a few plain steps, like "click Pay", then "the receipt shows", committed with the PR as .tada/flows/<feature>.md. No test suite.
It stops the merge the way CI does
Tada posts a status check on the PR. Mark it required in branch protection and a failed run stops the merge, the same mechanism your CI already uses. It stops merges, not deploys, and you can always override.
We treat a false block as a bug, not a footnote. Tada only blocks when a step actually failed on a real run, and the frames are attached, so you can see for yourself.
Stop shipping code no one ran.
Tada opens every feature your agent ships, works through it like a QA engineer would, and stops a broken one before anyone sees it.
See the whole product