Cannot assert on actual headers: Rack mutates header key

Given an OpenApi3 swagger yaml definition for a header:

x-Role: &Role
  in: "header"
  name: "Role"
  required: true
  schema:
    type: "string"
    enum: ["A", "B"]

And given a valid request:

curl ... -H "Role: A"

Committee, when raising an error, raises the following error for this request:

Committee::InvalidRequest:
       #/paths/... missing required parameters: Role

This is because Rack mutates all http headers, and Role becomes HTTP_ROLE.

This would seem unrelated to this gem, except that it is designed as Rack middleware, so it seems odd that it wouldn't work with rack conventions.

I'm not too familiar with the gem yet, but a first idea for a solution might be to cast all swagger-defined headers into HTTP_x formats before passing to validation.

Reproduce the OpenAPI 3 header example with the shown curl request, then trace the Rack middleware boundary and request-header validation path. Confirm that a required Role header is recognized despite Rack's HTTP_ROLE convention; done means the request validates without the missing-parameter error.