parsedSpec has this super unique format (operations are mounted under tags, the operations are basically moved inside an information key, and just a few top-level properties). parsedSpec is used in a lot of places, but here are the biggest areas:

Sidebar

See #5646

Search

Content

it’s looping through the tags, and through the operations that are mounted inside the tags, don’t forget there is a way to sort tags and operations through the configuration)

We want to get rid of it, and work with a plain OpenAPI 3.1 object instead. The new object can be just the result of upgrade() and dereference().