docs: fill missing XML docs and strip tracking IDs from src comments

Clears CommentChecker findings in src/ (3,280 -> 209, the remainder being false
positives like PLC-5/IEEE-754/M0.0) by adding missing summaries/params/returns,
normalising inheritdoc usage, and removing Gitea/review tracking IDs while keeping
the rationale they annotated. Comment-only: comment-stripped sources are identical
to the parent commit.

src/Server/ZB.MOM.WW.OtOpcUa.ControlPlane/ServiceCollectionExtensions.cs

@@ -21,7 +21,7 @@ namespace ZB.MOM.WW.OtOpcUa.ControlPlane;
 
 public static class ServiceCollectionExtensions
 {
-    // R3-04 (theme 4 guard): alias RoleParser.Admin rather than duplicating the literal — the same
+    // Alias RoleParser.Admin rather than duplicating the literal — the same
     // pattern Runtime/ServiceCollectionExtensions.DriverRole already follows for RoleParser.Driver.
     public const string AdminRole = RoleParser.Admin;
 
@@ -120,7 +120,7 @@ public static class ServiceCollectionExtensions
                 var dbFactory = resolver.GetService<IDbContextFactory<OtOpcUaConfigDbContext>>();
                 var coordinator = registry.Get<ConfigPublishCoordinatorKey>();
                 var probes = resolver.GetService<IEnumerable<IDriverProbe>>() ?? Enumerable.Empty<IDriverProbe>();
-                // R2-11 (05/CONV-2): deploy-gate TagConfig strictness mode from appsettings
+                // Deploy-gate TagConfig strictness mode from appsettings
                 // (Deployment:TagConfigValidationMode = Warn default | Error opt-in).
                 var mode = Enum.TryParse<TagConfigValidationMode>(
                     resolver.GetService<IConfiguration>()?["Deployment:TagConfigValidationMode"],
@@ -139,11 +139,11 @@ public static class ServiceCollectionExtensions
             },
             singletonOptions);
 
-        // Gitea #542 (2026-08-06): the fleet-status singleton is NO LONGER registered here — the
+        // The fleet-status singleton is NO LONGER registered here — the
         // whole FleetStatusBroadcaster → DPS → SignalR bridge → FleetStatusHub chain was DELETED.
         // It had zero clients end-to-end (no browser JS, no HubConnection — /fleet reads
         // NodeDeploymentState from the ConfigDb on a poll), its DriverHostStatusHeartbeat input had
-        // no production sender, and after mesh Phase 6 its "fleet" was only central's own pair.
+        // no production sender, and after the mesh split its "fleet" was only central's own pair.
 
         // Per-cluster mesh Phase 6: the redundancy-state singleton is NO LONGER registered here.
         // It was an admin-scoped, fleet-wide singleton — one Primary elected across the whole mesh.
@@ -194,7 +194,7 @@ public static class ServiceCollectionExtensions
     /// redundancy.
     /// </summary>
     /// <param name="builder">The Akka configuration builder.</param>
-    /// <param name="roleInfo">The local node's cluster-role view (Task 1's <c>ClusterRoleInfo</c>).</param>
+    /// <param name="clusterOptions">The Akka cluster options, including the node's cluster role.</param>
     /// <returns>The builder for fluent chaining.</returns>
     /// <remarks>
     /// After the mesh split, central's mesh sees only its own pair — a driver-only site pair therefore
@@ -225,7 +225,7 @@ public static class ServiceCollectionExtensions
     /// <remarks>
     /// Cluster-scope is the robust choice — it survives an accidental two-mesh merge by keeping one
     /// singleton per cluster. The <c>driver</c>-role fallback deliberately does NOT throw when a node
-    /// has no cluster role, because (a) that is the pre-Phase-6 fleet-wide behavior on a legacy single
+    /// has no cluster role, because (a) that is the earlier fleet-wide behavior on a legacy single
     /// mesh, keeping legacy/harness nodes and any not-yet-migrated deployment booting unchanged, and
     /// (b) on a genuinely split 2-node mesh the <c>driver</c> role is already pair-local — the mesh IS
     /// the pair. So the fallback is correct in both worlds and costs no availability.