code-change-verification

Run format, lint, mypy, and tests by executing the verification sequence from the repository root. This stack validates formatting, linting, typing, and tests to catch regressions and compile-time errors before merging code changes.

Enforce the verification stack when changes impact runtime code, tests, or build and test behavior. It applies to pull requests and commits touching runtime code, tests, or CI configuration to ensure baseline quality.

The mandatory code change verification process includes running format, lint, typing with mypy, and tests. It surfaces clear failure messages when any step fails, ensuring changes pass format, lint, and tests.

No external CI configuration is required to run the verification locally. The sequence executes format, lint, mypy, and tests via provided scripts or targets directly from the repository root to validate code changes.

Code change verification fails when formatting, linting, mypy typing, or tests encounter errors. The sequence surfaces clear failure messages for any step that fails, highlighting the specific issue preventing validation.