mbproxy: strip historical phase/wave/plan references from source comments

Comments described the *history* of how the code arrived (phase numbers,
wave IDs, review IDs, dated TODOs) instead of what it does today. That
scaffolding rotted as the codebase evolved. Cleaned 60 source files +
.gitignore; behaviour unchanged (387/387 tests still pass).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

mbproxy/src/Mbproxy/Admin/StatusDto.cs

@@ -60,9 +60,9 @@ public sealed record PlcPdusStatus(
     long RewrittenSlots,
     long PartialBcdWarnings,
     /// <summary>
-    /// Phase 12 (W2.22) — count of BCD-rewriter slot decisions where the wire value was
-    /// not a valid BCD nibble pattern (e.g. <c>0xABCD</c> at a tag address). The slot
-    /// passes through unrewritten and this counter increments.
+    /// Count of BCD-rewriter slot decisions where the wire value was not a valid BCD
+    /// nibble pattern (e.g. <c>0xABCD</c> at a tag address). The slot passes through
+    /// unrewritten and this counter increments.
     /// </summary>
     long InvalidBcdWarnings);
 
@@ -75,15 +75,16 @@ public sealed record FcCounts(
     long Other);
 
 /// <summary>
-/// Backend connect, exception, and multiplexer telemetry. Phase 9 added
-/// <c>InFlight</c>, <c>MaxInFlight</c>, <c>TxIdWraps</c>, <c>DisconnectCascades</c>, and
-/// <c>QueueDepth</c>. Phase 10 added the three coalescing counters
-/// (<c>CoalescedHitCount</c>, <c>CoalescedMissCount</c>, <c>CoalescedResponseToDeadUpstream</c>);
-/// the dashboard-side derived <c>coalescingRatio</c> is intentionally NOT carried on the wire
-/// — consumers compute <c>Hit / (Hit + Miss)</c>. Phase 11 added the five cache counters
-/// (<c>CacheHitCount</c>, <c>CacheMissCount</c>, <c>CacheInvalidations</c>,
-/// <c>CacheEntryCount</c>, <c>CacheBytes</c>); the dashboard-side derived
-/// <c>cacheHitRatio</c> is intentionally NOT carried on the wire.
+/// Backend connect, exception, and multiplexer telemetry, including the in-flight
+/// multiplexer fields (<c>InFlight</c>, <c>MaxInFlight</c>, <c>TxIdWraps</c>,
+/// <c>DisconnectCascades</c>, <c>QueueDepth</c>), the read-coalescing counters
+/// (<c>CoalescedHitCount</c>, <c>CoalescedMissCount</c>, <c>CoalescedResponseToDeadUpstream</c>),
+/// and the response-cache counters (<c>CacheHitCount</c>, <c>CacheMissCount</c>,
+/// <c>CacheInvalidations</c>, <c>CacheEntryCount</c>, <c>CacheBytes</c>).
+///
+/// <para>The dashboard-side derived ratios <c>coalescingRatio</c> and <c>cacheHitRatio</c>
+/// are intentionally NOT carried on the wire — consumers compute <c>Hit / (Hit + Miss)</c>
+/// from the raw counters.</para>
 /// </summary>
 public sealed record PlcBackendStatus(
     long ConnectsSuccess,
@@ -111,8 +112,8 @@ public sealed record ExceptionCounts(
     long Code03,
     long Code04,
     /// <summary>
-    /// Phase 12 (W2.22) — backend exceptions whose response code is not 01–04 (e.g. 0x06
-    /// Server Device Busy, 0x0B Gateway Target Failed To Respond, vendor-specific codes).
+    /// Backend exceptions whose response code is not 01–04 (e.g. 0x06 Server Device
+    /// Busy, 0x0B Gateway Target Failed To Respond, vendor-specific codes).
     /// </summary>
     long CodeOther);