Switchyard Testing and CI

Overview

Pick the smallest local gate that is genuinely equivalent to what CI will run, then map failures to targeted fixes. The two goals — move fast locally, never report a green run weaker than the CI gate you are claiming — usually conflict; this skill resolves that conflict from the current diff rather than from memory.

If your change also touches code you have not yet read, run switchyard-codebase-exploration first so the validation set covers the real impact, not just the diff surface.

Rust crates under crates/ (switchyard-core, switchyard-translation, switchyard-components, switchyard-server, switchyard-py) are active on the Rust core branch. For Rust-touching diffs, include cargo fmt --all --check, cargo clippy --workspace --all-targets -- -D warnings, and the smallest trustworthy cargo test scope; use cargo test --workspace before calling a broad Rust MR ready.

Quick Reference