[chrarnoldus]

Summary

• Introduce formatZodError / formatZodIssues to unwrap and format Zod validation issues, including invalid_union branches and unrecognized_keys.
• Fix the Custom LLM editor so validation failures on union schemas (such as API key vs Google service account auth) surface actionable field-level error messages instead of : Invalid input.
• Validate public_id prefix client-side before submission for immediate feedback.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Executive Summary

Reviewed the custom-LLM validation-error formatting fix end to end — new formatZodError/formatZodIssues helpers with union branch selection, 207 lines of tests, and the admin editor integration — and found no correctness, security, or memory-leak issues in the changed code; the union branch-selection logic, tRPC data.zodError/JSON-message fallbacks, and trimmed public_id handling were all verified against the actual CustomLlmDefinitionSchema, the tRPC error formatter, and zod 4.4.3 issue types.

Files Reviewed (3 files)

• apps/web/src/app/admin/custom-llms/CustomLlmsContent.tsx
• apps/web/src/lib/zod/format-zod-error.ts
• apps/web/src/lib/zod/format-zod-error.test.ts

---

_{Reviewed by kimi-k3 · Input: 84.6K · Output: 17.2K · Cached: 590.7K}

_{Review guidance: REVIEW.md from base branch main}