Can I vibecode Timeular?

Build a personal replacement for Timeular (EARLY) in an empty repository.
Use Tauri 2, React, TypeScript, SQLite, and optional OS accessibility APIs; do not offer alternative stacks.
The core loop is: track time and focused sessions with projects and reminders using frictionless software-only controls that mimic the tactical, habit-forming experience of a physical tracker, review patterns locally, and export a transparent activity record.
Focus heavily on a breathtaking, premium UI design. Use an immaculate color palette with vibrant accents against a sleek, modern background (dark mode preferred). Typography should be bold and modern (e.g., Roboto or Inter). Since we lack the physical 8-sided die hardware, the digital interface must be extremely tactile—use gorgeous 3D-like glassmorphism for a virtual 'tracker' that users can 'flip' or click with highly satisfying micro-animations, bouncy transitions, and hover states that make time tracking feel fun rather than tedious.
Create one-click start and stop, seamless switching between tasks, manual entries, idle detection, tags, projects, and notes. Implement a Quicktrack-like keyboard shortcut system for effortless logging when away from the main window.
Include smart suggestions or visualizations for background activity tracking (opt-in application-name tracking) to help fill in gaps retrospectively. Never record window contents or keystrokes.
Add Pomodoro-style mindful productivity sessions, break reminders, and an optional allowlist blocker. Provide daily, weekly, project, and category reports via highly visual, interactive charts and calendar views that break down billable vs. non-billable time.
Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward (CSV/JSON).
Put secrets in .env, ship .env.example, and never commit credentials. Add automatic local backups and a privacy screen explaining every collected field.
Include clear empty, loading, success, and recoverable error states with polished aesthetics. Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Deliberately leave out employee surveillance, cross-device blocking, and heavy team collaboration features.
Finish by running the tests and listing the exact commands used.