shm11C3/HardwareVisualizer

Filed from an AI-assisted performance audit (2026-06-06). Problem The tray render loop (src-tauri/src/adapters/tray.rs:87-88) calls current_widget_settings() on every 1 Hz snapshot, which does .tray_widget.clone() + .normalized() plus current_temperature_unit() — a lock acquisition and allocations every second purely to re-read settings that change only when the user edits them. Proposed Solution Cache the normalized widget settings (and temperature unit) in the tray adapter and invalidate/rebuild only on a settings-change notification, instead of cloning + normalizing per tick. Additional Context Minor in absolute cost, but the fix is small and removes per-second lock traffic and allocations from the path that runs 24/7 in tray mode. Good first issue for the Rust side.

Filed from an AI-assisted performance audit (2026-06-06). Each finding was adversarially verified against the actual code. Problem uuid is configured with features ["v7", "fast-rng", "macro-diagnostics"] (src-tauri/Cargo.toml:59-65), but the only uuid usage in the entire codebase is a single Uuid::now_v7().to_string() call (src-tauri/src/services/background_image_service.rs:93). now_v7() sources entropy from getrandom directly and does not use the fast-rng path — fast-rng only affects random (v4) generation, and it is what pulls the full rand 0.10 stack (rand_core, rand_chacha) into the binary (cargo tree -i [email protected] → uuid v1.23.1). macro-diagnostics only helps the compile-time uuid! literal macro, which is never used. Proposed Solution uuid = { version = "1.23.1", features = ["v7"] } Drops rand 0.10 + rand_chacha + rand_core from the runtime binary and a proc-macro dependency from the build, with no functional change. Additional Context Binary-size / dependency-hygiene win