Event Tables Being Dropped When Adding New Registry with a new db schema

[TharinduNalan]

I'm encountering an issue where adding a new registry to an existing Marten DocumentStore configuration causes event tables to be dropped and recreated, resulting in data loss.

Steps to Reproduce

1. Initial Setup - Run the following configuration from the FreightShipping example:

var store = DocumentStore.For(opts =>
{
   opts.Connection(connectionString!);
   opts.AutoCreateSchemaObjects = AutoCreate.CreateOnly;
   opts.Projections.Add<ShipmentViewProjection>(ProjectionLifecycle.Inline);
   opts.Events.DatabaseSchemaName = "events";
   opts.DatabaseSchemaName = "shipments";
});

await store.Storage.ApplyAllConfiguredChangesToDatabaseAsync(AutoCreate.CreateOnly);

After this initial run, the events.mt_events table contains 5 event records.

2. Add New Schema Registry - add a new registry which configured with a new schema:

var store = DocumentStore.For(opts =>
{
    opts.Connection(connectionString!);
    opts.AutoCreateSchemaObjects = AutoCreate.CreateOnly;
    opts.Projections.Add<ShipmentViewProjection>(ProjectionLifecycle.Inline);
    opts.Events.DatabaseSchemaName = "events";
    opts.DatabaseSchemaName = "shipments";

    // Adding this new registry, which is configured for a new schema, causes the issue. 
    opts.Schema.Include<ClientRegistry>();
});

await store.Storage.ApplyAllConfiguredChangesToDatabaseAsync(AutoCreate.CreateOnly);

ClientRegistry is defined as:

public class ClientRegistry : MartenRegistry
{
    public ClientRegistry()
    {
        For<CustomerEntity>()
            .DatabaseSchemaName("clients") // New schema
            .DocumentAlias("customers");
    }
}

Expected Behavior

• The existing event data in events.mt_events should be preserved
• The data in the shipments schema should be preserved
• Only the new clients schema and its tables should be created

Actual Behavior

• The events.mt_events table is dropped and recreated
• The shipments schema tables are also affected

I'm new to MartenDB and not sure if there's any reason for this behavior, or if my setup is not correct. But as I understand it shouldn't delete any existing data. The data deletion happens on ApplyAllConfiguredChangesToDatabaseAsync().
Any guidance on the proper approach to handling schema evolution while preserving existing data would be greatly appreciated.

Thanks.