Verify the result

Verification connects a claim to evidence. The agent’s summary is a list of claims, not proof that the work is complete.

Match every important claim to a check:

Claim	Useful evidence
The input rule works	Focused behavior tests at the boundaries
The application still integrates	Relevant suite and production build
The error is clear and visible	Browser check at relevant sizes
This API exists in our version	Installed types or code plus primary documentation
No unrelated code changed	Changed-file list and focused diff review

One check rarely proves everything. A type check does not prove authorization. A build does not prove the page looks right. One happy-path browser click does not prove failure handling.

Inspect the actual evidence

Read the test output, not just tests passed. Open the page, not just the screenshot filename. Inspect the changed files and diff, not just the agent’s description of them.

Look for scope drift: new dependencies, generated files, formatting churn, unrelated refactors, or behavior outside the request. A change can work and still be too broad.

Try a negative case

Happy paths often work first. Exercise one failure, boundary, or abuse case that matters. For display-name validation, send an empty value and 51 characters. For authorization, try to access another user’s record.

Negative cases reveal whether the system fails safely and whether the requirement exists at the correct boundary.

Report what was not verified

A useful completion report contains:

Changed: server-side display-name validation
Evidence: focused request tests, full API suite, production build
Negative case: empty and 51-character names rejected
Diff scope: route and request test only
Not verified: browser error message, which is outside this step

An honest limitation such as the payment sandbox was unavailable is valuable. It tells the next reviewer what risk remains. Everything works without matching evidence hides that risk.

The amount of verification should match the cost of failure. A typo needs less evidence than a payment or access-control change.