agent-device 0.18.0 → 0.18.2

package/ios-runner/AgentDeviceRunner/AgentDeviceRunner/Assets.xcassets/PoweredBy.imageset/Contents.json

@@ -1,21 +0,0 @@
-{
-  "images" : [
-    {
-      "filename" : "powered-by.png",
-      "idiom" : "universal",
-      "scale" : "1x"
-    },
-    {
-      "idiom" : "universal",
-      "scale" : "2x"
-    },
-    {
-      "idiom" : "universal",
-      "scale" : "3x"
-    }
-  ],
-  "info" : {
-    "author" : "xcode",
-    "version" : 1
-  }
-}

package/ios-runner/AgentDeviceRunner/AgentDeviceRunner/ContentView.swift

@@ -1,34 +0,0 @@
-//
-//  ContentView.swift
-//  AgentDeviceRunner
-//
-//  Created by Michał Pierzchała on 30/01/2026.
-//
-
-import SwiftUI
-
-struct ContentView: View {
-    var body: some View {
-        Spacer(minLength: 16)
-        VStack {
-            Image("Logo")
-                .resizable()
-                .scaledToFit()
-                .frame(width: 64, height: 64)
-                .clipShape(RoundedRectangle(cornerRadius: 14, style: .continuous))
-            Text("Agent Device Runner")
-                .padding(.top, 16)
-        }
-        Spacer(minLength: 16)
-        Image("PoweredBy")
-            .resizable()
-            .scaledToFit()
-            .frame(width: 180, height: 44)
-            .opacity(0.8)
-        .padding()
-    }
-}
-
-#Preview {
-    ContentView()
-}

package/ios-runner/README.md

@@ -1,53 +0,0 @@
-# agent-device iOS Runner
-
-This folder contains the lightweight XCUITest runner used to provide element-level automation for Apple-family targets.
-
-## Intent
-
-- Provide a minimal XCTest target that exposes UI automation over a small HTTP server.
-- Allow local builds via `xcodebuild` and caching for faster subsequent runs.
-- Support simulator prebuilds where compatible.
-
-## Status
-
-Current internal runner for iOS, tvOS, and macOS desktop automation.
-
-Protocol and maintenance references:
-
-- Protocol overview: [`RUNNER_PROTOCOL.md`](RUNNER_PROTOCOL.md)
-- TypeScript client: [`../src/platforms/ios/runner-client.ts`](../src/platforms/ios/runner-client.ts)
-- Swift wire models: [`AgentDeviceRunner/AgentDeviceRunnerUITests/RunnerTests+Models.swift`](AgentDeviceRunner/AgentDeviceRunnerUITests/RunnerTests+Models.swift)
-
-## UITest Runner File Map
-
-`AgentDeviceRunnerUITests/RunnerTests` is split into focused files to reduce context size for contributors and LLM agents.
-
-- `RunnerTests.swift`: shared state/constants, `setUp()`, and `testCommand()` entry flow.
-- `RunnerTests+Models.swift`: wire protocol models (`Command`, `Response`, snapshot payload models).
-- `RunnerTests+Environment.swift`: environment and CLI argument helpers (`RunnerEnv`).
-- `RunnerTests+Transport.swift`: TCP request handling and HTTP parsing/encoding.
-- `RunnerTests+CommandExecution.swift`: command dispatch (`execute*`) and command switch.
-- `RunnerTests+Lifecycle.swift`: activation/retry/stabilization and recording lifecycle helpers.
-- `RunnerTests+Interaction.swift`: tap/drag/swipe/type/back/home/rotate/app-switcher helpers.
-- `RunnerTests+Snapshot.swift`: fast/raw snapshot builders and include/filter helpers.
-- `RunnerTests+SystemModal.swift`: SpringBoard/system modal detection and modal snapshot shaping.
-- `RunnerTests+ScreenRecorder.swift`: nested `ScreenRecorder` implementation.
-
-## Snapshot Strategy
-
-iOS snapshots have two explicit public capture modes:
-
-- full/raw snapshots use recursive XCTest snapshots for rich hierarchy and diagnostics;
-- interactive snapshots filter the same visible tree down to agent-facing refs.
-
-Some simulator apps expose accessibility trees that lower-level AX services can inspect but XCTest
-cannot serialize reliably. In those cases interactive snapshots may return a sparse root quickly,
-while full snapshots preserve the XCTest error. See
-[`../docs/adr/0004-ios-snapshot-backend-strategy.md`](../docs/adr/0004-ios-snapshot-backend-strategy.md)
-for the backend boundary and future simulator AX-service direction.
-
-## Protocol Notes
-
-- The daemon posts JSON commands to `POST /command` on the runner's local HTTP listener.
-- The runner responds with a JSON envelope shaped as `{ ok, data?, error? }`.
-- The protocol is internal to `agent-device`; when adding or renaming commands, update both wire models and the protocol tests/docs in the same change.

package/ios-runner/RUNNER_PROTOCOL.md

@@ -1,76 +0,0 @@
-# iOS Runner Protocol
-
-The Apple runner speaks a small internal HTTP+JSON protocol between the TypeScript daemon and the XCUITest host. This protocol is a maintainer document, not part of the public user docs, but it should stay explicit so the TypeScript and Swift sides do not drift.
-
-## Transport
-
-- Endpoint: `POST /command`
-- Content type: `application/json`
-- Request body: one JSON command object
-- Response body: one JSON envelope
-
-The daemon probes `http://127.0.0.1:<port>/command` for simulator and desktop flows, and can use a tunneled device address for physical iOS/tvOS devices before falling back to localhost.
-
-## Request Shape
-
-Every request includes a `command` field. Additional fields depend on the command family.
-
-Examples:
-
-```json
-{ "command": "tap", "x": 120, "y": 240 }
-```
-
-```json
-{
-  "command": "snapshot",
-  "interactiveOnly": true,
-  "depth": 2,
-  "scope": "app",
-  "raw": false
-}
-```
-
-```json
-{ "command": "recordStart", "outPath": "/tmp/demo.mp4", "fps": 30, "maxSize": 720 }
-```
-
-```json
-{ "command": "rotate", "orientation": "landscape-left" }
-```
-
-The current command names are defined in:
-
-- [`../src/platforms/ios/runner-client.ts`](../src/platforms/ios/runner-client.ts)
-- [`AgentDeviceRunner/AgentDeviceRunnerUITests/RunnerTests+Models.swift`](AgentDeviceRunner/AgentDeviceRunnerUITests/RunnerTests+Models.swift)
-
-## Response Shape
-
-Successful and failed responses use the same top-level envelope:
-
-```json
-{
-  "ok": true,
-  "data": {
-    "message": "ok"
-  }
-}
-```
-
-```json
-{
-  "ok": false,
-  "error": {
-    "code": "UNSUPPORTED_OPERATION",
-    "message": "Unable to dismiss the iOS keyboard without a native dismiss gesture or control"
-  }
-}
-```
-
-`data` is command-specific. Common fields include snapshot nodes, text lookup results, gesture timing, visibility metadata, and screenshot or recording output details.
-
-## Maintenance Rules
-
-- Treat the TypeScript and Swift wire models as a single contract.
-- When adding, removing, or renaming a command, update the protocol fixtures/tests in the same change.
-- Keep this file focused on the actual wire shape rather than implementation details of command execution.