# Verification procedure and evidence

Run `./scripts/verify.sh` from a development environment with Python 3.12 and Docker. It is a
fail-fast executable contract that runs formatting, lint, strict typing, all automated tests,
a production image build, container startup/readiness, and create/list API smoke tests. The
individual commands are documented in `README.md` for environments without Docker.

Expected test evidence includes: CRUD and stable 404/422 bodies; 100 concurrent creates; atomic
update/status interleaving; on-demand status persistence; DNS rejection before transport;
redirect target revalidation; and query/credential log redaction. Outbound calls are mocked.

Generation environments do not necessarily expose a shell or Docker daemon. A committed script
is not itself a claim that it ran: consumers should preserve the actual command output in CI.
The architectural limitation remains that state is ephemeral and unique to one process, so the
container command intentionally selects one worker.