openapi.json fails to take into account servlet context path, produces bad spec file

i have a jax-rs application, packaged in a war, deployed on tomcat with a non-empty context path (so at http://host:port/war-name). the ApplicationPath is /api

the openapi.json generated currently looks like this:

{
  "openapi": "3.0.1",
  "paths": {
    "/api/someResourcePath": {
      "get": { }
    }
  }
}

this produces a non-working descriptor as it fails to take into account the context path my war is deployed at. it should probably look like:

{
  "openapi": "3.0.1",
  "servers":[
    {"url": "/war-name"}
  ],
  "paths": {
    "/api/someResourcePath": { }
  }
}

Start by tracing OpenAPI generation through the servlet deployment integration and locate where the request context path is available. Reproduce the WAR deployment under a non-empty Tomcat context path, then verify that the generated descriptor includes a server URL for that context while retaining the ApplicationPath in its paths.