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.Host/StartupRetry.cs

@@ -3,14 +3,14 @@ namespace ZB.MOM.WW.ScadaBridge.Host;
 /// <summary>
 /// Bounded retry-with-backoff for startup preconditions.
 ///
-/// Host-010 / REQ-HOST-4a: a Central node applies/validates database migrations
+/// REQ-HOST-4a: a Central node applies/validates database migrations
 /// before the host begins serving traffic. In container orchestration the database
 /// and the app frequently start together, so the database may be briefly
 /// unreachable. Rather than crashing the process on the first connection failure,
 /// the migration step is wrapped in this bounded exponential backoff: it tolerates a
 /// short outage and only fails fatally once attempts are exhausted.
 ///
-/// Host-015: only <em>transient</em> faults are retried. The optional
+/// Only <em>transient</em> faults are retried. The optional
 /// <c>isTransient</c> predicate classifies each exception; a permanent failure
 /// (e.g. a database schema-version mismatch — which no amount of waiting can fix)
 /// is rethrown immediately rather than being retried for minutes before the
@@ -42,7 +42,7 @@ public static class StartupRetry
     /// <summary>
     /// Executes an asynchronous operation with bounded exponential backoff, retrying only transient faults.
     /// Overload that forwards the retry-loop cancellation token to the operation itself —
-    /// Host-019: needed so callers (e.g. the database-migration step) can honour
+    /// needed so callers (e.g. the database-migration step) can honour
     /// <c>IHostApplicationLifetime.ApplicationStopping</c> inside the operation as well
     /// as inside the inter-attempt <c>Task.Delay</c>.
     /// </summary>
@@ -63,7 +63,7 @@ public static class StartupRetry
         Func<Exception, bool>? isTransient = null,
         CancellationToken cancellationToken = default)
     {
-        // Default: treat every exception as transient (preserves the pre-Host-015
+        // Default: treat every exception as transient (preserves the pre-existing
         // behaviour for callers that do not classify faults).
         isTransient ??= static _ => true;
 
@@ -94,7 +94,7 @@ public static class StartupRetry
     }
 
     /// <summary>
-    /// Transient-fault classifier for the database-migration startup step (Host-015).
+    /// Transient-fault classifier for the database-migration startup step.
     /// Returns <c>true</c> only for connection-class faults that a brief wait can
     /// resolve — a SQL connection/transport error or a timeout — and <c>false</c>
     /// for everything else (notably schema-validation <see cref="InvalidOperationException"/>s