fix groq and cerebras clients

[seanmcguire12]

why

• both groq and cerebras clients were not returning the response in the correct shape

what changed

• updated groq and cerebras clients to return an object with the expected shape:

const finalResponse = {
  data: result,
  usage: response.usage,
};

test plan

• tested with evals locally

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5ab9a6b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[greptile-apps]

PR Summary

Added consistent response formatting and error handling for Groq and Cerebras LLM clients to ensure proper data shape and usage metrics.

• Added structured response format { data: result, usage: response.usage } in both clients
• Improved JSON parsing from tool calls and content with proper error handling
• Added caching support for both raw and formatted responses
• Enhanced retry mechanism (up to 5 attempts) for failed JSON parsing
• Added comprehensive logging for response handling and errors

_{2 file(s) reviewed, 2 comment(s)
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

logic: Regex pattern /{[\s\S]*}/ may match nested JSON objects incorrectly, leading to invalid parsing

[greptile-apps]

logic: regex pattern /{[\s\S]*}/ could match nested JSON objects incorrectly or match the first {} it finds instead of the complete JSON object