Can I vibecode NordPass?

Build a robust, personal password manager inspired by NordPass in a fresh repository.
Your task is to build a local, highly-secure, zero-knowledge encrypted vault application. 

Technology Stack:
Use Rust, Tauri 2, React, SQLite, and established cryptographic libraries like Argon2id and ring for XChaCha20-Poly1305 encryption. Do not substitute this stack.

Core Vault Features:
- Zero-Knowledge Architecture: The app must strictly enforce that the vault can only be unlocked with a user-defined Master Password. The Master Password itself should never be stored; only a cryptographic hash should be kept for verification.
- XChaCha20 Encryption: Ensure all vault items (passwords, secure notes, credit cards) are encrypted locally using XChaCha20-Poly1305 authenticated encryption before ever touching the SQLite database.
- Password Generator: Include an advanced password generator that creates strong, complex, unique passwords with customizable parameters (length, symbols, numbers, upper/lowercase).
- Local Autofill & Autosave: Implement basic autofill mechanisms allowing users to quickly copy credentials to the clipboard. The clipboard must automatically clear after a short timeout (e.g., 30 seconds) for security.
- Data Health Check: Include a local-only routine that flags weak, reused, or aging passwords based on local analysis, strictly without sending hashes to third-party APIs unless explicitly opted in via a privacy-preserving mechanism (like k-anonymity).

Security & Engineering Requirements:
- Argon2id Key Derivation: Derive the master encryption key using Argon2id with a unique, securely generated salt. 
- Lock Timeout: Implement automatic locking of the vault after a period of inactivity to protect the user if they step away from their device.
- Emergency Access/Recovery Key: During initial setup, generate a secure recovery key. Make the recovery-key creation explicit, force the user to save it, and build a flow to restore the vault from a fresh installation using this key.
- Threat Model Documentation: Write a plain-language threat model documenting exactly what is protected and what is not (e.g., keyloggers, memory scraping). Display a persistent warning that this is a personal, unaudited build and should not replace an audited enterprise password manager for critical secrets.
- Encrypted Backups: Support straightforward, encrypted export of the vault data, ensuring data portability.
- UI/UX: Implement a sleek, dark-mode-first user interface with clear empty states, loading indicators, success messages, and recoverable error handling. 
- Put all configuration in a .env file and ship a .env.example. Never commit secrets to the repository.
- Write focused unit tests for the cryptographic core transformations (encryption/decryption) and at least one end-to-end happy path test (account creation -> add password -> unlock).

Deliberate Exclusions:
- Do not build a backend server, account syncing, billing, telemetry, analytics, or hosted control plane. All data must reside locally.
- Leave out identity-protection monitoring, data-broker removal, cross-platform syncing, and enterprise SSO integrations.

Finish the task by running your tests, confirming success, and listing the exact setup commands in a comprehensive README.md file.