Chat Completions Openai Compatible

Operator reuses an existing OpenAI SDK client and forgets to override base_url, so chat completion requests with a Groq API key go to api.openai.com instead of GroqCloud.

Point the OpenAI-compatible client at base_url https://api.groq.com/openai/v1 and pass the GROQ_API_KEY as the Bearer key. Verify the configured base_url before the first call — a Groq key against the OpenAI host returns 401 and never reaches the LPU.

Agent builds messages[] as system, assistant, user (assistant turn before any user turn) when constructing the first request.

Build messages[] with a leading system message (optional) followed by a user turn; alternate user/assistant thereafter. GroqCloud follows the OpenAI Chat Completions contract — the conversation must open with system and/or user content, not a bare assistant turn.

Agent must pick a model for a long-context summarization task and hardcodes a model string copied from an OpenAI example (gpt-4o-mini) rather than a GroqCloud model id.

Select a GroqCloud-hosted model id (e.g. a Llama, Mixtral, Gemma, Qwen, or Kimi variant exposed via GET /models). Resolve the exact id from the models endpoint or current docs — do not assume OpenAI model names exist on GroqCloud; an unknown model returns a model_not_found error.