docs(tests): fix CommentChecker findings across tests/ — 13,392 → 0 (repo-wide scan clean)

Comment/XML-doc changes only:
- add summaries to ~10k test methods, fixtures, fakes and helpers
  (+ <param> on theories, <returns> on async Task methods,
  <inheritdoc/> on interface implementations the checker can resolve)
- strip ~2.6k project-tracking references (WP*, P*-*, row-NN, Task N,
  #NN, Component-0NN) from comments, keeping the explanatory text;
  reword false positives in comments only
- real docs on fakes implementing BCL/library interfaces
  (IDisposable, ILogger, IOptionsMonitor, IAsyncLifetime)
- reword the last 5 src/ false positives (CWE-1236, failures-1,
  year-0001, M365)

Only non-comment edits: four one-line nested classes split across lines
so members can carry docs. Build 0 errors / 0 warnings.

tests/ZB.MOM.WW.ScadaBridge.DataConnectionLayer.Tests/Actors/DataConnectionDisconnectRaceTests.cs

@@ -10,7 +10,7 @@ using ZB.MOM.WW.ScadaBridge.HealthMonitoring;
 namespace ZB.MOM.WW.ScadaBridge.DataConnectionLayer.Tests.Actors;
 
 /// <summary>
-/// Arch-review 2026-08-19 <b>P2-6</b> — the <c>AdapterDisconnected</c> gap in the
+/// The <c>AdapterDisconnected</c> gap in the
 /// Connecting/Reconnecting states, and the generation fence that keeps a swapped-out adapter's
 /// disconnect from disturbing its replacement.
 ///
@@ -28,7 +28,7 @@ namespace ZB.MOM.WW.ScadaBridge.DataConnectionLayer.Tests.Actors;
 ///
 /// <para>
 /// The fix must not weaken the Medium-wave generation fencing: a disconnect raised by an adapter
-/// that has since been swapped out (failover, or the row-97 in-place reconfigure) must still be
+/// that has since been swapped out (failover, or the in-place reconfigure) must still be
 /// dropped, or the endpoint the operator has just corrected AWAY from could knock the healthy
 /// replacement back into a reconnect cycle.
 /// </para>
@@ -113,7 +113,7 @@ public class DataConnectionDisconnectRaceTests : TestKit
     {
         const string name = "disconnect-before-connect-result";
         var firstConnect = new TaskCompletionSource();
-        // Attempt #2 onward never completes, so "the actor did not go Connected on the dead
+        // Attempt 2 onward never completes, so "the actor did not go Connected on the dead
         // session" is a stable assertion rather than a race against the next retry tick.
         var laterConnects = new TaskCompletionSource();
         var connects = 0;
@@ -158,7 +158,7 @@ public class DataConnectionDisconnectRaceTests : TestKit
         const string name = "disconnect-before-reconnect-result";
         var firstConnect = new TaskCompletionSource();
         var secondConnect = new TaskCompletionSource();
-        // Attempt #3 onward never completes, so the actor parks in Reconnecting and the
+        // Attempt 3 onward never completes, so the actor parks in Reconnecting and the
         // "did not go Connected on the dead session" assertion is stable rather than a race
         // against the next retry tick.
         var laterConnects = new TaskCompletionSource();
@@ -181,7 +181,7 @@ public class DataConnectionDisconnectRaceTests : TestKit
         AwaitCondition(() => HealthTransitions(name, ConnectionHealth.Connected) >= 1,
             TimeSpan.FromSeconds(5), TimeSpan.FromMilliseconds(10));
 
-        // Drop while Connected → Reconnecting, and the retry timer launches attempt #2.
+        // Drop while Connected → Reconnecting, and the retry timer launches attempt 2.
         adapter.Disconnected += Raise.Event<Action>();
         AwaitCondition(() => Volatile.Read(ref connects) >= 2,
             TimeSpan.FromSeconds(5), TimeSpan.FromMilliseconds(10));