docs: complete XML-doc coverage and strip internal tracking IDs from code comments

Resolve all CommentChecker findings across the gateway server, worker, tests,
and .NET client (314 -> 0 real issues): add missing <returns>/<summary>/<param>
on public and test members, convert Stream/interface overrides to <inheritdoc/>,
and remove internal task/issue tracking IDs (SEC-*, IPC-*, WRK-*, GWC-*, TST-*,
Client.Dotnet-*) from shipped code documentation while preserving the design
rationale prose. Shipped comments should not carry internal bookkeeping, and
complete XML docs keep the analyzer/TreatWarningsAsErrors gate and generated API
docs clean. The 6 remaining flags are heuristic false positives (MD5, UTC-4,
capacity-1, near-1601) left intact so real documentation is not corrupted.

Claude-Session: https://claude.ai/code/session_01DMXXvNuPekkkrTEyPNxEkW

src/ZB.MOM.WW.MxGateway.Tests/Gateway/Dashboard/DashboardLoginRateLimitTests.cs

@@ -7,7 +7,7 @@ using ZB.MOM.WW.MxGateway.Server.Dashboard;
 namespace ZB.MOM.WW.MxGateway.Tests.Gateway.Dashboard;
 
 /// <summary>
-/// SEC-11: the <c>POST /auth/login</c> fixed-window per-IP rate limiter. Exercised through the same
+/// Tests the <c>POST /auth/login</c> fixed-window per-IP rate limiter. Exercised through the same
 /// partition factory the production policy registers, so the test pins the real permit limit and
 /// per-IP partitioning without standing up an HTTP server.
 /// </summary>

src/ZB.MOM.WW.MxGateway.Tests/Gateway/Dashboard/DashboardSessionAdminServiceTests.cs

@@ -203,7 +203,7 @@ public sealed class DashboardSessionAdminServiceTests
     /// <summary>
     /// Verifies that a successful close writes a canonical <c>dashboard-close-session</c>
     /// <see cref="AuditEvent"/> — actor, session-id target, and Success outcome — to the
-    /// audit store, not only the operational log (SEC-12).
+    /// audit store, not only the operational log.
     /// </summary>
     /// <returns>A task that represents the asynchronous operation.</returns>
     [Fact]
@@ -229,7 +229,7 @@ public sealed class DashboardSessionAdminServiceTests
 
     /// <summary>
     /// Verifies that a successful kill writes a canonical <c>dashboard-kill-worker</c>
-    /// <see cref="AuditEvent"/> to the audit store (SEC-12).
+    /// <see cref="AuditEvent"/> to the audit store.
     /// </summary>
     /// <returns>A task that represents the asynchronous operation.</returns>
     [Fact]
@@ -253,7 +253,7 @@ public sealed class DashboardSessionAdminServiceTests
 
     /// <summary>
     /// Verifies that an unauthorized (viewer) close attempt still writes a <c>Denied</c>
-    /// audit row, so rejected destructive attempts are durably recorded (SEC-12).
+    /// audit row, so rejected destructive attempts are durably recorded.
     /// </summary>
     /// <returns>A task that represents the asynchronous operation.</returns>
     [Fact]
@@ -305,7 +305,10 @@ public sealed class DashboardSessionAdminServiceTests
         /// <summary>Gets the audit events written through this writer, in order.</summary>
         public IReadOnlyList<AuditEvent> Events => _events.ToArray();
 
-        /// <inheritdoc />
+        /// <summary>Records the given audit event for later inspection by the test.</summary>
+        /// <param name="evt">The audit event to record.</param>
+        /// <param name="ct">Token to cancel the asynchronous operation.</param>
+        /// <returns>A task that represents the asynchronous operation.</returns>
         public Task WriteAsync(AuditEvent evt, CancellationToken ct = default)
         {
             _events.Enqueue(evt);

src/ZB.MOM.WW.MxGateway.Tests/Gateway/Dashboard/HubTokenServiceTests.cs

@@ -145,7 +145,7 @@ public sealed class HubTokenServiceTests
     }
 
     /// <summary>
-    /// The default token lifetime is the short (5-minute) window mandated by SEC-05, not the
+    /// The default token lifetime is the short (5-minute) window, not the
     /// former 30-minute window. Pins the value so a regression that widens the exposure window
     /// of an irrevocable, query-string-carried token is caught in CI.
     /// </summary>