Build a .NET feature workload

Start with a completed or developing feature. Produce executable checks that call its real implementation, plus a record of what they establish.

Workflow

Read the feature, nearby tests, project files, package versions, and test commands. Preserve the repository's framework and SDK.
Identify concrete invariants, input boundaries, failure outcomes, and important reachable states.
Separate implemented behavior from planned behavior. Do not disguise an unimplemented requirement as a passing or silently skipped test.
Read runtime semantics. Reuse deterministic tests when they cover the contract. For generated cases, select an existing generator or a compatible FsCheck or Hedgehog version.
Construct legal domain values through supported constructors. Keep invalid raw input separate to test parsing failures.
Build operations, independent expected results, and explicit reach observations. Ensure the workload invokes production code.
Use real external dependencies where their behavior is part of the property. Preserve the existing host or container setup.
Run a bounded local workload. Record executed cases, rejected cases, reached states, failures, and replay data.
Diagnose an unreached state before changing an invariant. Confirm whether a failure belongs to the feature, generator, oracle, or environment.

Check safety invariants at each relevant observation. For progress, record the triggering operation and verify completion within the stated bound.