SafeVault v1.1.7

SafeVault v1.1.7

SafeVault v1.1.7 fixes tray menu actions that could appear to do nothing after
the local UI session token was replaced by a second UI process that failed to
bind port 8765.

What Was Fixed

• The UI now checks that its requested port is available before it replaces the
  registered session file.
• A failed UI launch can no longer overwrite the token belonging to an already
  running Recovery Home process.
• When the registered session is stale and the default port is occupied, the
  tray selects the next available local port, such as 8766.
• Open SafeVault opens Recovery Home with the active session token.
• Recent Deleted now opens the /deleted page directly instead of opening the
  home page.

Root Cause

A failed second UI launch wrote a fresh token to ui-session.json before
Uvicorn attempted to bind the requested port. When that bind failed because an
older UI already owned port 8765, the tray retained the unusable token and the
running UI correctly returned HTTP 403 for subsequent menu clicks.

Upgrade Notes

Windows users should install the new SafeVaultSetup.exe over v1.1.6. Existing
protected folders, recovery history, backup archives, storage location, Startup
choice, and storage budget remain unchanged.

After upgrading, restart SafeVault or restart Windows so the tray process uses
the new version. No protected files, recovery records, or content objects are
modified by this fix.