Vault Key Encoding & Browser Compatibility Fix
Fixed an issue where vault keys containing non-Latin characters crashed the browser session by implementing safe Base64 header encoding.
#What's Changed
- [Fix] Fixed a critical bug that caused users to become permanently stuck in an error loop (Failed to execute 'set' on 'Headers') if their Vault Password contained non-Latin characters or certain Unicode symbols.
- [Security] Implemented safe Base64 transmission via X-Vault-Key-B64 headers across the frontend, CLI dashboard preview, and backend to guarantee full compatibility with all characters.