Regenerate API data from Aspire 13.6.0 staging build f4c27f2d

src/frontend/src/content/docs/integrations/dotnet/blazor-hosting.mdx

@@ -254,8 +254,9 @@ builder.Build().Run();
 
 <Aside type="caution" title="Experimental">
   `AddDotnetProjectBlazorGateway` and its `WithBlazorClientApp` overload
-  carry `ASPIREDOTNETPROJECT001`, in addition to the
-  Blazor integration's `ASPIREBLAZOR001` diagnostic. These gateway APIs are
+  report their own `ASPIREDOTNETPROJECT001` diagnostic. The Blazor
+  integration's `ASPIREBLAZOR001` diagnostic applies to other experimental
+  Blazor hosting types, such as `BlazorWasmAppResource`. These gateway APIs are
   experimental independently of the core Dotnet project APIs. This gateway
   runs as a file-based C# app and supports both `aspire run` and publishing.
   For details on suppressing the diagnostic, see

src/frontend/src/content/docs/whats-new/aspire-13-6.mdx

@@ -157,7 +157,7 @@ Other dashboard improvements include:
 
 - The dashboard ships as Native AOT and uses Fluent UI v5. Normal startup selects the packaged dashboard automatically, without a new configuration switch.
 - Pinning or unpinning a historical run keeps the selector open and preserves the current selection.
-- The empty terminal dock shows **No docked terminals**, a **More information** link, and the backtick-key hint for hiding the panel.
+- The backtick key opens and hides the terminal dock; the dashboard header and mobile navigation don't include a terminal entry. The empty dock shows **No docked terminals** and a **More information** link.
 - Management UI integrations expose **Manage** links on the resources they administer, reducing the need to find a separate management container.
 - The `azure-environment` resource uses a filled cloud icon instead of the generic resource icon.
 - Cross-origin or malformed `/_blazor` WebSocket upgrades are rejected before a dashboard circuit is allocated.