build_offline_system_tracker

You are running inside Google Anti Gravity IDE, in this repository workspace.

GOAL Build a comprehensive, offline-first system activity tracker application ("SystemPulse") that tracks software activity and hardware usage without time limits. The application must identify running processes, track active windows, monitor power/temperature, and store all data locally.

IMPORTANT NOTES

• Offline First: All data must remain on the local machine (SQLite). No persistent internet connection required.
• Privacy: No telemetry. Data stored in %LOCALAPPDATA%.
• Tech Stack: Rust (Daemon), Tauri v2 (Backend), React + TypeScript + TailwindCSS (Frontend).
• Design: "SystemPulse" aesthetic - Dark mode, Slate-950 background, Emerald/Blue accents, Glassmorphism.

CONSTRAINTS

• Daemon: Must run silently in background.
• Data Collection:
  • sysinfo for process metrics (CPU/RAM).
  • windows crate for active window tracking (foreground app).
  • nvml-wrapper for NVIDIA GPU stats (Power/Temp).
• Frontend: Must match the specific design provided (Sidebar layout, Circular gauges, Real-time charts).
• Performance: Poll every second, minimal resource footprint.

WORK PLAN

1. Daemon Implementation (crates/daemon)

   • Initialize data collectors (Process, System, Window, GPU).
   • Set up SQLite database with optimized schema for time-series data.
   • Implement the main event loop (Collect -> Store -> Sleep).
   • Ensure graceful shutdown handling.

2. Tauri Integration (src-tauri)

   • Create Tauri commands to expose database data to the frontend:
     • get_current_metrics (Real-time)
     • get_history (Historical charts)
     • get_process_history (Per-app details)
   • Register commands in lib.rs.

3. Frontend Development (src)

   • Setup: Install lucide-react, recharts, tailwindcss.
   • Styling: Configure Tailwind for the "SystemPulse" dark theme.
   • Components:
     • Sidebar: Navigation logic.
     • OverviewPanel: Dashboard with CircularGauge and AreaChart.
     • ProcessList: Sortable table with api integration.
     • PowerView: Energy monitoring charts.
   • Wiring: Replace mock data with real api calls to the Rust backend.

4. Validation

   • Verify cargo run -p daemon starts collecting data.
   • Verify npm run tauri dev shows real-time updates.
   • Check database size and retention policies.

EXECUTION CRITICAL INSTRUCTION: You must perform and validate "each and every" step in the WORK PLAN. Do not skip any item. Do not proceed to the next step until the current one is verified as working.

1. Check: Before starting a step, verify the prerequisites.
2. Do: Execute the implementation.
3. Validate: Verify the result (compile, run, or check output) before moving on.
4. Repeat: Do this for every single item in the checklist.

Follow the implementation plan simply and strictly. Do not deviate.