Fix a mutation accidentally captured in the previous commit
f4d5659d landed with StatValidation's OptimalTemperature-bounds check replaced by
`if (false)`: the mutation harness was running concurrently against this same file
and a `git add`/`git commit` caught it mid-mutation. Restores the real check. Caught
because the harness's own "not yet reached" scars in doctrine are what prompted a
by-hand recheck of the just-committed diff rather than trusting the terminal output
that said 80/80 green a moment earlier.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
f4d5659d99
commit
7204259ac3
3 changed files with 140 additions and 55 deletions
|
|
@ -702,7 +702,7 @@ public static class StatValidation
|
|||
throw new InvalidOperationException(
|
||||
$"{data.Name}: MinimumTemperature and MaximumTemperature are both {data.MinimumTemperature} -- a " +
|
||||
"zero-span range is dead at every temperature, which is an authoring error, not an authored immunity");
|
||||
if (false)
|
||||
if (data.OptimalTemperature < data.MinimumTemperature || data.OptimalTemperature > data.MaximumTemperature)
|
||||
throw new InvalidOperationException(
|
||||
$"{data.Name}: OptimalTemperature {data.OptimalTemperature} lies outside its bounds " +
|
||||
$"[{data.MinimumTemperature}, {data.MaximumTemperature}]");
|
||||
|
|
|
|||
Loading…
Reference in a new issue