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).
2026-10-07 15:34:32 -04:00
parent f2e0861709
commit f40409a688
115 changed files with 549 additions and 411 deletions
@@ -239,14 +239,14 @@ public sealed class MxAccessEventMapperTests
    }

    /// <summary>
-    ///     Verifies the exact-format fast path PERF-20 added in front of the
+    ///     Verifies the exact-format fast path added in front of the
    ///     general parse chain returns exactly what that chain returned. The
    ///     cases cover the captured MXAccess shape (which the fast path is meant
    ///     to catch on a US-shaped host), its zero-padded and second-precision
    ///     siblings, and strings the derived formats cannot match — an ISO
    ///     round-trip form, a long-date form, and a day-first European form —
    ///     which must fall through to the unchanged two-stage chain. The
-    ///     expectation is computed with the pre-PERF-20 chain in this test, so it
+    ///     expectation is computed with the original chain in this test, so it
    ///     holds on any host culture: the fast path is a shortcut, never a
    ///     different answer.
    /// </summary>
@@ -353,8 +353,8 @@ public sealed class MxAccessEventMapperTests
    }

    /// <summary>
-    ///     The parse chain exactly as it stood before PERF-20 added the
-    ///     exact-format stage, used as the parity oracle above.
+    ///     The parse chain exactly as it stood before the
+    ///     exact-format stage was added, used as the parity oracle above.
    /// </summary>
    /// <param name="text">Timestamp string to parse.</param>
    /// <param name="utc">The parsed UTC timestamp on success.</param>