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

@@ -5,7 +5,7 @@ using Microsoft.CodeAnalysis.CSharp.Syntax;
 namespace ZB.MOM.WW.ScadaBridge.ScriptAnalysis;
 
 /// <summary>
-/// M3.1: the single authoritative script-trust validator, fusing the two
+/// The single authoritative script-trust validator, fusing the two
 /// previously-divergent implementations:
 ///
 /// <list type="number">
@@ -80,8 +80,8 @@ public static class ScriptTrustValidator
     /// public entry point above always uses the full analysis set; this overload
     /// exists so tests can pin behaviour against the minimal TPA-fallback set
     /// (<see cref="ScriptTrustPolicy.BuildMinimalFallbackReferences"/>) and prove
-    /// the degraded mode still catches the documented forbidden anchors
-    /// (ScriptAnalysis-001). The two passes are otherwise identical.
+    /// the degraded mode still catches the documented forbidden anchors.
+    /// The two passes are otherwise identical.
     /// </summary>
     /// <param name="code">The C# script source to analyse.</param>
     /// <param name="baseReferences">The base reference set Pass 1 resolves against.</param>