End-to-end flow verification

Reading the code tells you what you wrote. It does not tell you what the user gets. The work is not complete until you have driven it.

The rule

Never declare work complete based on reading code. Completion requires direct verification of the rendered interface and the full user journey. Unit tests and implementation-level assertions are evidence about units, not about the feature.

Drive the real interface with Playwright or a computer-use agent, as a user would: click the things a user clicks, type what a user types, wait how long a user waits.

1. The happy path, as a user