guardian-validation-matrix

Classify the changed layer first, then run the package-local checks mapped to that layer, such as cargo test -p guardian-server for server code. Expand to broader checks only when the change touches contracts, auth, or cross-layer behavior.

Run workspace-wide tests only when multiple packages across Rust and TypeScript were edited, targeted checks failed suggesting wider fallout, or the task explicitly requests a broad verification sweep. Otherwise prefer package-local test commands.

For packages/guardian-client changes, run npm test and npm run build inside that package. For the TypeScript multisig SDK, run the same commands in packages/miden-multisig-client, adding upstream example smoke checks when behavior is user-visible.

No. When a lower-layer change is observable in examples/demo or examples/smoke-web, add a manual smoke run such as cargo run -p guardian-demo or the browser smoke-test skill. Unit tests do not replace example smoke checks for user-visible behavior.

Combine the relevant package-local commands for both layers and validate at least one upstream consumer, such as an example smoke test. Document any coverage you intentionally skip with a reason rather than implying it was unnecessary.