[waleedlatif1]

Summary

• A v2 4xx logs only Client error response with its status, so a 400 from bad input can't be told apart from one the API refuses by design without reproducing the call
• v2Error records the response's error.code, plus its details.code when the refusal names one, against the response object it builds. v2ValidationError adds the slice and its top-level field (body.mapping) and the Zod issue kind (invalid_type)
• withRouteHandler reads that summary off the response it actually returns and adds errorCode / errorField / errorReason to its closing line. A response built only to extract a message is never logged
• Never logged: the message, which can quote user input, and path segments below the top-level field, which can be record keys the caller wrote (e.g. CSV headers)

Type of Change

• Improvement

Testing

• Ran the real v2ValidationError / v2Error helpers: a record-key failure logs body.mapping while the response still names the full path; details.code comes through as the reason; an untagged response reads back nothing
• app/api/v2/lib and with-route-handler tests (33) pass; biome, check:comment-hygiene, check:test-patterns clean; CI runs the rest

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing (new tests pass the test-audit authoring gate)
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

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

1 Skipped Deployment

Project	Deployment	Actions	Updated
docs	Ignored	Preview	Nov 14, 2026 2:33am UTC

[cubic-dev-ai]

All reported issues were addressed across 4 files

<sub>Reply with feedback, questions, or to request a fix.

Turn on auto-fix | Re-trigger cubic</sub>

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge.

Summary

Adds response-specific error details to the route handler’s closing error log.

• V2 request logs show why API errors were returned.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A[v2 error helper] --> B[Response]
  A --> C[WeakMap summary]
  B --> D[Route returns response]
  D --> E[Closing error log]
  C -->|Look up returned response| E

Loading

_{Reviews (2) · Last reviewed commit: "improvement(api): tag the returned respo..." · Reviewed by Greptile}

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 3 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Turn on auto-fix | Re-trigger cubic}