max / makenotwork

Scope the server's mutation runs by blast radius Unscoped this crate generates 9,766 mutants and each re-runs the suite, so a pass is about six days of machine. It has consequently never completed once, which meant no mutation data at all for the largest thing we ship. 2,610 now. Ordered money, then user data, then the security boundary. A survivor is a line whose behaviour no test observes, so the question is where we can be wrong without finding out, and that matters most where being wrong costs a creator money or their files. Only files that already have tests. Mutating an untested file reports every mutant as a survivor, which buries the real findings and answers a question grep answers for free. 50 files in the money and user-data groups have no test at all, among them db/transactions/purchases.rs at 1,375 lines, db/users.rs at 1,269 and routes/stripe/webhook/checkout.rs at 1,024. db/subscriptions.rs looks tested and is not: its only `#[cfg(test)]` is a test-only constructor. Those are a coverage gap to close rather than a mutation result to compute.