This update makes the lock screen honest and closes out an issue from 1.8.1.

If you removed your master password on version 1.8.1, some of your keys could have stayed secured under that old password while NostrKey reported no password was set. Your keys were never lost or exposed. They stayed encrypted the whole time. NostrKey now detects that state, says so plainly, and restores access when you enter that old password once.

Also in this update:
- Removing or changing your master password now reports any key it could not convert instead of staying quiet.
- Clearer wording everywhere: keys without a master password are still encrypted on your device with a device key, and every screen now agrees.

Key-integrity fixes. If you have used NostrKey normally, your keys are fine and updating is routine.

• Removing your master password could, in some cases, leave keys still secured with that password while the app reported none was set — so they could not be unlocked. Keys (and stored API keys and vault notes) are now correctly re-secured to the passwordless tier during removal.
• If you already hit this on a previous version, your keys were never lost — they stayed encrypted under the password you removed. Open NostrKey and, if it detects this state, it will ask for that password once and restore access.
• Signing/decryption are reliably refused while the vault is locked, and the vault key is fully cleared from memory on lock.
• Substantially expanded automated tests around key storage, master-password handling, and cryptographic randomness.

Reliability fixes for the encrypted vault, found during pre-release testing of the Safari build:

• Keys created after a master password is set are now always protected by that password; any key previously left device-wrapped is re-secured automatically on your next unlock.
• Unlocking is resilient — one unreadable profile no longer blocks the whole vault, and it is named instead of silently skipped.
• The vault no longer re-locks whenever the browser suspends the extension's background worker; your auto-lock timer is the only thing that locks it.
• Unlock errors now show their real cause instead of a generic "try again" message.
• Message kinds that carry raw key material are accepted from extension UI pages only.

v1.8.0 — a ground-up redesign as a clean "instrument" for your identity:
• See exactly what you sign — plain-language actions, clear warnings, full event details before you approve.
• Manage each identity's keys, relays, permissions and remote signing (NIP-46) in one place.
• Three themes (Console / Instrument / Analog), light/dark/system, plus text-size and contrast controls.
• Folder-based encrypted backup and recovery.
• Hardened under the hood, with encryption at rest by default.