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/Central/AuditLogPartitionMaintenanceService.cs

@@ -7,7 +7,7 @@ using ZB.MOM.WW.ScadaBridge.Commons.Interfaces;
 namespace ZB.MOM.WW.ScadaBridge.AuditLog.Central;
 
 /// <summary>
-/// Central <see cref="IHostedService"/> (M6-T5, Bundle D) that rolls
+/// Central <see cref="IHostedService"/> that rolls
 /// <c>pf_AuditLog_Month</c> forward once a day. Each tick opens a fresh DI
 /// scope, resolves <see cref="IPartitionMaintenance"/>, and calls
 /// <see cref="IPartitionMaintenance.EnsureLookaheadAsync"/> to SPLIT any
@@ -19,7 +19,7 @@ namespace ZB.MOM.WW.ScadaBridge.AuditLog.Central;
 /// </summary>
 /// <remarks>
 /// <para>
-/// <b>Why a hosted service, not an actor.</b> Bundle C's
+/// <b>Why a hosted service, not an actor.</b>
 /// <see cref="AuditLogPurgeActor"/> sits inside the central singleton
 /// because it needs supervised lifecycle alongside the rest of the
 /// reconciliation / ingest pipeline. Roll-forward is genuinely a once-a-day
@@ -33,8 +33,7 @@ namespace ZB.MOM.WW.ScadaBridge.AuditLog.Central;
 /// <b>Failure containment.</b> The tick body wraps the maintenance call in
 /// a try/catch so a transient SQL Server error never tears down the hosted
 /// service — the next tick simply retries. The exception is logged with
-/// the original stack trace at <c>Error</c> level; ops surfaces (M6 Bundle
-/// E's central health collector) can subscribe to the logger to alert on
+/// the original stack trace at <c>Error</c> level; ops surfaces can subscribe to the logger to alert on
 /// repeated failures.
 /// </para>
 /// <para>