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.LoadHarness/Scenarios/ObservabilityProbes.cs

@@ -7,7 +7,7 @@ using ZB.MOM.WW.ScadaBridge.LoadHarness.Metrics;
 namespace ZB.MOM.WW.ScadaBridge.LoadHarness.Scenarios;
 
 /// <summary>
-/// The two "does observability still work at scale?" probes WP-4's test protocol
+/// The two "does observability still work at scale?" probes the target-scale test protocol
 /// names — health report delivery timing and debug view latency — run continuously
 /// alongside the sustained load rather than after it, so both are measured against a
 /// site that is actually busy.
@@ -137,7 +137,8 @@ public sealed class ObservabilityProbes : IAsyncDisposable
 
     private int _disposed;
 
-    /// <inheritdoc />
+    /// <summary>Stops the probes and releases their resources.</summary>
+    /// <returns>A task that represents the asynchronous operation.</returns>
     public async ValueTask DisposeAsync()
     {
         // Idempotent: the orchestrator stops the probes early (so the register row 50

tests/ZB.MOM.WW.ScadaBridge.LoadHarness/Scenarios/StoreAndForwardDrainScenario.cs

@@ -49,7 +49,7 @@ public sealed record DrainProgressSample(double ElapsedSeconds, long Delivered,
 /// Phase 1 buffers <paramref name="messageCount"/> messages with
 /// <c>attemptImmediateDelivery: false</c>, spread across many origin instance names
 /// and issued from many concurrent tasks — the "concurrent buffering from multiple
-/// instances" WP-4 asks about (<c>[xc-7]</c>). Phase 2 registers a delivery handler
+/// instances" case the load test targets. Phase 2 registers a delivery handler
 /// that always succeeds and drives sweeps to completion, timing the drain.
 /// </para>
 /// <para>