docs: strip task-tracking IDs from code comments and fill missing XML docs

Tracking IDs are review bookkeeping that rots in shipped source; the rationale they tagged is kept. Comment-only change (CommentChecker 458 -> 16 false positives).

src/ZB.MOM.WW.MxGateway.Tests/Alarms/AlarmWatchListResolverTests.cs

@@ -19,7 +19,7 @@ public sealed class AlarmWatchListResolverTests
     /// <summary>
     ///     Resolves and projects to the target list. These cases assert composition rules, which
     ///     live in <see cref="AlarmWatchListResolution.Targets"/>; the discovery-provenance fields
-    ///     the resolution also carries (GWC-37) are asserted by their own cases below.
+    ///     the resolution also carries are asserted by their own cases below.
     /// </summary>
     /// <param name="resolver">The resolver under test.</param>
     /// <param name="options">Alarm options to resolve against.</param>
@@ -259,7 +259,7 @@ public sealed class AlarmWatchListResolverTests
     }
 
     /// <summary>
-    ///     GWC-37: swallowing the discovery failure is right for the resolver but leaves the
+    ///     Swallowing the discovery failure is right for the resolver but leaves the
     ///     caller unable to tell "discovery produced nothing" from "nothing was configured", which
     ///     is why the empty watch-list could sit unnoticed for a monitor's whole life. The
     ///     resolution therefore reports whether discovery was attempted, whether it failed, and
@@ -284,7 +284,7 @@ public sealed class AlarmWatchListResolverTests
     /// <summary>
     ///     The complement of the case above: discovery disabled is not discovery failed. An empty
     ///     watch-list here means the deployment did not ask for subtag coverage, which the monitor
-    ///     must not report as a degraded standby (GWC-37).
+    ///     must not report as a degraded standby.
     /// </summary>
     /// <returns>A task that represents the asynchronous operation.</returns>
     [Fact]