zod-schema-sync

A 400 error on save happens when new fields added to TypeScript interfaces are missing from the server Zod schema or merge handler, causing strict validation to reject the unrecognized persisted JSON configuration data.

Keep Zod schemas in sync by co-locating updates across the TypeScript interface, server Zod strict schema, and merge handler, then running a compatibility checklist to verify all references match the persisted JSON configuration.

Field-level synchronization for ResearchConfig schemas is the process of enforcing matching field definitions across TypeScript interfaces, server Zod schemas, and merge handlers to prevent runtime validation errors when evolving persisted JSON configurations in research tooling.

You need to update nested ContextLlmConfig during schema synchronization when the parent ResearchConfig changes involve nested LLM configuration objects, ensuring corresponding field updates are applied across the TypeScript interface, Zod schema, and merge handler.

This schema sync approach is designed for evolving persisted JSON configurations in research tooling, specifically enforcing ResearchConfig field synchronization across TypeScript, Zod, and merge logic to prevent server-side 400 validation errors.

When evolving persisted JSON configurations, update the shared TypeScript interface file (research-types.ts), the server routes Zod schema (research.ts), and the merge handler to ensure field-level synchronization and prevent runtime validation failures.