[diegosouzapw]

Fixes CI failure on main (check:route-validation:t06).

The route was using TestRequestSchema.parse(await request.json()) directly, which is flagged by the gate. Replaced with the canonical validateBody() + isValidationFailure() pattern from @/shared/validation/helpers.

[gemini-code-assist]

Code Review

This pull request refactors the request body validation in the guardrails test route to use the helper functions validateBody and isValidationFailure instead of calling TestRequestSchema.parse directly. The reviewer suggested enhancing the error response when validation fails by including detailed error information (validation.error.details) in the response payload to provide clients with more actionable feedback.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

When validation fails, the validation object contains detailed error information in validation.error.details. Passing these details to createErrorResponse will provide clients with actionable feedback about which fields failed validation.

  if (isValidationFailure(validation)) {
    return createErrorResponse({
      status: 400,
      message: "Invalid request body — expected { input: string | object | array, disabledGuardrails?: string[] }",
      type: "invalid_request",
      details: validation.error.details,
    });
  }

[github-actions]

CI Coverage Report

• Coverage job: cancelled
• PR test policy: success

Coverage artifact was not available for this run.

[kilo-code-bot]

WARNING: Error message for invalid JSON changed from the schema description to a short "Invalid JSON body" string

Previously, the single catch block returned the same message for both invalid JSON and schema validation failures. After this refactor, invalid JSON now returns "Invalid JSON body" while schema validation still returns the detailed "Invalid request body — expected { input: string | object | array, disabledGuardrails?: string[] }" message. This behavioral change could break client-side error handling that depends on matching the exact error message string.

If the goal is to keep error messages consistent, consider:

• Using the same descriptive message for both error paths, OR
• Exposing a machine-readable discriminator (e.g., error type/code) that clients can depend on instead of the message string.

[kilo-code-bot]

Code Review Summary

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity	Count
WARNING	1

Issue Details (click to expand)

WARNING

File	Line	Issue
src/app/api/guardrails/test/route.ts	36	Error message changed for invalid JSON — returns generic "Invalid JSON body" while schema failure returns detailed description. Clients matching error string messages will break silently.

Files Reviewed (1 file)

• src/app/api/guardrails/test/route.ts - 1 warning

---

_{Reviewed by step-3.7-flash-20260528 · 264,808 tokens}