Debugging case / Oct 7, 2026

Saved successfully. Still refusing to leave.

Native candidates could save and then hang or crash during teardown or a late activation after a minimized session.

The symptom

Native candidates could save and then hang or crash during teardown or a late activation after a minimized session.

What was tried

Failed builds, close traces and controlled comparisons were retained. A timer guard was followed by a separately tested post-commit activation guard.

What the evidence supports

CH records three ordinary exact-candidate exits, clean logs and all fifty-nine original profiles restored. The older failures were not rewritten as passes.

The lesson

Test the released bytes, normal shutdown and cold reopen. One clean exit does not close an intermittent bug.

CH release checks passed; broader stability remains ongoing

Evidence & perspective

  • CE: the game needed to know when to leave · 2026-10-06 · Release acceptance and publication records

    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 · 2026-10-07 · Release acceptance, live link rechecked October 8

    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.