[Feature] enable users to more fully configure what's "enforced" in a contract

[graciegoheen]

Describe the feature

Similar to #10195, which asks to support constraints independently from enforcing a full model contract. A few other configurations would be helpful to users:

• "I want my contract to only enforce a subset of columns, but I want to allow for schema evolution."
• "I want my data tests to be enforced as part of the contract." (related to Write Audit Publish)
• "I want model freshness to be enforced as part of the contract."

Describe alternatives you've considered

No response

Who will this benefit?

No response

Are you interested in contributing this feature?

No response

Anything else?

No response

[abhishek09827]

Hi @graciegoheen , I’d like to work on this.

I’ve looked into the requirements:
Data Tests & Freshness Enforcement: By extending ContractConfig and modifying RunTask to trigger these checks as part of the contract.
Partial Config Support: Adding the configuration structure to allow decoupling constraints from full enforcement (even if adapter support follows later).
Could you please assign this issue to me?