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.StoreAndForward/NotificationForwarder.cs

@@ -50,7 +50,7 @@ public sealed class NotificationForwarder
     /// failure. Sourced from host configuration.
     /// </param>
     /// <param name="logger">
-    /// Optional logger. StoreAndForward-018: a corrupt buffered payload is logged at
+    /// Optional logger. A corrupt buffered payload is logged at
     /// Warning before being discarded so an operator has a forensic trail of the row
     /// that vanished from the buffer.
     /// </param>
@@ -76,18 +76,6 @@ public sealed class NotificationForwarder
     /// <returns>A task that resolves to <c>true</c> when central accepts (or the payload is corrupt and discarded); throws on a transient forward failure so the engine retries.</returns>
     public async Task<bool> DeliverAsync(StoreAndForwardMessage message)
     {
-        // StoreAndForward-018: an unreadable payload cannot be fixed by retrying.
-        // The design doc explicitly forbids parking notifications ("notifications do
-        // not park — they are retried at the fixed forward interval until central
-        // acks"; Component-StoreAndForward.md). The earlier behaviour returned false
-        // here, which the S&F engine interprets as a permanent failure and parks
-        // the row — contradicting the invariant and surfacing the row in the
-        // central UI's parked-message list. The correct outcome for a corrupt-payload
-        // notification is to DISCARD: log a Warning with the buffered row id +
-        // payload preview for forensics, then return true so the engine clears the
-        // buffer via its standard success-path cleanup. The buffered row is
-        // unrecoverable; retrying or parking would both make the queue worse, not
-        // better.
         if (!TryBuildSubmit(message, out var submit))
         {
             _logger.LogWarning(
@@ -122,7 +110,7 @@ public sealed class NotificationForwarder
     /// forwarded to central, returning <c>false</c> if the payload is unreadable.
     ///
     /// The buffered payload IS a serialized <see cref="NotificationSubmit"/> written by
-    /// the site <c>Notify.Send</c> enqueue path (Task 19). Its
+    /// the site <c>Notify.Send</c> enqueue path. Its
     /// <see cref="NotificationSubmit.NotificationId"/> is the central idempotency key —
     /// it was generated by the script, equals the buffered row's
     /// <see cref="StoreAndForwardMessage.Id"/>, and is stable across every retry. The