Adding some notes about ancillary marten store limitations and adding…

… a note about AddWolverineHttp() to the migration guide

docs/guide/durability/marten/ancillary-stores.md

@@ -115,8 +115,15 @@ In the case of the ancillary Marten stores, the `IDocumentSession` objects are "
 any identity map mechanics for better performance. 
 :::
 
-What's not (yet) supported:
+## What's not (yet) supported
 
+::: warning
+There is currently a limitation where Wolverine can only use the inbox/outbox storage from the main Marten
+document store even if your handler declares that it is from a separate store. This is perfectly fine if your
+ancillary stores target the same PostgreSQL database. This limitation will be removed in 3.0.
+:::
+
+* It is not possible to use more than one ancillary store in the same handler with the middleware
 * The "Event Forwarding" from Marten to Wolverine
 * Fine grained configuration of the `IDocumentSession` objects created for the ancillary stores, so no ability to tag
   custom `IDocumentSessionListener` objects or control the session type. Listeners could be added through Wolverine middlware

docs/guide/migration.md

@@ -25,4 +25,10 @@ a significant improvement in Wolverine's ability to detect node changes and roll
 
 The PostgreSQL transport option requires you to explicitly set the `transportSchema`, or Wolverine will fall through to
 using `wolverine_queues` as the schema for the database backed queues. Wolverine will no longer use the envelope storage
-schema for the queues.
+schema for the queues.
+
+For [Wolverine.Http usage](/guide/http/), the Wolverine 3.0 usage of the less capable `ServiceProvider` instead of the previously
+mandated [Lamar](https://jasperfx.github.io/lamar) library necessitates the usage of this API to register necessary
+services for Wolverine.HTTP in addition to adding the Wolverine endpoints:
+
+snippet: sample_adding_http_services

src/Http/WolverineWebApi/Program.cs

@@ -23,15 +23,22 @@
 using WolverineWebApi.WebSockets;
 using Order = WolverineWebApi.Order;
 
+#region sample_adding_http_services
+
 var builder = WebApplication.CreateBuilder(args);
 
 // Add services to the container.
 
-builder.Services.AddLogging();
+// Necessary services for Wolverine HTTP
+// And don't worry, if you forget this, Wolverine
+// will assert this is missing on startup:(
+builder.Services.AddWolverineHttp();
+
+#endregion
+
 
-// Learn more about configuring Swagger/OpenAPI at https://aka.ms/aspnetcore/swashbuckle
+builder.Services.AddLogging();
 builder.Services.AddEndpointsApiExplorer();
-builder.Services.AddWolverineHttp();
 
 #region sample_register_custom_swashbuckle_filter