fix(modes): respect SoC limits in maximize modes and stop per-cycle write spam

[bvweerd]

Problem

1. SoC limits ignored. maximize_export discharged every battery at max_discharge_w even at/below min_soc; maximize_import charged at max_charge_w even at/above max_soc. SoC gating only existed in the reactive layer, so an explicit maximize mode could drain a battery to empty or push a full one into overcharge (leaving protection to the BMS alone).
2. Per-cycle write spam. Both maximize modes rewrote every array, load and battery setpoint on every 5 s cycle regardless of change — dozens of service calls per minute against actuators that were already in position.

Fix

• Battery targets in the maximize modes respect SoC: at/below min_soc → no discharge (target 0); at/above max_soc → no charge (target 0).
• Targets are compared against the actual entity state before writing: unchanged actuators are skipped, while externally changed ones are still re-asserted on the next cycle — enforcement is preserved without the spam.

Note: maximize modes still override scheduled batteries (the optimizer) — that is intentional per the mode semantics ("sell/consume as much as possible" is an explicit user command), now bounded by SoC.

Tests

New in tests/test_control_modes.py: min-SoC blocks discharge in maximize_export, max-SoC blocks charge in maximize_import, no writes when entities already match, external change is re-asserted. Full suite: 243 passed.

https://claude.ai/code/session_01RUWpwxbGsgR3PoLHLq4Djz

---

Generated by Claude Code