fix(review): full code-review remediation — 5 High + Medium/Low across 16 modules

Remediation from the full per-module code review at 4307c381 (findings recorded
separately in code-reviews/).

Highs fixed:
- DeploymentManager-025/SiteRuntime-031: stop broadcasting notification lists + SMTP
  configs (incl. credentials) to sites; site purges already-persisted rows on apply
  (enforces the central-only delivery design; clears plaintext SMTP creds at rest).
- DataConnectionLayer-023: guard the native-alarm subscribe path against the
  mid-flight-unsubscribe adapter-feed leak (mirrors the DCL-021 tag-path fix).
- SiteEventLogging-024: normalize From/To query bounds to UTC (the -016 fix the
  audit trail claimed but never committed).
- KpiHistory-001: add an in-flight guard to the recorder sample tick.
- ScriptAnalysis-001: harden the trust analyzer's TPA-absent fallback (resolve
  forbidden anchors in the minimal reference set; warn on degraded mode) — anchors
  added to validation references only, never the compile gate.
(InboundAPI-026 left to the feat/ipsen-movein effort per owner decision.)

Medium/Low: DM-026 deterministic deploy-status tiebreaker; SR-027/028/029/030
native-alarm leak/phantom-active/delete-during-redeploy fixes; AL-013/014/016;
TE-024 (folder-mutation audit rows now persisted)/025; SF-025 gauge-provider
clear-on-stop; ESG-025/026; SEC-023/024/025; SCA-007/008/009; plus doc/test
accuracy COM-023/024, HOST-025/026, HM-024/025, NS-027/028.

Full-solution build 0 warnings; ~3560 tests across 18 touched suites green.

tests/ZB.MOM.WW.ScadaBridge.ConfigurationDatabase.Tests/RepositoryCoverageTests.cs

@@ -940,6 +940,31 @@ public class DeploymentManagerRepositoryTests : IDisposable
         Assert.Equal("d-002", current!.DeploymentId);
     }
 
+    [Fact]
+    public async Task GetCurrentDeploymentStatus_SameTickRecords_DeterministicTiebreakerPicksHighestId()
+    {
+        // DeploymentManager-026: deployments are insert-only, so two records for the
+        // same instance can tie on DeployedAt when created within the same clock tick
+        // (rapid redeploy, or redeploy right after a timed-out attempt). Without a
+        // secondary sort key the "current" read is non-deterministic. The repository
+        // now orders by DeployedAt DESC, THEN Id DESC, so the most recently inserted
+        // (highest Id) row wins the tie deterministically.
+        var instance = await SeedInstanceAsync();
+        var sameInstant = DateTimeOffset.UtcNow;
+
+        await _repository.AddDeploymentRecordAsync(
+            new DeploymentRecord("d-old", "admin") { InstanceId = instance.Id, DeployedAt = sameInstant });
+        await _repository.SaveChangesAsync();
+        await _repository.AddDeploymentRecordAsync(
+            new DeploymentRecord("d-new", "admin") { InstanceId = instance.Id, DeployedAt = sameInstant });
+        await _repository.SaveChangesAsync();
+
+        var current = await _repository.GetCurrentDeploymentStatusAsync(instance.Id);
+        Assert.NotNull(current);
+        // d-new was inserted second → it has the higher Id and must win the tie.
+        Assert.Equal("d-new", current!.DeploymentId);
+    }
+
     [Fact]
     public async Task DeleteDeploymentRecord_ViaStubAttachPath_RemovesEntity()
     {