fix(health): acked SendAsync transport — report-loss counter restore is live, not dead code

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

@@ -4,13 +4,20 @@ namespace ZB.MOM.WW.ScadaBridge.HealthMonitoring;
 
 /// <summary>
 /// Abstraction for sending health reports to central.
-/// In production, implemented via Akka remoting (Tell, fire-and-forget).
+/// In production, implemented over Akka ClusterClient with an acked round-trip
+/// (review 01 [Medium]): the transport Asks and awaits a
+/// <see cref="SiteHealthReportAck"/>, so a lost/rejected report surfaces as a
+/// fault the sender can observe (and its per-interval counter-restore fires).
 /// </summary>
 public interface IHealthReportTransport
 {
     /// <summary>
-    /// Sends a health report to central (fire-and-forget).
+    /// Sends a health report to central and completes only once central has
+    /// acknowledged processing. MUST THROW on non-delivery (Ask timeout, actor
+    /// system not started, or a not-accepted ack) — the sender's counter-restore
+    /// path in <c>HealthReportSender</c> depends on that exception.
     /// </summary>
     /// <param name="report">The site health report to send.</param>
-    void Send(SiteHealthReport report);
+    /// <param name="cancellationToken">Cancels the in-flight send.</param>
+    Task SendAsync(SiteHealthReport report, CancellationToken cancellationToken);
 }