The `SNAPSHOT_CAPTURE_FAILED` code emitted by `captureRuntimeSnapshotAfterActionSafely` is not listed in the `recoverableUiError.code` enum in `schemas/structured-output/xcodebuildmcp.output.ui-action-result/2.schema.json`, so any consumer validating against the published outputSchema will reject responses that contain this code.

After a successful long press the runtime snapshot is cleared but never refreshed, so agents receive no updated UI context. Long press typically opens context menus or action sheets, yet unlike `tap`, `swipe`, `type_text`, and `batch`, it never calls `captureRuntimeSnapshotAfterActionSafely` — forcing agents to make an extra `snapshot_ui` call to see the resulting UI.

After a successful long press the runtime snapshot is cleared but never refreshed, so agents receive no updated UI context. Long press typically opens context menus or action sheets, yet unlike `tap`, `swipe`, `type_text`, and `batch`, it never calls `captureRuntimeSnapshotAfterActionSafely` — forcing agents to make an extra `snapshot_ui` call to see the resulting UI.

After a successful long press the runtime snapshot is cleared but never refreshed, so agents receive no updated UI context. Long press typically opens context menus or action sheets, yet unlike `tap`, `swipe`, `type_text`, and `batch`, it never calls `captureRuntimeSnapshotAfterActionSafely` — forcing agents to make an extra `snapshot_ui` call to see the resulting UI.

In `src/mcp/tools/ui-automation/touch.ts`, the success path of the touch executor calls `clearRuntimeSnapshot(simulatorId)` but never calls `captureRuntimeSnapshotAfterActionSafely`. Every other elementRef-based action tool changed in this PR (`tap.ts`, `swipe.ts`, `type_text.ts`, `batch.ts`) recaptures a fresh runtime snapshot after a successful action so the agent can chain a follow-up ref-based action. Because `touch` now requires `elementRef`, the inconsistency means any follow-up touch/tap on a resolved ref will fail with `SNAPSHOT_MISSING` until the agent manually re-invokes `snapshot_ui`, defeating the rs/1 parity goal of this PR.

The new `uiError?` field on `UiActionResultDomainResult` can carry `code: 'SNAPSHOT_CAPTURE_FAILED'` (set by `captureRuntimeSnapshotAfterActionSafely` in `post-action-snapshot.ts`), but that code is not included in the `recoverableUiError.code` enum in `schemas/structured-output/xcodebuildmcp.output.ui-action-result/2.schema.json`, causing schema validation failures for any MCP client that validates structured output.

When `internalSchema` is a `ZodEffects` (created by `.superRefine()` or `.refine()`), `getObjectSchemaKeys` finds no `shape` property and returns `null`, so `filterSessionDefaultsForSchema` falls through and returns **all** session defaults unfiltered. `waitForUiSchema` is `z.strictObject(waitForUiSchemaShape).superRefine(...)`, so passing build-related session defaults (`projectPath`, `scheme`, `configuration`, etc.) to its strict inner `ZodObject` causes a `PARAMETER_VALIDATION_FAILED` error — the tool silently fails instead of running.

For each container element, the function scans the entire `elements` array twice — once for `hasOverflowingDescendant` and once for `findSheetGrabberDescendant` — giving O(n²) complexity that will degrade noticeably on rich UI screens where the flattened accessibility tree can have hundreds of nodes.

After a successful `touch down`, `clearRuntimeSnapshot(simulatorId)` is called unconditionally (line 128), so a subsequent `touch up` call will immediately fail with `SNAPSHOT_MISSING` when it tries to `resolveElementRef` — making drag-style interactions (down on element A, release on element B) impossible without an intervening `snapshot_ui` call.