v0.6.0

What's Changed

Added

• Security modes — choose on first launch how the encryption key is protected: a master
  password (default), the OS keyring on macOS and Windows, or a local KEK file with user-only
  permissions. The mode can be changed later in Settings → Security…; switching modes
  re-encrypts all saved secrets in one transaction.
• Keyring integration on macOS and Windows via Latchkey. Linux supports the master-password
  and local-key-file modes.
• Reset secrets in the security settings removes saved connection passwords and the AI API
  key, then lets you choose a new security mode.
• Existing master-password installations are detected automatically and keep working without
  re-entering secrets.
• Connection test feedback — show a localized running status immediately and disable
  Test until the request finishes. Results include a success/error label and error details;
  successful tests are green and errors are red.

Changed

• Unlock secrets (F8) and Change master password (Ctrl+P) are available only in
  master-password mode.
• Testing a connection no longer requires or fills in a profile name; a name is still required
  when saving. Connection strings and SSH settings remain validated.
• Connection tests are cancelled after 10 seconds, with a localized timeout message and
  Test enabled again.

Fixed

• Automatic unlock validates the key against every stored connection password and AI API key
  before accepting it or migrating legacy credentials; a mismatched key leaves secrets locked.
• Resetting secrets also removes passwords embedded in legacy connection URIs. Connection forms
  strip URI credentials even when separate login/password fields are already populated, keeping
  explicitly entered values and filling missing fields from the URI.
• Connection form errors and test results appear below all fields and above the action buttons,
  without overlapping authentication options. Status changes repaint without another keypress.
• Locked-secret errors use the selected interface language in both the connection form and
  connection manager.
• Connection test failures, including network timeouts, are displayed in the form with their
  cause instead of only being logged.

Full Changelog: v0.5.3...v0.6.0