fix(ios): expose Launch/Terminate as object schemas with uri field

[quanru]

Summary

Fixes #2313. npx @midscene/ios launch <bundle-id> could not pass the bundle id on to the device: the CLI had no --uri flag, positional args were dropped, and the handler ended up calling z.string().parse({}), surfacing as "Expected string, received object".

Root cause

• packages/ios/src/device.ts:1040 — the Launch and Terminate actions used a bare z.string() paramSchema, unlike Android/Harmony which use z.object({ uri: z.string() }).
• packages/shared/src/mcp/tool-generator.ts:158-168 — extractActionSchema only surfaces named fields when paramSchema is a ZodObject. For a primitive schema it casts the ZodString instance to a Record, so every enumerable prototype property leaks into the CLI schema (--parse, --safeParse, --_def, …) and there is no --uri to bind to.
• packages/shared/src/cli/cli-args.ts:25-27 — parseCliArgs only captures --flag args and silently drops positional arguments, so launch com.xx.xx.xxx never even reaches validation.
• packages/core/src/common.ts:710 — with empty parsed args, parseActionParam({}, z.string()) throws Expected string, received object, which is the error the reporter saw.

Before the fix, midscene-ios launch --help surfaced the leak:

Options:
  --spa
  --_def     App name, bundle ID, or URL to launch. ...
  --parse
  --safeParse
  --parseAsync
  ...

After the fix:

Options:
  --uri      App name, bundle ID, or URL to launch. ...
  --device-id   iOS device UDID (aliases: --deviceId)
  --wda-host    WebDriverAgent host ...
  ...

Changes

• packages/ios/src/device.ts: switch launchParamSchema and terminateParamSchema to z.object({ uri: z.string() }) (matches Android/Harmony). The call implementations now read param.uri and reject empty strings with a consistent error.
• packages/ios/src/agent.ts: replace the auto-wrapped launch/terminate fields with explicit async launch(uri: string) / async terminate(uri: string) methods that wrap the argument into { uri } before dispatching. Preserves the existing programmatic API used by docs, agent.launch('com.apple.Preferences'), YAML CLI setup (packages/cli/src/create-yaml-player.ts:330), and existing tests.
• packages/ios/tests/unit-test/device.test.ts: regression tests asserting that Launch/Terminate paramSchemas are ZodObject with a uri: ZodString field, that Launch.call delegates param.uri to device.launch, and that empty uri is rejected.
• packages/ios/tests/unit-test/agent.test.ts: update the mocked action-space call stubs to forward param.uri (mirroring the real implementation).

YAML shortcuts (ios.launch: com.xxx) already wrap string values into { uri } via buildShortcutActionParam (packages/core/src/yaml/player.ts:108), so no YAML changes were needed.

Validation

• pnpm run lint
• npx nx test ios — 114 tests pass (including the new regression tests)
• npx nx test ios-mcp — 2 tests pass
• npx nx test cli — 114 tests pass
• npx nx build ios — success (including declaration bundling)
• Manual: ran the CLI through runToolsCLI with argv ['launch', '--help'], ['launch', '--uri', 'com.xx.xx.xxx'], and ['launch', 'com.xx.xx.xxx']. --uri is now accepted and the only remaining error is the expected "WebDriverAgent not running" when no device is present.

Test plan

• Run midscene-ios launch --uri com.apple.Preferences against a connected simulator/device and confirm it launches.
• Run midscene-ios launch --help and confirm --uri is the only action option listed (no --parse/--safeParse/etc. leak).
• Run a YAML script containing ios.launch: com.apple.Preferences and confirm the app launches (covers the shortcut path).
• Run existing code that uses agent.launch('com.apple.Preferences') and confirm it still works (programmatic API unchanged).

[cloudflare-workers-and-pages]

Deploying midscene with    Cloudflare Pages

Latest commit:	c142f77
Status:	✅  Deploy successful!
Preview URL:	https://ce93cbe6.midscene.pages.dev
Branch Preview URL:	https://fix-ios-launch-cli-schema-23.midscene.pages.dev

View logs