SafeVault v1.1.8

SafeVault v1.1.8

SafeVault v1.1.8 fixes tray menu actions that could start local UI processes
without opening Recovery Home or Recent Deleted in the browser.

What Was Fixed

• Tray readiness checks now use a lightweight authenticated /health endpoint
  instead of repeatedly loading the full database-backed dashboard.
• Open SafeVault reuses the active local UI session once it is ready.
• Recent Deleted opens the authenticated /deleted page without creating
  additional UI processes while a slow dashboard request is still running.
• On Windows, SafeVault falls back to the system default URL handler when
  Python's browser launcher reports failure.

Root Cause

The tray previously polled the full Recovery Home page every 200 milliseconds
while waiting for a new local UI process. Dashboard rendering performs database
and status work. When those requests exceeded the short readiness timeout, they
continued running in the UI process, while the tray treated the session as
unavailable. Repeated menu clicks could therefore start more UI processes and
never reach the browser-open step.

The new health endpoint verifies the per-session token but performs no vault or
database work, so readiness checks complete quickly without exposing protected
file information.

Upgrade Notes

Windows users should install the new SafeVaultSetup.exe over v1.1.7. 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
v1.1.8. The installer may close running SafeVault processes during the upgrade.
No protected files, recovery records, or content objects are modified by this
fix.