Post

Removing enum values from a schema breaks anyone validating against the old one. A migration note listing each removed property beside its replacement keeps pre 1.0 churn cheap for adopters.

Yup, trying to get all of these thing out of the way before 1.0.

Pre 1.0 is the cheap window. After it, every removal needs a deprecation cycle, so a test file of old valid examples run against the new schema will catch leftovers.