docs(xmldoc): fill missing XML docs + strip tracking-ID comments across src

Adds <summary>/<param>/<returns>/<inheritdoc> where missing and removes
project bookkeeping IDs (task/tracking refs) from shipped code comments,
so the docs read cleanly and CommentChecker is quiet except for known
false positives (PLC/protocol terms, event/IEqualityComparer inheritdoc).
Doc/comment-only; no logic changed; solution builds clean.

src/Server/ZB.MOM.WW.OtOpcUa.ControlPlane/Coordinators/ConfigPublishCoordinator.cs

@@ -16,7 +16,7 @@ namespace ZB.MOM.WW.OtOpcUa.ControlPlane.Coordinators;
 /// <see cref="DispatchDeployment"/> over DistributedPubSub on the <c>deployments</c> topic, gathers
 /// per-node <see cref="ApplyAck"/> replies, and seals the deployment when every expected node
 /// has acked Applied. Per-node ACKs are persisted in <c>NodeDeploymentState</c> so a failover of
-/// this singleton (Task 31) can recover in-flight state from the DB.
+/// this singleton can recover in-flight state from the DB.
 ///
 /// Discovery of the "expected ACK set" comes from <c>Akka.Cluster.State.Members</c> filtered by
 /// the <c>driver</c> role — the DB does not own per-node role assignment.
@@ -46,6 +46,7 @@ public sealed class ConfigPublishCoordinator : ReceiveActor, IWithTimers
     /// <summary>Creates actor props for the ConfigPublishCoordinator with the specified configuration.</summary>
     /// <param name="dbFactory">The database context factory for accessing configuration data.</param>
     /// <param name="applyDeadline">The timeout for waiting for apply acknowledgments from cluster nodes.</param>
+    /// <returns>The Akka.NET <see cref="Akka.Actor.Props"/> used to spawn this actor.</returns>
     public static Props Props(
         IDbContextFactory<OtOpcUaConfigDbContext> dbFactory,
         TimeSpan? applyDeadline = null) =>
@@ -68,14 +69,12 @@ public sealed class ConfigPublishCoordinator : ReceiveActor, IWithTimers
         Receive<SubscribeAck>(_ => { /* DPS subscribe confirmation */ });
     }
 
-    /// <summary>
-    /// On startup recover any deployment that was mid-flight when a prior singleton instance
-    /// died. We re-derive <c>_expectedAcks</c> from <c>NodeDeploymentState</c>, replay the ACKs
-    /// that already landed in the DB, and resume the deadline timer.
-    /// </summary>
     /// <inheritdoc />
     protected override void PreStart()
     {
+        // On startup recover any deployment that was mid-flight when a prior singleton instance
+        // died. We re-derive _expectedAcks from NodeDeploymentState, replay the ACKs
+        // that already landed in the DB, and resume the deadline timer.
         // Subscribe to per-node ApplyAck broadcasts so DriverHostActors on remote members can
         // route their ACKs to whichever node currently hosts this singleton.
         DistributedPubSub.Get(Context.System).Mediator.Tell(new Subscribe(DeploymentAcksTopic, Self));