heimdall-rust-test-runnerlisted

# Heimdall Rust Test Runner Use this skill for verification work in the Heimdall repo. ## Trigger guidance - Use it when the task asks to run tests, validate a change, or choose the right Rust or UI verification command. - Prefer it after meaningful Rust edits and before handoff on non-trivial changes. - Do not use it for code review-only requests that do not require running checks. ## Suite selection Choose the narrowest useful command first: | Changed files | Command | | --- | --- | | `pricing.rs` | `cargo test pricing -- --nocapture` | | `scanner/` | `cargo test scanner -- --nocapture` | | `oauth/` | `cargo test oauth -- --nocapture` | | `server/` | `cargo test server -- --nocapture` | | `config.rs` | `cargo test config -- --nocapture` | | `webhooks.rs` | `cargo test webhooks -- --nocapture` | | `agent_status/` | `cargo test agent_status -- --nocapture` | | `main.rs` or `cli_tests.rs` | `cargo test cli_tests -- --nocapture` | | `optimizer/` | `cargo test optimizer -- --nocapture` | | `scheduler/` | `cargo test scheduler -- --nocapture` | | `hook/` | `cargo test hook -- --nocapture` | | `classifier.rs` | `cargo test classifier -- --nocapture` | | `watcher.rs` | `cargo test watcher -- --nocapture` | | `src/ui/` or TS-only changes | `./node_modules/.bin/tsc --noEmit` | | Multiple modules or unclear scope | `cargo test -- --nocapture` | ## Required workflow 1. Identify the changed surface from the diff or user request. 2. Run the targeted suite first for fast feedback.