release: 0.6.4

[vibesoftwarecoder]

Cuts 0.6.4. version.txt 0.6.3 → 0.6.4, plus the hand-written notes the release workflow reads.

No code changes — both shipping commits already merged: 98b5cfa (#46, the installer no longer destroys host configuration) and 459f88d (#47, the documentation that claimed it could not).

Why this one is worth cutting

Installing from a release zip deleted everything in the install directory before copying the new build in — appsettings.json and appsettings.local.json included, with no backup and no warning. Every host-local setting was lost silently.

It included the file the docs recommend because a deploy cannot overwrite it. True of a source build; false of the zip install, which is how almost everyone upgrades.

⚠️ A correction the notes carry

PR #46 and its commit message said the fix was "not retroactive" and would protect only the upgrade after the one carrying it.

That is wrong. The installer that runs during an upgrade is the one inside the release just downloaded, not the one already on the machine — the documented command runs .\scripts\install-service.ps1 from the extracted folder. So upgrading 0.6.3 → 0.6.4 uses 0.6.4's installer, and configuration is preserved.

The only gap is running an installer from an older extracted copy against this zip.

Getting that backwards understates the release: it is not insurance for some future upgrade, it protects the one the user is about to perform. The notes say so explicitly rather than leaving the earlier claim standing.

Verified against a real upgrade

before  appsettings.json       E7AC4C57508AF9BF  1579 bytes
after   appsettings.json       E7AC4C57508AF9BF  1579 bytes
before  appsettings.local.json 60CC6361B5C0EB1F    81 bytes
after   appsettings.local.json 60CC6361B5C0EB1F    81 bytes

A deliberately edited MaxSeats survived; a deliberately removed setting was correctly reported as newly added by the release.

Known limitations, carried forward

The notes restate the three that are still true: seats capture the RDP surface rather than a dedicated virtual display, a streaming seat still reports Ready (#43), and MoonlightVibe seat discovery is fixed but not yet in a release of that client.

Once merged, pushing v0.6.4 publishes. The workflow refuses a tag that disagrees with version.txt.

🤖 Generated with Claude Code

https://claude.ai/code/session_01SQvL62WkT8xDWXqyjFCGDw