alera-emulator

# Alera Mobile Emulator Use `alera emulator` to work with the single mobile-emulator tab associated with an Alera workspace. The runtime host owns device discovery, helper processes, input, observations, and lifecycle. Do not start `adb`, `emulator`, `simctl`, `scrcpy`, or `serve-sim` directly when this command surface is available. ## Check Capabilities First ```bash alera emulator --json capabilities ``` Read the backend-specific capability flags before planning an operation. Android and iOS do not expose identical actions. An unsupported operation returns `unsupported_capability`; use a supported alternative or stop instead of retrying unchanged. `--json` belongs to the command group, before the subcommand: ```bash alera emulator --json devices --platform android ``` Replies deliberately omit private stream URLs and tokens. The embedded Alera tab consumes those credentials internally; agents do not need them. ## Resolve The Target Commands that operate an attachment resolve their target in this order: 1. `--tab-id` 2. `--workspace-id` 3. `ALERA_WORKSPACE_ID` `ALERA_TAB_ID` identifies the terminal running the command and is never treated as the emulator tab. Use `--tab-id` only with an emulator tab id returned by `list` or `attach`. ## Discover And Attach ```bash alera emulator --json devices alera emulator --json devices --platform ios alera emulator --json attach --workspace-id <workspace-id> --platform android --device-id <avd-name> alera emulator --json lis...