grok-cli-runtime

# Grok runtime Primary helper: - `node "${CLAUDE_PLUGIN_ROOT}/scripts/grok-companion.mjs" <subcommand> [flags]` Subcommand surface: - `task [--prompt-file <path>] [--write] [--web] [--memory] [--background] [--resume <uuid>] [--resume-last] [--fresh] [--model <id>] [--effort <level>] [--max-turns <n>] [--cwd <dir>] [--json] [--] [prompt]` - The upstream Grok CLI has no default turn limit. An unset limit is unlimited, and one turn is one main-agent model call plus its tool cycle, excluding subagent calls. The companion defaults consult and write to `--max-turns 60`; consult previously defaulted to 25. When the limit is reached, Grok prints the complete final JSON envelope to stdout, including partial text, usage, `num_turns`, and `modelUsage`, then exits 1 with stderr `Error: max turns reached`. The companion salvages that envelope and records `failureKind: "turn_limit"`. - Grok headless JSON has no top-level `model` field. Model names are available only as keys in `modelUsage` when usage attaches, so model capture depends on that map and on error-path salvage. Missing `modelUsage` leaves the resolved model unavailable. - `review [--base <ref>] [--focus <text>] [--cwd <dir>] [--background] [--json]` - `status [job-id] [--cwd <dir>] [--json]` - `history [--all] [--limit <n>] [--cwd <dir>] [--json]` - `result <job-id> [--cwd <dir>] [--wait] [--wait-timeout-ms <ms>] [--json]` - `cancel <job-id> [--cwd <dir>] [--json]` - `stats [--all] [--cwd <dir>] [--json]` - `setup [--conti...