release: v0.4.10 — fix silent --device failures, real physical-device support

[justrach]

The bug

Every --device command silently did nothing and reported success.

devicectl.zig shelled out to bare xcrun devicectl. xcrun resolves through xcode-select, which on this machine points at CommandLineTools — where devicectl does not exist. Combined with io.runCommand not checking exit status, the failure was swallowed entirely.

# before
$ kuri-mobile ios launch --device --udid FAKEUDID com.foo.bar
$ echo $?
0        # did nothing whatsoever

# after
$ kuri-mobile ios launch --device --udid FAKEUDID com.foo.bar
devicectl failed (exit 1): ERROR: The specified device was not found. (Name: FAKEUDID)
error: the Xcode tool reported a failure (see the message above).
$ echo $?
1

This is the same bug class fixed for simctl in 0.4.6 — devicectl was missed. It now goes through the Xcode resolver by absolute path with a checked exit status.

A second latent bug: listDevicesJson passed --json-output -, but devicectl states that writing JSON to a file on disk is the only supported machine interface — it never writes JSON to stdout. That call would have created a file literally named -.

Physical device support

With the plumbing fixed, real devices gain genuine support:

Command	Before	After
install / uninstall	simulator only	✅ devicectl
list-apps	errored on --device	✅ devicectl
launch / terminate	silently no-op	✅ works
device-info, device-processes, lock-state, displays, reboot	—	✅ new

lock-state is worth calling out: automation that appears to do nothing because the screen is locked is a common and confusing failure, and this makes it checkable.

Verified against a real paired iPhone (iPhone 16 Pro Max) — device-info returns actual hardware properties.

Scope, stated honestly

devicectl exposes no screenshot and no UI hierarchy. So tap/swipe/type/uitree/screenshot remain simulator-only no matter what is plugged in — those genuinely need XCUITest. The registry's scope field now reflects reality exactly:

41 tools | {'simulator': 29, 'simulator+device': 7, 'device': 5}

An agent reading ios tools --json can now tell "won't work on your phone" from "not set up yet" without trying it.

Verification

All four release targets build; test, test-fetch, test-browse, kuri-mobile's suite all exit 0; e2e-ios SKIPs cleanly with no simulator booted.

Not verified: no iOS device is currently connected (all three paired devices report unavailable), so the write paths — install --device, uninstall --device, reboot — are exercised only through the error path. device-info against a paired-but-disconnected device does return real data.

🤖 Generated with Claude Code

https://claude.ai/code/session_012gzdKWXk7UbHm5TtSGqYBJ