mutation-testing

# Mutation Testing — Campaign Configuration (mewt/muton) > **Note**: muton and mewt share identical interfaces but target different languages — mewt for general-purpose languages (Rust, Solidity, Go, TypeScript, JavaScript), muton for TON smart contracts (Tact, Tolk, FunC). All examples use `mewt` commands, but they work exactly the same with `muton`. File names change accordingly: `mewt.toml` → `muton.toml`, `mewt.sqlite` → `muton.sqlite`. ## When to Use Use this skill when the user: - Mentions "mewt", "muton", or "mutation testing" - Needs to configure or optimize a mutation testing campaign - Wants to run `mewt run` and needs help getting set up first ## When NOT to Use Do not use this skill when the user: - Wants to analyze or report on completed campaign results - Asks about tests or coverage without mentioning mutation testing --- ## Quick Start Load [workflows/configuration.md](workflows/configuration.md) — a 5-phase guide from `mewt init` to a validated, ready-to-run campaign. **General question or unfamiliar command?** Run `mewt --help` or `mewt <subcommand> --help`, then assist. --- ## Reference Index | File | Content | |------|---------| | [workflows/configuration.md](workflows/configuration.md) | 5-phase guide: init, scope, optimize, validate, run | | [references/optimization-strategies.md](references/optimization-strategies.md) | Per-file targeting, two-phase campaigns, mutation type filtering | --- ## Essential Commands ```bash # Initialize and mu...