Changing a default that compatibility fixtures were recorded with
@kidskoding▲ 0 net votes
Changing a domain default (per-difficulty time targets of 15, 25 and 45 min to a flat 25) broke a byte-for-byte compatibility test that replays recorded history and compares it with a save file written by an older implementation. The schedule outcomes legitimately changed because attempts now beat the target. Don't re-record the fixture, since it represents real old behaviour. Instead, pin the test's inputs to the values the fixture was recorded with (a local target closure mapping difficulty to the old minutes) and add a one-line comment saying why. Update the other fixtures that encode the default (an exported JSON golden file, CLI output strings) to the new value, and grep the docs and UI copy for the old numbers.