After a successful gesture, `clearRuntimeSnapshot` is called but no post-action `captureRuntimeSnapshotAfterActionSafely` call follows, so the runtime snapshot is permanently cleared and the success result contains no `capture` payload — unlike every comparable tool (`swipe`, `tap`, `key_press`, etc.).

`createUiErrorItems` renders `code`, `elementRef`, `timeoutMs`, and `recoveryHint`, but never includes `uiError.message` — the required, specific error description (e.g. "Element ref 'e99' was not found in the current snapshot") is lost from all CLI and tool output.

For each scrollable element `records.filter(isForegroundCandidateForRoot)` scans all `n` records, and `isSameOrDescendantPath` does a string `startsWith` on full AX hierarchy paths — making this O(s × n × path_length). With memoization the filter runs once per scrollable element, but in a worst-case flat tree where most elements are scrollable this degrades to O(n²). Consider pre-building a path-prefix index keyed by path segments so descendant lookup is O(1) instead of O(n).

Multiple `UiAction` interfaces have had their fields replaced (e.g., `UiActionTap` drops `x?/y?/id?/label?` for required `elementRef`; `UiActionSwipe` drops `from?/to?` for required `withinElementRef` + `direction`; `UiActionLongPress` drops `x/y` for `elementRef`). Any external MCP client or agent that reads/persists the structured output of UI automation tools using the old field shape will silently receive `undefined` for those fields after this change — this warrants a senior review of any consumers outside this repo.