The problem
Some native candidates saved, then hung or crashed while closing.
The choice
Retain failed candidates, investigate the actual failing path and require repeated ordinary exits on the exact release candidate.
Why this direction
A forced process stop cannot establish a repaired shutdown or a safe release.
What it changed
CE addressed timer reentry; CH later addressed post-commit activation. The accepted runs also restored all protected profiles.
Later revisions
Finite tests remain scoped. They do not guarantee all future crashes are solved or establish a hardware root cause.
Evidence & perspective
- CE: the game needed to know when to leave
CE records eight ordinary exits, including three exact-package checks, and preservation of 59 real profile files. A later activation fault required another repair before CH. Earlier failed candidates remain failures.
- CH: four original buildings reach the public county
CH contains four original exteriors, reuses five scoped building routes, and passed three normal candidate exits with 59 profile files restored. The current Windows download was checked for its exact published size. These are bounded PC checks, not minimum-spec or whole-game acceptance.