High | Enhance Cooling Control with Full Feature Preparation and Deferred Fan Control Testing

[HuckleR2003]

Current cooling features are basic (fan curves, PWM/DC modes).

This issue tracks the preparation of the full cooling control module, integrating real-time temperature sensor data
(e.g., via libraries like OpenHardwareMonitor or psutil extensions) with AI diagnostics in hck_GPT.

The goal is

to enable predictive alerts, automated fan adjustments, and user-friendly visualizations
(e.g., "High temp detected - suggest increasing fan speed to 70%").

The entire functionality will be prepared in code (including UI updates and core logic),

but official testing of fan control

(e.g., actual hardware manipulation) will be deferred until the new program cache system is implemented.
This ensures stability and avoids potential risks during early alpha stages. Once cache is in place, we can safely test and refine.

Aligns with roadmap for v1.5.1+ and enhances the "intelligent monitoring" pillar of PC_Workman.Dependencies: Implementation of the new program cache system (create a separate issue if not already tracked, e.g., "Introduce Advanced Caching for Historical Data").
Stable integration of hck_GPT for diagnostics (already in core, but verify compatibility).

Steps to Implement:

Preparation Phase (Pre-Cache):

Add dependencies for sensor reading (e.g., integrate OpenHardwareMonitorLib or equivalent cross-platform alternatives).

Update core/ modules to fetch and process live temperature data from CPU/GPU/fans.
Expand ui/ to include real-time temp displays, fan curve editors, and PWM/DC toggles in an expanded dashboard view.
Link to hck_GPT for AI-driven suggestions (e.g., analyze temp spikes and propose adjustments via natural language).
Mock fan control logic in code (simulate adjustments without hardware access for now).
Write unit tests for non-hardware parts (e.g., data parsing, AI integration).

Post-Cache Testing Phase:

After cache system rollout, enable hardware-level fan control testing on supported setups (e.g., Windows with admin privileges).
Run high-load scenarios (e.g., stress tests with tools like Prime95) to validate alerts and auto-adjustments.
Gather logs and refine based on "time travel" data from cache (historical temp patterns).
Document safety warnings in README.

Actually version: v.1.5.8
Milestone: v1.7.0 (or adjust based on cache progress)

Marcin HCK Firmuga