feat(localdb): wire 2-node replication for the site database, default OFF

Task 7 of the LocalDb Phase 1 adoption plan.

AddZbLocalDbReplication registers the engine; MapZbLocalDbSync exposes the
passive endpoint the peer node dials. Both are unconditional but INERT by
default: with no LocalDb:Replication:PeerAddress the initiating
SyncBackgroundService starts and immediately idles, and nothing dials the
endpoint. A site pair replicates only once an operator sets a peer on BOTH
nodes. The endpoint shares the Kestrel h2c listener the site gRPC server already
uses, so there are no listener or port changes.

Deviation from the plan: it put AddZbLocalDbReplication in Program.cs. Doing so
would have left it untested - the composition-root tests build
SiteServiceRegistration's graph, not Program.cs - so a registration that silently
went missing would still show green. It now sits next to AddZbLocalDb in
SiteServiceRegistration, where the DI-graph tests actually cover it.
MapZbLocalDbSync stays in Program.cs because it needs the WebApplication.

Two pins added to SiteLocalDbWiringTests, which configures no peer:
  - the engine resolves and is idle (not connected, no peer, never synced) -
    default-off means inert, not unregistered;
  - OplogBacklog is 0, not null. It is deliberately nullable so a failed poll
    reads as "unknown" instead of a healthy zero; a real 0 proves the provider is
    wired to the oplog, which Task 9's health signal depends on.

Inbound auth on the sync endpoint is Task 8. Until that lands the endpoint is
unauthenticated - which is precisely why replication ships default-OFF and no
config in this repo sets a peer.

Verified: build 0 warnings; Host 296/296, SiteEventLogging 70/70,
SiteRuntime 530/530, Commons 684/684, Communication 312/312.

Claude-Session: https://claude.ai/code/session_01BL2Vu1ESDQ9SCN4gVKkdts

tests/ZB.MOM.WW.ScadaBridge.Host.Tests/SiteLocalDbWiringTests.cs

@@ -2,6 +2,7 @@ using Microsoft.AspNetCore.Builder;
 using Microsoft.Extensions.Configuration;
 using Microsoft.Extensions.DependencyInjection;
 using ZB.MOM.WW.LocalDb;
+using ZB.MOM.WW.LocalDb.Replication;
 using ZB.MOM.WW.ScadaBridge.Host;
 using ZB.MOM.WW.ScadaBridge.Host.Actors;
 
@@ -120,6 +121,35 @@ public class SiteLocalDbWiringTests : IDisposable
         Assert.Same(first, second);
     }
 
+    [Fact]
+    public void Site_Replication_IsRegistered_AndInertWithNoPeer()
+    {
+        // Task 7's default-OFF pin. This fixture configures NO
+        // LocalDb:Replication:PeerAddress, which is the shipping default, so the
+        // engine must resolve cleanly and sit idle rather than throw, retry, or
+        // report a connection. "Default-off" here means inert, NOT unregistered —
+        // the services are always in the graph.
+        var status = _host.Services.GetService<ISyncStatus>();
+
+        Assert.NotNull(status);
+        Assert.False(status!.Connected);
+        Assert.Null(status.PeerNodeId);
+        Assert.Null(status.LastSyncUtc);
+    }
+
+    [Fact]
+    public void Site_Replication_OplogBacklog_IsZero_NotNull_OnAHealthyIdleNode()
+    {
+        // OplogBacklog is deliberately nullable: null means "unknown" (no provider
+        // wired, or the poll failed) and must never be reported as a healthy 0. On a
+        // node whose local database is present and readable, a real 0 proves the
+        // backlog provider is actually wired to the oplog — a null here would mean
+        // Task 9's health signal is about to publish "unknown" forever.
+        var status = _host.Services.GetRequiredService<ISyncStatus>();
+
+        Assert.Equal(0L, status.OplogBacklog);
+    }
+
     [Fact]
     public void Site_LocalDb_CreatesTheConfiguredFile()
     {