ares-do: send key events and take screenshots

.github/workflows/release.yml

@@ -8,8 +8,8 @@ on:
 env:
   # Every binary that goes into a release archive.
   BINS: >-
-    ares-device ares-install ares-launch ares-novacom ares-package
-    ares-pull ares-push ares-setup-device ares-shell
+    ares-device ares-do ares-install ares-launch ares-novacom
+    ares-package ares-pull ares-push ares-setup-device ares-shell
 
 jobs:
   # One archive per platform, with all tools inside.

Cargo.toml

@@ -12,6 +12,7 @@ members = [
     "ares-setup-device",
     "ares-novacom",
     "ares-pull",
+    "ares-do",
 ]
 
 [workspace.package]

README.md

@@ -21,6 +21,7 @@ The device list is shared with the official CLI, so you can mix both.
 | [`ares-push`](ares-push#readme)                | Copy files to the device                       |
 | [`ares-pull`](ares-pull#readme)                | Copy files from the device                     |
 | [`ares-novacom`](ares-novacom#readme)          | Fetch the device SSH key, forward a port       |
+| [`ares-do`](ares-do#readme)                    | Send key events, take screenshots, replay flows |
 
 Each command has its own README with the full option list and examples. Every
 tool also accepts `--help`. Every device-facing tool accepts `-d NAME`, or reads
@@ -34,7 +35,7 @@ All install methods below give you the **whole set** of tools at once.
 
 Download one archive per platform from the
 [latest release](https://github.com/webosbrew/ares-cli-rs/releases/latest).
-It holds all nine binaries.
+It holds all ten binaries.
 
 Linux and macOS:
 
@@ -88,7 +89,7 @@ Needs a [Rust](https://rustup.rs/) toolchain, plus the build dependencies below.
 ```sh
 cargo install --locked --git https://github.com/webosbrew/ares-cli-rs \
   ares-setup-device ares-device ares-package ares-install ares-launch \
-  ares-shell ares-push ares-pull ares-novacom
+  ares-shell ares-push ares-pull ares-novacom ares-do
 ```
 
 Cargo puts the binaries in `~/.cargo/bin`, which is already on your `PATH`

RELEASING.md

@@ -9,7 +9,7 @@ All crates share one version, set by `workspace.package.version` in the root
    `Cargo.lock`, then commit.
 2. Tag the commit and publish a GitHub release for the tag.
 3. The `Release` workflow runs on `released` and uploads:
-   - one archive per platform, with all nine binaries inside, plus a
+   - one archive per platform, with all ten binaries inside, plus a
      `.sha256` file for each
    - one `.deb` per tool, for `amd64` and `arm64`
 
@@ -24,7 +24,7 @@ Publish in this order, because each step depends on the one before it:
 cargo publish -p ares-device-lib
 cargo publish -p ares-connection-lib
 for p in ares-package ares-install ares-launch ares-device ares-shell \
-         ares-push ares-pull ares-setup-device ares-novacom; do
+         ares-push ares-pull ares-setup-device ares-novacom ares-do; do
   cargo publish -p "$p"
 done
 ```

ares-do/Cargo.toml

@@ -0,0 +1,29 @@
+[package]
+name = "ares-do"
+version.workspace = true
+edition.workspace = true
+authors.workspace = true
+license.workspace = true
+readme = "README.md"
+repository.workspace = true
+homepage.workspace = true
+keywords.workspace = true
+categories.workspace = true
+description = "Send key events and take screenshots on a webOS device"
+
+[lints]
+workspace = true
+
+[dependencies]
+ares-device-lib = { workspace = true }
+ares-connection-lib = { workspace = true }
+clap = { workspace = true, features = ["derive", "env"] }
+serde = { workspace = true, features = ["derive"] }
+serde_json = { workspace = true }
+libssh-rs = { workspace = true }
+# Same escaping ares-connection-lib uses, so a command built here and one
+# built there quote identically.
+snailquote = "0.3.1"
+
+[package.metadata.deb]
+section = "devel"