JSON-to-Zod converters silently drop type safety on emails, UUIDs, timestamps

A developer tested two JSON-to-Zod converters with a typical API response and found both reduced fields like email, UUID, and ISO timestamp to plain z.string(). The schema compiled without errors, but validators would accept invalid data like "not-an-email" or "2026-99-99". The post warns that such tools can introduce silent validation gaps in production code.