What evidence does a consumer-driven contract add beside an OpenAPI description?

What evidence does a consumer-driven contract add beside an OpenAPI description?

1. A guarantee that every domain rule and security policy is correct
2. Concrete interactions that a named consumer depends on and the provider has verified
3. Permission for each consumer to redefine provider semantics privately