-
cargo fmt --all(CI runsrustfmt --checkandclippy -D warnings) - Scoped release build of the crates touched:
cargo build --release -j 32 -p <crate> -
cargo test -p <crate>passes (cargo checkis not sufficient — test code is interleaved with production code) - ES-YAML conformance suite at 0 failed (
cargo run --release -p es-yaml-runner -- --dir tests/es-compat-yaml/yaml), or: not applicable because this change is docs/landing-only - New ES-compatible behaviour has a matching YAML case under
engine/tests/es-compat-yaml/yaml/ - Docs updated if user-visible behaviour changed
- For non-trivial changes: the applicable audit in
docs/CONTRIBUTION_REVIEW.md - For non-trivial changes: if this PR changes an operational document or runnable recipe, complete the operational audit in
docs/CONTRIBUTION_REVIEW.md. Record a negative control that exits non-zero with no artifact extracted, installed, published, or served. Keep verification and its action in one block; rerun the control with the failing exit discarded and with the next documented block appended, and require that neither reaches an artifact or unsafe/privileged path. List tested variants and unsupported variants separately, and verify every publication copy. Otherwise mark this itemN/Awith a reason.
Not run:
- Written by:
- Verified (commands run, output observed):
- Assumed (not tested, and what would falsify it):