Contributing: Validation

Required local validation flow and engineering quality gates for contributor changes.

Contributor changes are expected to follow gate-driven validation with targeted tests first, then broader suite checks.

Default Local Runner Policy

Context	Recommended command
Full local suite	`cargo nextest run`
Targeted integration lane	`cargo nextest run —test vm` (or relevant target)
When `cargo test` is needed	Use only when behavior depends on `cargo test` semantics.

Core Validation Pipeline

Shell

  $ cargo nextest run  $ cargo nextest run --test cpython_harness  $ cargo nextest run --test differential_cpython  $ cargo nextest run --test fuzz_parser_vm  $ scripts/run_builtin_parity_gate.sh  $ scripts/run_coverage_gate.sh

Gate Expectations

Gate	Expectation
Semantic parity	Tests must encode CPython behavior, not current PYRS quirks.
No quick-fix substitution	Root-cause fixes are required for core interpreter/runtime paths.
Temporary workaround tracking	Any temporary path must be justified in code/tests and removed once the owning regression or probe is covered.
Checkpoint discipline	Keep changes in small, focused commits with tests/docs updated together.

Optional Tooling

Shell

$ ./scripts/bootstrap_dev_tools.sh

Canonical Internal References

docs/README.md
docs/DEVELOPER_TOOLING.md
docs/COVERAGE_GATE_POLICY.json
docs/BUILTIN_PARITY.md