fix(health): rows 80+73 — unconfigured replication reports null, reconciler presence surfaced

ROW 80 (observability correctness). An unreplicated site published
LocalDbReplicationConnected=false / LocalDbOplogBacklog=0, contradicting the
nullable semantics every doc and the proto already state ("null means no
reading, NOT disconnected with an empty backlog").

Root cause: the replication engine is registered unconditionally and idles
without a peer, so ISyncStatus answers false/0 on a node that was never meant to
replicate, and LocalDbReplicationStatusReporter passed that straight through.
Two consequences: an operator read connected:false on a healthy site as a fault,
and central's null branches — row 33's conditional KPI emission and
sustained-badge anchor exclusion — never received the null they exist for, so
rig site-b/site-c emitted a permanently misleading
localDbReplicationConnected=0 series.

Fix mirrors the SiteEventLogReplicationCheck precedent: the Host evaluates
SiteLocalDbSetup.ReplicationIsConfigured ONCE and passes it to
AddLocalDbReplicationHealthBridge as a third provider; unconfigured
short-circuits the probe to (null, null). HealthMonitoring never reads LocalDb
config itself, and the same captured value now also feeds
SiteEventLogReplicationCheck so the two surfaces cannot disagree.
ISiteHealthCollector.SetLocalDbReplicationStatus widens to bool? — the
non-nullable bool was the type-level root cause (null was inexpressible).
false now means exactly one thing: configured, peer session down = a real fault.

Wire/central/UI needed no change: the proto already carries BoolValue/Int64Value
wrappers and the aggregator + KPI source already branch on null. This makes code
match doc, so no doc claim was weakened.

Watch the trap that caused this: configured-ness is PeerAddress OR ApiKey (only
the dialling half sets a peer address). The pre-existing SiteLocalDbWiringTests
fixture sets ApiKey and IS a replicating node, so its false/0 assertion is
correct and is kept, with a comment saying so; the new
UnreplicatedSiteLocalDbHealthTests fixture is the genuinely-unreplicated one.

ROW 73 (silent loss of self-heal). AkkaHostedService skips
SiteReconciliationActor when no IDeploymentConfigFetcher is resolvable, and that
skip was a lone boot Warning — a node with no self-heal path at all went on
reporting itself perfectly healthy forever.

Adds tri-state SiteHealthReport.StartupReconcilerActive (null = not reported,
i.e. the central self-report or a pre-row-73 site build; true = running;
false = booted without it), latched once at boot by the Host in both branches.
Additive proto field 29 (BoolValue, vendored C# regenerated via
docker/regen-proto.sh centralcontrol; csproj restored, verified empty diff).
The skip branch also raises its log to Error — no configuration makes the
fetcher legitimately absent on a site node — and writes a best-effort
deployment/Error site event so the evidence outlives the boot log.

Central treatment: a "No self-heal" WARNING badge on the site tile, not a
failure. Config still reaches the node via LocalDb replication while it is up;
what it lost is recovery from a deploy that landed while it was down — degraded,
not offline. Only the explicit false is badged (badging null would light up the
whole fleet the moment central is upgraded ahead of the sites), and offline
sites are skipped, matching the replication-backlog badge.

Fail-before evidence: with the row-80 gate behaviourally reverted,
UnreplicatedSite_HealthReport_ReportsNullForBothLocalDbFields fails
"Expected: null / Actual: False" and 3 of the 8 new reporter unit tests fail.

Tests: HealthMonitoring 128, Host 518, CentralUI 1051, Communication 717,
Commons 715, SiteEventLogging 81 — all green.

src/ZB.MOM.WW.ScadaBridge.HealthMonitoring/ISiteHealthCollector.cs

@@ -162,14 +162,38 @@ public interface ISiteHealthCollector
     /// service. Point-in-time: values are NOT reset on <see cref="CollectReport"/>.
     /// </summary>
     /// <param name="connected">
-    /// Whether a sync session is currently running. <see langword="false"/> is the
-    /// normal state on a node with no peer configured — replication ships default-OFF.
+    /// Whether a sync session is currently running, or <see langword="null"/> when there
+    /// is no reading to give — which is the state of a node with replication UNCONFIGURED
+    /// (register row 80). <see langword="false"/> means "replication is configured on this
+    /// node and the peer session is currently down", i.e. a genuine fault worth a badge;
+    /// reporting that on a deliberately-unreplicated site reads as a fault that isn't one.
     /// </param>
     /// <param name="oplogBacklog">
-    /// Unacked oplog entries, or <see langword="null"/> when unknown. Pass null through
-    /// unchanged: a failed poll rendered as 0 would report a broken pair as healthy.
+    /// Unacked oplog entries, or <see langword="null"/> when unknown (failed poll) or not
+    /// applicable (replication unconfigured). Pass null through unchanged: a failed poll
+    /// rendered as 0 would report a broken pair as healthy.
     /// </param>
-    void SetLocalDbReplicationStatus(bool connected, long? oplogBacklog)
+    void SetLocalDbReplicationStatus(bool? connected, long? oplogBacklog)
+    {
+        // Default no-op so test fakes do not need to be updated.
+    }
+
+    /// <summary>
+    /// Record whether this node spawned its <c>SiteReconciliationActor</c> at boot, for the
+    /// <c>StartupReconcilerActive</c> field of every subsequent <see cref="CollectReport"/>
+    /// (deferred-work register row 73).
+    /// </summary>
+    /// <remarks>
+    /// Called ONCE at boot by the Host, which owns the spawn decision — this is a latched
+    /// boot fact, not a polled gauge, so there is no reporter hosted service behind it.
+    /// A collector that is never told (central's self-report, or any test host) leaves the
+    /// field null, which reads as "not reported" rather than "reconciler absent".
+    /// </remarks>
+    /// <param name="active">
+    /// <see langword="true"/> when the reconciler was created; <see langword="false"/> when
+    /// it was skipped because no <c>IDeploymentConfigFetcher</c> was available.
+    /// </param>
+    void SetStartupReconcilerActive(bool active)
     {
         // Default no-op so test fakes do not need to be updated.
     }