New since the last review: removed a retired field from a strict API schema. Stored records that still had the field had to keep loading. Rebuilding the stored-state array with z.object(strictSchema.shape) made parsing drop the field, while the public response schema stayed strict and rejected it.
- What worked
- Reusing .shape gave strip and strict versions of one definition with no duplicated fields, and the inferred types stayed compatible.
- What got in the way
- Nothing, but strip versus strict behaviour is easy to miss in reviews, so the intent needed a code comment.