RCT: reset soc strategy

[Maschga]

Fix #26811

TODO:

• test

\cc @andig

[sourcery-ai]

Hey - I've left some high level feedback:

• In the BatteryNormal case, dereferencing m.rSocStrategy assumes it was always captured earlier; consider guarding against a nil value (or enforcing the invariant more explicitly) to prevent a potential panic if this code path is reused or reordered in the future.
• You clear m.rSocStrategy even when Write fails; consider only resetting it after a successful write so you don't lose the original strategy in error scenarios.
• If RCT instances can be used from multiple goroutines, access to rSocStrategy should be synchronized (e.g., via a mutex) to avoid data races when capturing and restoring the SOC strategy.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- In the `BatteryNormal` case, dereferencing `m.rSocStrategy` assumes it was always captured earlier; consider guarding against a nil value (or enforcing the invariant more explicitly) to prevent a potential panic if this code path is reused or reordered in the future.
- You clear `m.rSocStrategy` even when `Write` fails; consider only resetting it after a successful write so you don't lose the original strategy in error scenarios.
- If `RCT` instances can be used from multiple goroutines, access to `rSocStrategy` should be synchronized (e.g., via a mutex) to avoid data races when capturing and restoring the SOC strategy.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}