Validate .NET checks with mutations

The target is the test oracle. One detected mutation shows sensitivity to that defect, not complete correctness.

Establish scope and baseline

Read the requested properties, actual assertions, build configuration, and test command. Reconstruct missing catalog entries from code, marking the restricted scope.

Confirm the mutation scope, time or execution budget, and whether fixes are authorized. Reuse existing authorization. Do not request the same decision repeatedly.

Run the intended tests against the unchanged source snapshot. Record revision, dirty changes, SDK/runtime, package versions, command, test count, and failures.

Stop on a baseline correctness failure. A skipped, undiscovered, or unexercised test does not establish a green baseline.

Choose the execution method

Read mutation execution and verdicts.