Feature Verify (test → find → fix → re-test)

Proves one feature works by actually exercising it, then fixes what fails. Loop until green — never report "it should work".

The loop

1. Define "working"

List the concrete checks before touching anything: the happy path, the main error path, and the edge cases that matter. Write them down as a checklist — that list is the definition of done.

2. Exercise it for real

Pick the cheapest method that proves reality:

• Backend/logic: run it — a unit test, a script, curl/Invoke-RestMethod against the dev server.
• UI/flow: drive the browser (Playwright, see e2e-testing) or ask the user to click while you watch logs.
• Data: query the DB after the action to confirm what was actually persisted.

Always start the app and confirm it boots clean (no console/server errors) before testing the feature itself.

3. Observe precisely

For each check record: expected vs actual, plus evidence (output, status code, screenshot, DB row). "Seems fine" is not an observation.