docs(src): fix CommentChecker findings across src/ — 1,032 → 5 (all false positives)

Comment/XML-doc changes only, no code logic:
- strip project-tracking references (WP*, P*-*, row-NN, #NN, Task N) from
  comments, keeping the explanatory rationale
- add missing summaries, <param>, <returns>, <typeparam> and <inheritdoc/>
- replace misused <inheritdoc/> with real docs; where <inheritdoc/> was
  combined with useful remarks, move the rationale into // comments
- drop stale replicationActor <param> on DeploymentManagerActor ctor

Remaining 5 are false positives (CWE-1236 x2, failures-1, year-0001, M365).
Build 0 errors / 0 warnings.

src/ZB.MOM.WW.ScadaBridge.Commons/Messages/DebugView/DebugSnapshotRequest.cs

@@ -7,7 +7,7 @@ namespace ZB.MOM.WW.ScadaBridge.Commons.Messages.DebugView;
 /// <param name="CorrelationId">Correlation id echoed on the reply.</param>
 /// <param name="AlarmsOnly">
 /// When <c>true</c> the site builds ONLY the alarm half of the snapshot and returns an
-/// empty <see cref="DebugViewSnapshot.AttributeValues"/> list (wire efficiency, WP2.3).
+/// empty <see cref="DebugViewSnapshot.AttributeValues"/> list (wire efficiency).
 /// Set by the central per-site live alarm cache, whose seed/reconcile fan-out discards
 /// every attribute row anyway. Defaults to <c>false</c> so the Debug View and every other
 /// caller keep the full snapshot; additive on the wire

src/ZB.MOM.WW.ScadaBridge.Commons/Messages/Health/SecretMirrorNodeStatus.cs

@@ -2,7 +2,7 @@ namespace ZB.MOM.WW.ScadaBridge.Commons.Messages.Health;
 
 /// <summary>
 /// One site node's latest deployed-secrets mirror outcome, as carried on
-/// <see cref="SiteHealthReport.SecretMirrorStatuses"/> (review finding M1).
+/// <see cref="SiteHealthReport.SecretMirrorStatuses"/>.
 /// </summary>
 /// <remarks>
 /// Every site node runs its own <c>DeployedSecretsMirror</c> and records its current

src/ZB.MOM.WW.ScadaBridge.Commons/Messages/Health/SiteHealthReport.cs

@@ -75,7 +75,7 @@ public record SiteHealthReport(
     public double? ScriptOldestBusyAgeSeconds { get; init; }
 
     /// <summary>
-    /// WP3.1: script-execution worker threads the stuck-script watchdog has DETACHED and
+    /// Script-execution worker threads the stuck-script watchdog has DETACHED and
     /// replaced — a script wedged past its deadline plus grace in uninterruptible blocking
     /// I/O, so the pool started a fresh thread and the wedged one will exit only when its
     /// body finally returns. Point-in-time, refreshed by <c>ScriptSchedulerStatsReporter</c>.
@@ -85,7 +85,7 @@ public record SiteHealthReport(
     public int DetachedScriptThreads { get; init; }
 
     /// <summary>
-    /// WP3.1: per-interval count of script and alarm on-trigger runs SHED because
+    /// Per-interval count of script and alarm on-trigger runs SHED because
     /// <c>MaxConcurrentRunsPerScript</c> runs were already in flight for that script. Raw
     /// per-interval count (drained on collect) like <see cref="ScriptErrorCount"/>. A
     /// sustained non-zero value means a trigger is firing faster than its script completes;
@@ -136,8 +136,7 @@ public record SiteHealthReport(
     public long? LocalDbOplogBacklog { get; init; }
 
     /// <summary>
-    /// WP2.6d (arch-review misc — site stream alarm-vs-attribute shared buffer):
-    /// cumulative count of alarm state changes dropped from
+    /// Cumulative count of alarm state changes dropped from
     /// <c>SiteStreamManager</c>'s dedicated alarm publish queue because it was at
     /// capacity — i.e. the site-wide alarm hand-off itself fell behind, not a
     /// per-subscriber buffer. Point-in-time (not reset on collect), refreshed by
@@ -154,9 +153,9 @@ public record SiteHealthReport(
     /// </summary>
     /// <remarks>
     /// <para>
-    /// Tri-state, and the distinction is the whole point (deferred-work register row 73).
+    /// Tri-state, and the distinction is the whole point.
     /// <b>Null = not reported</b>: a central self-report, where the notion does not apply,
-    /// or a site node running a pre-row-73 build. <b><see langword="true"/></b> = the
+    /// or a site node running an older build. <b><see langword="true"/></b> = the
     /// reconciler is running. <b><see langword="false"/></b> = the node booted WITHOUT it,
     /// because no <c>IDeploymentConfigFetcher</c> was resolvable.
     /// </para>
@@ -175,12 +174,12 @@ public record SiteHealthReport(
     public bool? StartupReconcilerActive { get; init; }
 
     /// <summary>
-    /// Every site node's latest deployed-secrets mirror outcome (review finding M1) — one
+    /// Every site node's latest deployed-secrets mirror outcome — one
     /// entry per node that has recorded a row in the replicated <c>secret_mirror_status</c>
     /// table, including the STANDBY node, whose own health report is never sent.
     /// </summary>
     /// <remarks>
-    /// <b>Null = no data</b>: a central self-report, a pre-M1 site build, a site whose
+    /// <b>Null = no data</b>: a central self-report, an older site build, a site whose
     /// reporter has not run yet, or a failed read. An EMPTY list means the feature is wired
     /// but no node has recorded a status yet. A node entry with an empty
     /// <see cref="SecretMirrorNodeStatus.Failures"/> list is a healthy mirror. Names and

src/ZB.MOM.WW.ScadaBridge.Commons/Messages/Instance/SetStaticAttributeCommand.cs

@@ -10,7 +10,7 @@ namespace ZB.MOM.WW.ScadaBridge.Commons.Messages.Instance;
 /// <param name="Value">Canonical string form of the new value.</param>
 /// <param name="Timestamp">UTC timestamp of the command.</param>
 /// <param name="SourceExecutionId">
-/// Audit Log #23 (ParentExecutionId tag-cascade): the <c>ExecutionId</c> of the
+/// ParentExecutionId tag-cascade: the <c>ExecutionId</c> of the
 /// execution issuing this write — a site script run
 /// (<c>ScriptRuntimeContext.SetAttribute</c>) or the inbound API request behind a
 /// <c>Route.To(...).SetAttributes(...)</c>. Additive and nullable; <c>null</c>