v3.36.0

v3.36.0

• CRITICAL FIX: saving the config (or loading a profile) while an event was active could leave changes applied forever. When undoing an event after a reload, the daemon re-read the config from disk - but that config was already the new one, just saved. If the active event no longer matched what the new config said, "undo" found nothing to revert, leaving reniced apps, disabled cores, disabled WiFi, or disabled GMS stuck permanently, with the daemon believing everything was clean. Not a rare edge case - editing an active event and saving, or switching profiles, are completely ordinary actions. Fixed by capturing a real snapshot of what was applied at the moment each event starts, used when undoing it instead of re-reading the config.
• Found via a self-audit, verified with real reproductions before fixing - same rigor as the rest of this critical-fix series.
• Also includes v3.35.0's stale-data detection and the battery rate comparison bar.