v1.12.0: file association repair

Fixes a serious file-association bug: please upgrade

.bat and .cmd stopped running. FATE registered them like any other code type, and for these two that alone is destructive: their handlers open with "%1" %*, where the script is the executable. As soon as a second handler appears in the type's "Open with" list and no explicit user choice exists, Windows stops running the script and shows "Pick an app" instead. Setting FATE as the default on its own Default-apps page then made it unrecoverable, because that picker has no "Windows Command Processor" to select.

FATE now refuses to register either type. The repair happens during install: the per-machine entries a previous version wrote need elevation, so upgrading is what actually restores your batch files. Both types still open in FATE from the Open dialog, drag & drop and Edit in FATE.

"Claim file types" was breaking the types it claimed. Writing a per-user class default does not make an app the handler on Windows 11, and it suppresses the rule that does work. 39 of 41 claimed types were left with no handler at all, while the counter reported them as won. The counter now resolves each type through the shell instead of guessing, and a Repair button undoes the damage. On the author's machine: 29 working types before, 59 after.

Also in this release

• Quitting with unsaved work now offers Save / Don't save / Cancel, per tab, instead of discard-or-nothing.
• Turning off "reopen last session's tabs" now clears the stored list rather than just ignoring it.
• A file you open explicitly is no longer robbed of focus by tabs restoring behind it.
• PowerShell helpers run with -WindowStyle Hidden, which should settle the console window that occasionally blinked at launch.

Full detail in the changelog.