Fixed
- Energy history: reserve-space pruning (
energyHistoryReserveSpace) could delete yesterday's and today's records when free disk space stayed below the configured reserve; since the daily energy diff (prit/cnit/ctit) baseline is anchored to the last record of the previous day, losing it caused today's energy values to be computed incorrectly after a prune; pruning now always keeps yesterday's and today's records intact and only removes older history, logging a warning instead of pruning when no removable records remain outside that protected window
Full Changelog: v10.7.4...v10.7.5