client-api-wire-shape-verification

API wire shape drift causes runtime 400 errors when field names, types, or nullability differ between your typed request<T>() wrapper and the backend route handler. Diffing the actual backend response JSON against client TypeScript types identifies the mismatch.

Verify Prisma to TypeScript mappings by checking your client wrapper shapes against actual backend source code, including route handlers, Prisma query returns, and body validators, rather than relying on stale plan documents or schema guesses to ensure exact field-name and nullability alignment.

The best way to prevent type drift is enforcing a pre-commit verification checklist that cross-checks typed request<T>() calls against actual backend route handlers and Zod schema body validators. This catches field-name, type, and nullability mismatches before shipping code.

Yes, you can use it to align Zod schemas with backend DTOs. It specifically guides full-stack TypeScript workflows to validate client wrapper shapes against actual backend body validators and route handlers when separate agents or teams implement frontend and backend endpoints.

Yes, it supports optional automated wire-shape round-trip tests for end-to-end validation. These tests enforce verification of client wrapper shapes against actual backend source code to catch silent runtime crashes caused by type and nullability drift.

You should not rely on plan documents when the actual backend implementation has diverged, causing stale schema guesses. Relying on outdated Prisma model assumptions instead of actual route handlers and query returns leads to silent runtime crashes and API 400 errors.