Contract-first extension scope

[flazarus1A]

Hello, there is one thing I don't fully understand for the contract-first extension.

Based on this comment, its purpose is to reduce the burden for the developer by feeding the MicroProfile configuration from the AsyncAPI document.

Do you envision to extend it with code generation à la quarkus-openapi-generator? In its current state, nothing seems to prevent me from building a Quarkus application producing or consuming events that don't match at all the schemas in my AsyncAPI document.