Commit & PR Description Writer

fix: repair unescaped control chars in model JSON before failing JSON.parse on the sliced response was throwing whenever the model put a literal newline inside a string instead of an escaped one. That's invalid JSON but the content itself was usually fine, so users were getting a 502 for no real reason. Now we try a strict parse first, and only if that fails do we repair control characters inside string literals and retry. If that also fails we throw like before. Moved the parsing logic into its own module (src/lib/model-json.ts) since anthropic.ts imports server-only, which blocks importing it from a test script.

Fixes spurious 502s caused by the model returning JSON with a literal newline (or other control character) inside a string value instead of an escaped one. That's technically invalid JSON, so the old parse (JSON.parse on the slice between the first and last brace) would throw immediately even though the actual content was fine. What changed: - Added src/lib/model-json.ts with the parsing logic: try a strict JSON.parse first, and only if that fails, repair control characters inside string literals and retry. - If the repaired parse still fails, it throws like before, so real parse failures still surface as errors. - Moved this out of anthropic.ts into its own module because anthropic.ts imports server-only, which made it impossible to import the parsing logic from a test script.