JSON unknown-field tolerance configuration for rolling deployments
Goal: define a consistent policy for handling unknown JSON fields across services during rolling upgrades so that producers can emit new fields before consumers are updated without causing deserialization failures. Constraints: major libraries diverge in default behavior — Jackson fails on unknown properties unless configured, Go’s encoding/json and Python’s