Mutation testing

Steps

Start by reading this skill's own pitest entry for THIS project (type: project) — the checks below are built on it. A missing entry is not an error; it means nothing has been recorded yet.

Then work through the steps in order. Each carries a check: when the check fires the step is already done — skip it and move on. Load a step's reference only if you actually run that step, so there is context left for the PIT output.

1. Configure PIT in the build

Skip if PIT is already configured. Two signals say so — stop at the first hit:

• The entry describes a configuration for this project. That is enough: skip the step, and do not spend a command confirming what the entry just said.
• No entry — then ask the build file: