Can I vibecode Keeper?

Build a comprehensive, modern, and highly secure personal substitute for Keeper Password Manager in an empty repository. 
The application should be a locally-first desktop app with an optional self-hosted cloud sync backend.
Use an advanced modern stack: Rust and Tauri 2 for the desktop application, React for the frontend UI, SQLite for local storage, and high-standard audited cryptographic libraries for all security operations.

The application must incorporate the following core Keeper features:
1. Zero-Knowledge Architecture: All vault data (passwords, notes, keys) must be encrypted locally on the device using AES-256 encryption before any syncing. The master password is never stored or transmitted. The encryption key should be derived using Argon2id with a unique, randomized salt.
2. Robust Password Management: Implement a highly configurable Password Generator that can create strong, randomized passwords (customizable length, symbols, numbers). Include a feature that monitors the age and strength of passwords, prompting updates.
3. Secure File Storage & Notes: Allow the user to securely store private files, photos, videos, and secure text notes within the encrypted vault.
4. Auto-Fill & Browser Integration Preparation: Design the vault architecture so that a companion browser extension (KeeperFill equivalent) could seamlessly retrieve credentials via local IPC. Ensure clipboard clearing mechanisms exist when manually copying passwords.
5. Biometric Authentication Integration: Support biometric login hooks (Face ID, Touch ID, Windows Hello equivalent via Tauri plugins) to unlock the locally encrypted vault quickly.
6. Self-Destruct Mechanism: Implement a unique local security setting that optionally wipes all vault data from the device after a user-defined number of failed login attempts.
7. Multi-Device Sync Architecture: Build the application such that it can securely export and synchronize encrypted blobs across devices via a user-defined remote endpoint (WebDAV, S3, or self-hosted server).
8. Emergency Access Feature: Allow users to encrypt a backup recovery phrase or key fragment that can only be decrypted by designated trusted contacts.
9. Dark Web Monitoring (Mock/API Ready): Provide an interface designed to connect to the "Have I Been Pwned" API or similar service to safely check if saved credentials appear in known breaches using k-Anonymity (sending only password hash prefixes).

Additional Strict Requirements:
- Make the first run work locally with a single documented command.
- Display a persistent warning that the build has not received an independent security audit.
- Provide clear empty, loading, success, and recoverable error states.
- Ensure strict input validation, safe filenames, and graceful handling of unavailable network APIs.
- Write focused tests for the core encryption/decryption transformation, biometric mock triggers, and one complete end-to-end happy path for creating and retrieving a password record.
- Create a comprehensive README with setup instructions, an architecture diagram, a plain-language threat model, data location details, and step-by-step backup/restore procedures.
- Do NOT implement enterprise billing, analytics, telemetry, or a hosted control plane. Keep it strictly focused on individual user security and privacy.