The `cli/json` swipe success test is skipped via `it.skip` because the stored fixture still reflects the old coordinate-based swipe contract — this masks a contract change rather than treating it as one requiring review.

Calling `resolveElementRef(simulatorId, elementRef, 'touch')` rejects elements with `application` or `window` roles with `TARGET_NOT_ACTIONABLE` before the `usesWithinElementDragPoints` branch is ever reached, because `deriveActions` in `runtime-snapshot.ts` explicitly excludes `touch` from those roles (`if (role !== 'application' && role !== 'window')`). The intended swipe-based drag path for viewport-level elements is therefore unreachable. Fix by resolving without a strict action requirement and then validating the element can support drag (e.g. has `touch` or `swipeWithin`), or by passing `'swipeWithin'` as the required action and checking `touch` availability for the non-container path after resolution.

After a successful touch, `clearRuntimeSnapshot` is called but `captureRuntimeSnapshotAfterActionSafely` is never called, so the response has no `capture` payload and `previousRuntimeSnapshot` is not set — unlike every other semantic UI action tool (`tap`, `long_press`, `swipe`, `drag`, `gesture`, `type_text`, `batch`). Any follow-up `resolveElementRef` call will immediately fail with `SNAPSHOT_MISSING`, and `setUiActionStructuredOutput` falls back to the stale `snapshot_ui` next-step rather than the runtime-snapshot guidance path.

Add `previousRuntimeSnapshot: resolution.snapshot.payload` to the `createUiActionSuccessResult` options object so the text-field element is suppressed from next-step guidance after typing, consistent with `tap`, `swipe`, `long_press`, and `drag`.

For every scrollable candidate, `foregroundScore` calls both `findSheetGrabberDescendant` (`records.find`) and `records.filter(isForegroundCandidateForRoot)`, each O(n), making the whole function O(n²) over the snapshot element count. On a complex screen with hundreds of accessibility elements this runs on every UI action tool call.

For every scrollable candidate, `foregroundScore` calls both `findSheetGrabberDescendant` (`records.find`) and `records.filter(isForegroundCandidateForRoot)`, each O(n), making the whole function O(n²) over the snapshot element count. On a complex screen with hundreds of accessibility elements this runs on every UI action tool call.

These constants (and the `compactRuntimeSnapshotText`, `normalizedRuntimeSnapshotText`, `isHiddenRuntimeTarget`, `isLowPriorityRuntimeTarget` helpers) are copied verbatim from `domain-result-text.ts`; extract them into a shared module to eliminate the duplication.