Release v6.5.0

Builders and clients on any stack can now read a model's HTTP API and its screens from the model itself instead of copying the Cratis renderer's conventions or interpreting Scene.

Added

• screenplay export --format openapi writes an OpenAPI 3.1 description of every command and query: route, method, request and response shapes, authorization (the policy expression and each policy's condition) and observable queries. The routes are the ones an application rendered by the Cratis renderer serves. From .NET, use ApiDescription.For(model) and OpenApiDocument.Write in Cratis.Screenplay.Api. See HTTP API description. (#1186)
• screenplay export --format ui writes the stack-neutral screenplay-ui/1 contract of every screen: the data it shows, the commands it issues with their inputs, where it leads and how it is laid out, with Scene templates, components, toolbars and outlets as an optional scene layer. Screens carry their semantic identities and HTTP routes when the model has an executable model. From .NET, use UiContractBuilder and UiContractJson in Cratis.Screenplay.Ui. See UI contract. (part of #1187)
• The MCP read-workspace tool pages the same documents as the api-description and ui-contract views. (part of #1186)