Malte Langkabel
cb5572ffdd
The scripted session only placed buildings, so every unlock container stayed at its initial value for the whole run and the checksum never saw them change. It now destroys the enemy stations twice and takes the offered schematic choice, so awarded groups, per-schematic levels and the derived recipe/item sets are exercised too. Adds a test that pins down that unlock state actually reaches the checksum: two sessions in lockstep, one takes the choice, checksums must diverge. The scripted-session tests cannot show this themselves — they compare runs against each other, so they pass whether or not UnlockState is in the fold. Verified by temporarily removing the fold: the new test fails, the old two do not. The first choice is asserted rather than assumed, so a config change that stops offering a group fails loudly instead of silently dropping the coverage. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YHcUerKAZKWNvSKJxYKbnG