grok-result-handlinglisted

# Grok result handling When the helper returns Grok output: - Return the companion output verbatim, whether the Bash tool reports it from stdout or stderr. Do not paraphrase, summarize, or add commentary before or after it. - Keep the grok-session and job lines; the user needs them to resume or inspect the run. - Preserve reported request id, turn count, aggregate and per-model token usage, cost, partial-cost, incomplete-usage-ledger, and structured-output fields. Grok headless JSON has no top-level `model` field; model names come only from `modelUsage` keys when usage attaches, including a salvaged error envelope. Upstream per-model entries contain input, output, cache-read, and model-call counts plus optional cost; never invent aggregate reasoning or total tokens. When `usage_is_incomplete` is true, present counts are observed lower bounds and both job-total token and cost coverage are incomplete. Missing values stay missing; do not infer zero or exactness. - A Grok max turns outcome preserves the complete final JSON envelope, including partial text, usage, `num_turns`, and `modelUsage`, even though the process exits 1 with stderr `Error: max turns reached`. Treat its `failure: turn_limit` as a sizing result, not an engine health failure. - For review output, keep findings ordered by severity and use the file paths and line numbers exactly as the helper reports them. - If there are no findings, say that explicitly and keep the residual risk note brief. - If Grok made edit