v0.2.2

Clear a slot

Freeing a live slot used to mean extracting it and then deleting the files by hand, which
is exactly the moment to delete the wrong one. Clear slot does it from the app -- the
toolbar, or right-click any live slot -- and before it does, it goes looking for the most
recently made copy of that slot in the vault and compares its play time with the live
save's.

If the live save is further on, or if the vault has no copy of the slot at all, the
confirmation says so and asks again, because that gap is precisely what clearing would
cost you. The live folder never counts as its own backup, even when it is catalogued in
place -- that would answer "backed up" by pointing at the very save about to be deleted.

Like every other write, the live state is auto-snapshotted first, so Undo brings the
slot straight back.

Xbox / Game Pass clears the same way: the containers.index record is kept and flagged
Deleted, as the Xbox app itself does, so the cloud copy is told to go rather than being
re-synced back down -- and writing into the slot again un-deletes it.

On the command line: nmsvault clear <slot> [--yes].

Downloads

Platform	File
Windows	NMSSaveVault-Setup-v0.2.2.zip
Linux / Steam Deck (x86_64)	NMSSaveVault-v0.2.2-linux-x86_64.tar.gz
macOS (Apple Silicon)	NMSSaveVault-v0.2.2-macos-arm64.tar.gz

Windows: extract and run NMSSaveVault.exe, or run install.bat to put it on the Start
Menu. Installing over an older version keeps your config.

The Linux and macOS kits are still untested on real hardware -- the save format is
identical on all three platforms, so what is unproven is the packaging and the game
detection, not how saves are read or written. Reports welcome either way.

NMSSaveVault.exe is a verbatim renamed copy of the Authenticode-signed CPython
pythonw.exe, so Windows raises no unknown-publisher warning. That is the Python
runtime's own signature, not a signature over this project's code.