docs(comments): strip internal task/milestone/bundle bookkeeping from code comments

Remove project bookkeeping citations from shipped code comments across the
solution: hyphenated task IDs (WP-14, StoreAndForward-025), milestone/task/
issue refs (M3, Task 4, Audit Log #23, #21), Bundle X task-bundle labels,
and C/D/K/S/T phase labels.

Comment text only — no code logic, string/log literals, or XML-doc structure
changed. Genuine descriptions are preserved (only the citation is stripped),
and technical lookalikes are retained (UTF-8, SHA-256, T00:00:00, M365,
UTC-5, pre-C4/pre-C5 schema versions). Flagged by the new CommentChecker
TaskReferenceInComment / TrackingReferenceInComment checks plus targeted
grep passes; full solution builds clean, append-only guard tests pass.

src/ZB.MOM.WW.ScadaBridge.AuditLog/Site/HealthMetricsAuditRedactionFailureCounter.cs

@@ -4,7 +4,7 @@ using ZB.MOM.WW.ScadaBridge.HealthMonitoring;
 namespace ZB.MOM.WW.ScadaBridge.AuditLog.Site;
 
 /// <summary>
-/// Audit Log (#23) M5 Bundle C — bridges
+/// Bridges
 /// <see cref="IAuditRedactionFailureCounter"/> (incremented by
 /// <see cref="ZB.MOM.WW.ScadaBridge.AuditLog.Redaction.ScadaBridgeAuditRedactor"/> every time
 /// a header / body / SQL parameter redactor stage throws and the redactor has
@@ -22,16 +22,15 @@ namespace ZB.MOM.WW.ScadaBridge.AuditLog.Site;
 /// redaction failures must NEVER abort the user-facing action, alog.md §7).
 /// </para>
 /// <para>
-/// Mirrors the M2 Bundle G <see cref="HealthMetricsAuditWriteFailureCounter"/>
+/// Mirrors the <see cref="HealthMetricsAuditWriteFailureCounter"/>
 /// shape one-for-one so the two health-metric bridges age together.
 /// </para>
 /// <para>
-/// Site-side only for M5: the redaction filter also runs on the central
-/// writers (CentralAuditWriter + AuditLogIngestActor), but the central
-/// health-metric surface that would expose <c>AuditRedactionFailure</c>
-/// alongside the existing central counters ships in M6. Until then, the
-/// central composition root keeps the NoOp default — the redactions still
-/// happen, they just don't get counted into a health report.
+/// Site-side only: the redaction filter also runs on the central
+/// writers (CentralAuditWriter + AuditLogIngestActor); the central
+/// health-metric surface exposing <c>AuditRedactionFailure</c> is bridged
+/// separately by <c>CentralAuditRedactionFailureCounter</c>, which the
+/// central composition root registers in place of the NoOp default.
 /// </para>
 /// </remarks>
 public sealed class HealthMetricsAuditRedactionFailureCounter : IAuditRedactionFailureCounter