Can I vibecode Day One?

Build a comprehensive, modern, local-first digital journaling application inspired by Day One. The focus must be on an award-winning, distraction-free, and minimalist user interface, robust privacy, and rich multimedia integration.

Tech Stack: Tauri 2 + React + TypeScript + Tailwind CSS + SQLite.

Core Requirements & Features:
1. Privacy First: Implement local-only storage using SQLite. All entries must be stored locally. Add a mock biometric/passcode lock screen on app startup to simulate security.
2. Rich Multimedia Support: Allow users to write rich text entries (Markdown support) and attach images. Display images elegantly inline or as a gallery within the entry. 
3. Metadata Extraction: Automatically append metadata to each entry upon creation, including Date, Time, Location (mocked if necessary), and Weather (mocked or fetched via a free weather API if provided in .env).
4. Organization & Habit Building: 
   - Support multiple journals (e.g., "Personal", "Work", "Travel").
   - Implement tags and a robust full-text search.
   - Include a daily "Prompt" feature to help users overcome writer's block.
   - Build an "On This Day" feature that surfaces entries from past years to encourage reflection.
5. User Interface & Experience:
   - Create a clean, beautiful, minimalist, and frictionless UI. The design should feel premium, using a thoughtful typography scale, smooth transitions, and a calming color palette.
   - Implement a two-pane layout: a sidebar on the left for navigation (Journals, Tags, On This Day, Settings) and a main timeline/entry view on the right.
   - The timeline should display a beautiful masonry or list view of entries with image thumbnails and excerpts.
   - Include clear empty, loading, validation, success, and failure states. Support dark and light modes.
6. Export: Provide an option to export all entries as a ZIP file containing Markdown files and a folder of images, ensuring the user is never trapped in the app.

Development Guidelines:
- Start from an empty folder and create the complete working project.
- Make the default mode single-user and private. Do not add analytics, telemetry, ads, or third-party accounts.
- Use accessible keyboard navigation, focus states, and sensible contrast.
- Write focused unit tests for the data model and the most important workflow. Add one end-to-end smoke test that proves the core loop works.
- Create a comprehensive README with setup instructions, architecture overview, data location, and limitations.
- Include scripts for install, development, test, and build. Run the tests and build before finishing, and fix any errors.