Can I vibecode Enpass?

Build a comprehensive, privacy-first, zero-knowledge password manager as a personal replacement for Enpass in an empty repository. The application must empower users with full data sovereignty by storing all vaults and encrypted data locally or on the user's own cloud storage (like Google Drive, Dropbox, or Nextcloud), completely eschewing any proprietary centralized servers.

Tech Stack: Use Rust, Tauri 2, React, SQLite, Argon2id for key derivation, and well-audited cryptographic libraries (e.g., standard AES-256-GCM for authenticated encryption). Do not offer alternative stacks.

Core Functionality & Security Features:
1. Zero-Knowledge Architecture & Encryption: All vault data must be encrypted with 256-bit AES-GCM. The master key must be derived locally using Argon2id with a unique salt. Ensure that under no circumstances is the master password stored or transmitted. Never invent custom cryptographic primitives; rely strictly on established, maintained crates.
2. Multiple Vaults & Unlimited Items: Support creating and syncing multiple vaults (e.g., Personal, Work, Family) with unlimited credentials. 
3. Data Sovereignty & Offline Access: Data must be securely accessible offline. Implement optional sync logic that can interface with local folders (which the user syncs via their own cloud provider).
4. Password Management & Autofill: Include robust password generation (customizable length, symbols, numbers), TOTP (one-time password) generation for two-factor authentication, and an organizational system utilizing customizable categories, tags, and templates.
5. Security Auditing: Build a "Security Score" dashboard that analyzes the vault locally to flag weak, reused, or potentially compromised passwords. 
6. Client Security: Implement automatic lock timeouts, clipboard clearing after 30 seconds, and biometric authentication integration where supported by the OS (Face ID, Touch ID, Windows Hello).
7. Import/Export & Recovery: Provide straightforward tools for easy migration from other password managers (CSV import/export) and encrypted backups. Ensure explicit recovery-key creation and document the restore process.

Implementation Requirements:
- Write a plain-language threat model before implementing any sensitive feature. 
- Put secrets in .env, ship .env.example, and never commit credentials.
- Make the first run work locally with a single documented command.
- Display a persistent, un-hideable warning in the UI that the build has not received an independent security audit and is for personal use only.
- Implement comprehensive input validation, safe filename handling, and graceful error recovery.
- Include clear empty, loading, success, and recoverable error states for all UI interactions.

Testing & Documentation:
- Write focused unit tests for cryptographic transformations, vault serialization/deserialization, and at least one end-to-end happy path for creating a vault, adding an entry, and unlocking.
- Create a detailed README with setup instructions, architecture overview, permission models, data locations, backup steps, and the exact commands used to run tests.
- Explicitly exclude accounts, billing, telemetry, analytics, hosted control planes, enterprise sharing guarantees, identity-protection monitoring, and external breach alerts requiring API transmission of passwords.

Finish by running the tests and listing the exact commands used to start the application.