create-test-run

## Overview Turn a "run this" request into a created test run with as little friction as the user wants, then offer to watch it. Two phases: 1. **Build + confirm the run.** Resolve what to run (test case or suite), on which devices, with what app — filling any unspecified field with a documented default — then show a one-screen summary and create on confirmation. 2. **Offer monitoring once.** After creation, present the monitor choice in a single prompt and delegate to `monitor-test-run` if the user wants it. > **Tool naming.** Kobiton MCP tools are referenced by bare name (`createTestRun`, > `getOrgSettings`, `listDevices`, `getTestCase`, `getTestSuite`). The host > resolves the prefix (`mcp__plugin_automate_kobiton__createTestRun`, > `mcp__kobiton__createTestRun`, etc.). ## Inputs | Input | Required | Notes | |-------|----------|-------| | test case id **or** test suite id | one of | A test case id → `TEST_CASE` selection; a suite id → `TEST_SUITE`. If the user named neither, ask for it (it's the one thing with no sensible default). | | device count / specific devices | no | Default: 1 device matching the test case/suite platform. The user may say "3 devices", name models, or give UDIDs. | | run name / app version / allocation | no | All defaulted (see Step 2). | ## Steps ### 1. Resolve the target and its platform - A **test case id** → fetch it (`getTestCase`) to learn its platform and the app under test. Selection will be `TEST_CASE` with `testCaseSelec...