Openapi

Everything under Quiote\Openapi.

Classes

Class	Description
OpenApiGenerator	Derives an OpenAPI 3.1 document from things the app already declares: the routing IR says which paths and verbs exist and which action each resolves to, each action’s own validators say which parameters it accepts and what they must look like (via ActionInputSchemaResolver, the same derivation that gives an MCP tool its inputSchema), the output type says what media type a successful response carries, and ProblemDetails says what a failure looks like.
OpenApiOptions	The document-level knobs OpenApiGenerator can’t derive from code: info, servers, and which routes to describe at all.
RoutePathTemplate	A route path parsed into the shape OpenAPI wants: a template whose placeholders are bare {name}, plus what the placeholders’ inline syntax said about them.