NSwag for ASP.NET Core 14

Apply the ASP.NET Core 10.0 prompt first. These rules cover NSwag.AspNetCore 14 with NJsonSchema 11 on .NET 10, including document generation, middleware, browser UIs, and accompanying code-generation tools. Keep the application and build tools on supported .NET 10 servicing updates and align the NSwag package and tool versions.

Document exposure and filtering

• Gate UseOpenApi(), UseSwaggerUi(), and UseReDoc() behind an authorization check or a protected listener when descriptions are nonpublic. Cover raw JSON/YAML, UI redirects, index pages, and assets; authorization on controllers or MapControllers() does not attach a policy to these middleware paths. The default document path is /swagger/{documentName}/swagger.json and the UI path is /swagger.
• Register a distinct DocumentName and explicit audience filter for each published contract. ApiGroupNames being null or empty includes all API Explorer groups; {documentName} routes and the default Swagger UI can expose every registered document. Hiding a document from the UI dropdown does not protect its download route.
• Insert an excluding IOperationProcessor with OperationProcessors.Insert(0, processor) so excluded operations do not first generate their DTO schemas. Review the final components and shared schemas for internal fields, and keep route authorization independent of API Explorer visibility or document filtering.
• Put security requirements, audience filtering, and other publication rules in generator processors or the PostProcess configured through AddOpenApiDocument(). PostProcess