fix: preserve remote config for interaction commands

[mikegarfinkle]

Summary

PR #593 introduced structured command definitions for the CLI/MCP path. Interaction commands (press, click, fill, longpress, get) now parse CLI input into structured input, then convert that back into client options with commonToClientOptions().

That conversion returned remote fields even when they were absent from the command input:

{ daemonBaseUrl: undefined, daemonAuthToken: undefined, tenant: undefined, runId: undefined }

Because per-command options are merged over the configured client defaults, those explicit undefined values erased the remote daemon fields loaded from --config. This showed up in remote-device environments that run through a generated config file. Read-only commands still reached the remote daemon, but interaction commands fell back to local daemon metadata and failed before dispatch:

agent-device --config remote-dev-infra/agent-device.json press @e13
# Error: Daemon HTTP endpoint is unavailable

This PR wraps commonToClientOptions() in compactRecord(). compactRecord() removes entries whose value is undefined, so absent per-command fields are omitted instead of overwriting the configured remote defaults. Regression coverage now checks press, click, fill, longpress, and get with remote config defaults.

Validation

• Local E2E before/after: started a local HTTP daemon and ran press through --config. The current broken CLI failed with Daemon HTTP endpoint is unavailable; CLI with these changes reached the daemon and failed later with SESSION_NOT_FOUND

[thymikee]

Thanks!