Prove It Works

Before you claim a change is done, produce evidence. Don't say "this works" — show it working.

1. Name the claim. State exactly what the change is supposed to do, in one sentence.
2. Pick the shortest path that exercises it end to end — run the command, hit the endpoint, call the function, click the flow. Prefer the real path over a test that stands in for it.
3. Run it and capture the actual output: command, exit code, logs, response body, or screenshot. Paste the real result, not a paraphrase.
4. Point to the line in the output that proves the claim. Explain why it confirms the behavior.
5. Exercise at least one edge or failure case — empty input, error path, boundary value — and show what happens.
6. If you cannot run it, say so plainly and list exactly what you did verify (types compile, tests pass) and what remains unproven.
7. Never present expected output as if it were observed. Label anything you did not actually run.