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.CentralUI/ScriptAnalysis/SandboxConsoleCapture.cs

@@ -10,7 +10,7 @@ namespace ZB.MOM.WW.ScadaBridge.CentralUI.ScriptAnalysis;
 /// however, <b>process-global</b>: redirecting it with <c>Console.SetOut</c> for
 /// the duration of one run corrupts any other run executing concurrently —
 /// outputs interleave, and whichever run finishes first restores
-/// <c>Console.Out</c> while the others are still writing (CentralUI-003).
+/// <c>Console.Out</c> while the others are still writing.
 /// </para>
 /// <para>
 /// This writer is installed into <c>Console.Out</c>/<c>Console.Error</c>
@@ -81,7 +81,7 @@ internal sealed class SandboxConsoleCapture : TextWriter
         return new CaptureScope(this, previous);
     }
 
-    // CentralUI-030: intra-script concurrency hardening. A sandboxed script
+    // Intra-script concurrency hardening. A sandboxed script
     // can fan out work with `Task.WhenAll` / `Task.Run`; `AsyncLocal` flows
     // the capture `StringWriter` into every child task, so two tasks can
     // race the *same* buffer. `StringWriter` is not thread-safe — concurrent