Installer honesty, continued. An adversarial review of the v0.35.1 packaging fixes found four real defects — two of them introduced by v0.35.1 itself. The app is unchanged; like v0.35.1, this release is entirely about installing and building.
Fixed
An install that needs a restart no longer claims it failed. Windows returns a distinct "installed, but restart to finish" result when it had to replace files that were in use. v0.35.1 reported that as FAILED — nothing was changed, which was untrue, and never mentioned restarting — leaving you free to launch a half-replaced app. It now confirms the install succeeded and tells you to restart before launching ROAR.
The build could delete the installer package it had just made. The v0.35.1 rule kept the two newest packages, which quietly discarded a freshly built one whenever two newer versions were already present — building an older version to reproduce a bug, for instance — while still printing "built" and reporting success. The version being built is now always kept.
The version stamp is written next to the build recipe rather than wherever the build was started from, so it can neither go missing nor be stamped from a stale copy.
Upgrading
Upgrading in place from v0.35.1 works normally. If you are on v0.34.0 or earlier and an update appears to do nothing, uninstall ROAR from Settings → Apps first, then run this installer. Your data is safe either way — settings, licence, history, snippets and vocabulary live outside the program folder and are never touched by install or uninstall.
Your existing licence and any trial in progress carry over untouched.
Full changelog: https://github.com/xhan145/roar/blob/main/CHANGELOG.md