validate-change

# Validate a Change ## Companion Guidance Use `karpathy-guidelines` alongside this skill for implementation or review work. Keep changes scoped, surface assumptions, and define focused validation before editing. Use this skill to choose the smallest validation set that still covers the surfaces touched by a change. ## Mandatory Rules - Format changed files with the language-native formatter before the final lint/test pass. - If any Rust code changed, always run `just test-rust`. - If any Rust code changed, also run `cargo fmt --all`. - If any Rust code changed, also run `cargo clippy --workspace --all-targets -- -D warnings`. - If `crates/core` or `crates/adaptive` changed, run the full matrix across Rust, Python, Go, and Node.js. - If a language surface changed, always run that language's test target even when Rust core did not change. - If dynamic plugin behavior changed, use `maintain-dynamic-plugins` and include the native SDK, worker protocol, Python SDK, docs, packaging, and Codecov surfaces in the validation plan. - If code changes alter APIs, bindings, commands, paths, packaging behavior, observability/adaptive semantics, or documented best practices, update any dependent maintainer or consumer skills in the same branch. - During iteration, prefer `uv run pre-commit run --files <changed files...>`. - Before review or handoff, run `uv run pre-commit run --all-files`. ## Start With The Change Shape - **Core runtime or shared semantics changed** Us...