Compose all component types, not just schemas

The current state of affairs is that responses can be defined as components and referenced with the "$ref":"{uri}" syntax, but these cannot be composed using the allOf directive. Trying to do so results in an error. Adding sibling properties also results in an error. So there is currently no way to define a response with a general schema and then add endpoint-specific models or examples. This seems like a gross oversight and major limitation.

For example, let's say that there are multiple endpoints that return lists of models following a standard response format, but each endpoint returns different models. It would be ideal to keep the reusable format of the response in a response component and compose it with the specific model under the path definition.

Without this functionality, the only options are to have invalid documents or abandon the use of response components.

Start by reviewing the response component rules, $ref syntax, allOf composition, and sibling-property restrictions described in the specification. Define the expected behavior for composing a reusable response with endpoint-specific models or examples, then document and validate an example showing that the resulting document is valid.