Can I vibecode RoboForm?

Build a comprehensive and highly secure personal substitute for RoboForm in an empty repository. You will create a robust local password manager, secure form filler, and digital vault that implements the core workflows of premium password managers, while ensuring absolute local control over user data.

Tech Stack:
- Rust & Tauri 2 for a secure, cross-platform desktop foundation.
- React and TypeScript for a modern, highly responsive user interface.
- SQLite for local database management.
- Argon2id and AES-256-GCM (using audited cryptographic libraries) for state-of-the-art encryption.

Core Application Features & Requirements:
1. Advanced Vault & Secure Storage:
   - Implement "Safenotes" for securely storing free-text, Wi-Fi passwords, software license keys, and other sensitive information.
   - Support multiple record types: Web Logins, Credit Cards, Bank Accounts, and Identities.
   - Implement a secure organization system utilizing Folders, Categories, and "Pinned" (favorite) items for quick access.

2. Comprehensive Password Management & Generator:
   - Build a highly customizable Password Generator that creates strong, unique, and complex passwords (configurable length, character sets, symbols).
   - Implement a "Security Center" feature that audits the user's local vault and flags weak, reused, or duplicate passwords.
   - Create an AutoSave and AutoFill workflow simulation (e.g., a browser-extension-like UI or mock API) to demonstrate how credentials and checkout forms would be securely captured and injected into target applications.

3. Cryptography & Threat Model:
   - Write a plain-language threat model document before implementing any sensitive feature.
   - The master key MUST be derived exclusively from the user's master password using Argon2id with a unique, randomly generated salt.
   - Encrypt all vault data at rest using AES-256-GCM authenticated encryption from a widely recognized and maintained Rust cryptography library. NEVER invent your own cryptographic primitives.
   - Ensure the application runs in a "Local-Only Mode" by default.

4. Essential Security Mechanisms:
   - Implement strict inactivity lock timeouts (e.g., locking the vault after 5 minutes of no user interaction).
   - Automatically clear the system clipboard after a configured duration (e.g., 30 seconds) whenever a password or sensitive field is copied.
   - Make recovery-key creation explicit during the initial onboarding process and require the user to verify they have saved it.

5. Data Portability & Best Practices:
   - Implement reliable data import/export functionality (e.g., standard CSV formats compatible with major password managers) and encrypted backups.
   - Include clear empty, loading, success, and recoverable error states throughout the React UI.
   - Add stringent input validation and safe filename handling.
   - Store environment variables securely in .env, ship an .env.example, and never commit credentials.
   - Write focused tests for core cryptographic transformations and one complete end-to-end happy path for creating and unlocking a vault.
   - Create a thorough README outlining setup, architecture, permissions, local data location, and backup procedures.

6. Exclusions (Out of Scope):
   - Do NOT add user accounts, cloud sync, billing, telemetry, analytics, or any hosted control plane.
   - Do NOT implement enterprise management features, multi-user secure sharing, identity-protection monitoring (dark web scanning), or data-broker removal.
   - Clearly display a persistent UI warning that this build is a personal substitute and has not received an independent security audit.

Finish by running the tests, ensuring the first run works locally with one documented command, and listing the exact commands used.