What problem does it solve? Verifying changes to the Rust multisig SDK requires coordinated manual testing across multiple cosigner sessions, GUARDIAN server endpoints, and Miden networks, which is error-prone without a structured workflow. This Skill provides a repeatable smoke-testing procedure that maps code changes to the minimal workflow that proves the behavior. ## Core Features & Use Cases - Workflow Selection Matrix: Maps changed code areas (account creation, cosigner sync, proposal lifecycle, offline export/import, state verification, key recovery) to the smallest canary workflow that validates them. - Multi-Target Deployment Testing: Supports smoke runs against local dev, staging (devnet), and production (testnet) GUARDIAN endpoints, including scratch-project testing of published crate versions. - Timing Baseline Comparison: Records elapsed time per blocking operation and compares against a reference baseline to flag regressions beyond 2x or 60 seconds. - Use Case: After modifying proposal signing logic in crates/miden-multisig-client, run the add-cosigner canary with three demo sessions to verify create, sign, execute, and post-execution sync still pass with acceptable timings. ## Quick Start Ask the AI to smoke test the Rust multisig SDK after your recent changes, specifying the target environment and signature scheme.
