🔒 Fix Unsafe JSON.parse of LLM output

[redNSF]

🎯 What: The application was directly parsing LLM output via JSON.parse without explicitly handling syntax errors.
⚠️ Risk: If the LLM generates invalid JSON, JSON.parse throws an error. Previously, this error fell into a generic catch block that returned the raw error.message to the client. This could lead to a denial of service (unhandled exceptions in some contexts) or exposure of sensitive stack trace/parser information.
🛡️ Solution: Wrapped JSON.parse in a specific try/catch block. If parsing fails, the API now logs the error internally and returns a sanitized, generic 500 error message (Invalid JSON response from LLM) to the client. Additionally, the outer catch block was updated to use error: unknown instead of any, improving TypeScript safety and complying with project conventions.

---

PR created automatically by Jules for task 5888121746191579623 started by @redNSF

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
motionbrief	Ready	Preview, Comment	Apr 1, 2026 1:19pm