[docs] Document MongoDB EF Core net10.0 support and dependency consolidation

src/frontend/src/content/docs/integrations/databases/efcore/mongodb/mongodb-efcore-get-started.mdx

@@ -26,7 +26,7 @@ Adding MongoDB through Aspire — rather than wiring up containers and connectio
 - **Automatic connection configuration.** When a consuming C# project references the MongoDB database resource, Aspire injects connection details automatically so your app finds them through dependency injection.
 - **Built-in health checks.** The hosting integration automatically registers a health check so the dashboard and your orchestrator can tell when the server is ready.
 - **Dashboard observability.** The database resource shows up in the Aspire dashboard with logs, status, and telemetry alongside your other services.
-- **A first-class C# client integration.** C# apps use the `Aspire.MongoDB.EntityFrameworkCore` package to register a `DbContext` through dependency injection, with health checks, logging, tracing, and metrics all wired up automatically.
+- **A first-class C# client integration.** C# apps use the `Aspire.MongoDB.EntityFrameworkCore` package to register a `DbContext` through dependency injection, with health checks, logging, tracing, and metrics all wired up automatically. The package targets `net8.0`, `net9.0`, and `net10.0`.
 
 ## How the pieces fit together
 

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

@@ -706,6 +706,7 @@ Existing integrations add new workflows and safer defaults:
 - **Deno hosting.** `Aspire.Hosting.JavaScript` adds experimental `AddDenoApp` / `addDenoApp`, which runs a script from an app directory, with task and serve modes, permission controls, and runtime flags. These APIs report `ASPIREDENO001`, and Deno must be installed for local execution. The first-party API differs from the Community Toolkit's [Deno integration](/integrations/frameworks/deno/deno-host/).
 - **MongoDB replica sets.** Experimental `WithReplicaSet` / `withReplicaSet` configures and initializes a single-member replica set, enabling transactions and change streams after readiness. A separate `AddMongoDBReplicaSet` API supports multi-member local scenarios. Both paths are local-run-only and reject publishing; see [MongoDB replica sets](/integrations/databases/mongodb/mongodb-host/#enable-transactions-and-change-streams-with-a-single-member-replica-set).
 - **MongoDB automatic TLS.** Local MongoDB resources now use Aspire's shared certificate configuration, including standalone servers. Existing plaintext clients should review the [TLS migration guidance](#mongodb-now-uses-automatic-tls-during-local-runs).
+- **MongoDB EF Core now targets .NET 10.** `Aspire.MongoDB.EntityFrameworkCore` adds a `net10.0` asset alongside `net8.0` and `net9.0`, using `MongoDB.EntityFrameworkCore` 10.0.4 on that target. `MongoDB.Driver` is now 3.12.0 across all target frameworks, and the redundant explicit `Snappier` package reference was removed now that `MongoDB.Driver` 3.12.0 requires a compatible version directly. See [MongoDB EF Core integrations overview](/integrations/databases/efcore/mongodb/mongodb-efcore-get-started/).
 - **Microsoft Foundry Toolboxes.** `AddToolbox` / `addToolbox` bundles tools behind one MCP endpoint and manages immutable versions as tool configuration changes. MCP approval policies are discovery metadata that the consuming application must enforce. See the [Toolbox walkthrough](/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-host/#add-a-toolbox).
 - **Remote Foundry Local services.** `RunAsFoundryLocal` / `runAsFoundryLocal` now accepts an endpoint, so an AppHost, including one on WSL2 or Linux, can observe a Foundry Local service already running on another host (for example, a Windows GPU box) without starting, stopping, or downloading models on it. The integration also handles the newer `foundry server` CLI generation. See [Connect to a remote Foundry Local service](/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-host/#connect-to-a-remote-foundry-local-service).
 - **Blazor WebAssembly debugging.** Standalone and hosted WebAssembly apps can expose dashboard commands for starting and stopping an Edge or Chrome debugging session during local runs. The related Dotnet project gateway APIs are also available to polyglot AppHosts and participate in publishing, but remain unstable and may change. See [Blazor gateway hosting](/integrations/dotnet/blazor-hosting/#add-a-blazor-gateway-for-a-c-project-resource).