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.SiteRuntime/Scripts/AuditingDbCommand.cs

@@ -10,12 +10,12 @@ using AuditEvent = ZB.MOM.WW.Audit.AuditEvent;
 namespace ZB.MOM.WW.ScadaBridge.SiteRuntime.Scripts;
 
 /// <summary>
-/// Audit Log #23 — M4 Bundle A: <see cref="DbCommand"/> decorator that emits
+/// <see cref="DbCommand"/> decorator that emits
 /// exactly one <c>DbOutbound</c>/<c>DbWrite</c> audit event per execution.
 /// </summary>
 /// <remarks>
 /// <para>
-/// <b>Vocabulary lock (M4 plan):</b> both writes (Execute / ExecuteScalar) and
+/// <b>Vocabulary lock:</b> both writes (Execute / ExecuteScalar) and
 /// reads (ExecuteReader) emit <see cref="AuditKind.DbWrite"/> on the
 /// <see cref="AuditChannel.DbOutbound"/> channel. The <c>Extra</c> JSON column
 /// distinguishes them — <c>{"op":"write","rowsAffected":N}</c> for writes,
@@ -41,7 +41,7 @@ internal sealed class AuditingDbCommand : DbCommand
     private readonly Guid _executionId;
 
     /// <summary>
-    /// Audit Log #23 (ParentExecutionId): the spawning execution's id when this
+    /// ParentExecutionId: the spawning execution's id when this
     /// run was inbound-API-routed; <c>null</c> for non-routed runs. Threaded
     /// alongside <see cref="_executionId"/> and stamped onto the <c>DbWrite</c>
     /// audit row.
@@ -136,9 +136,9 @@ internal sealed class AuditingDbCommand : DbCommand
         // the wrapper, but writes from the user go through to the inner
         // command so the underlying provider keeps its wiring intact.
         get => _wrappingConnection ?? _inner.Connection;
-        // SiteRuntime-022: unwrap the AuditingDbConnection wrapper via its
+        // Unwrap the AuditingDbConnection wrapper via its
         // own internal Inner accessor instead of reflecting into a private
-        // _inner field. Reflection was the original SiteRuntime-006 anti-
+        // _inner field. Reflection was the original anti-
         // pattern (and is forbidden inside script bodies by the trust
         // model) — both classes are internal sealed in the same assembly,
         // so the proper API surface is available without leaking anything
@@ -223,7 +223,7 @@ internal sealed class AuditingDbCommand : DbCommand
         }
         finally
         {
-            // ExecuteScalar is classified as "write" per the M4 vocabulary
+            // ExecuteScalar is classified as "write" per the vocabulary
             // lock — it's a single-value execution; rowsAffected mirrors the
             // inner command's value if exposed (DbCommand has no RecordsAffected
             // property, so we report -1 when the provider didn't surface it).
@@ -382,7 +382,7 @@ internal sealed class AuditingDbCommand : DbCommand
 
     /// <summary>
     /// Best-effort emission of one <c>DbOutbound</c>/<c>DbWrite</c> audit row.
-    /// Mirrors the M2 Bundle F <c>EmitCallAudit</c> 3-layer fail-safe pattern.
+    /// Mirrors the <c>EmitCallAudit</c> 3-layer fail-safe pattern.
     /// </summary>
     private void EmitAudit(
         DateTime occurredAtUtc,
@@ -463,7 +463,7 @@ internal sealed class AuditingDbCommand : DbCommand
         }
 
         // RequestSummary captures the SQL statement + parameter values by
-        // default per the alog.md M4 acceptance criteria. Per-target SQL
+        // default per the alog.md acceptance criteria. Per-target SQL
         // parameter redaction is configured via AuditLogOptions.PerTargetOverrides
         // (RedactSqlParamsMatching) and applied at write time by the redactor.
         string? requestSummary = BuildRequestSummary();
@@ -485,13 +485,13 @@ internal sealed class AuditingDbCommand : DbCommand
             // (e.g. a shared script running inline).
             actor: _sourceScript,
             target: target,
-            // Audit Log #23: a sync one-shot DB write has no operation
+            // A sync one-shot DB write has no operation
             // lifecycle, so CorrelationId is null. ExecutionId carries the
             // per-execution id so this row shares an id with the other sync
             // trust-boundary rows from the same script run.
             correlationId: null,
             executionId: _executionId,
-            // Audit Log #23 (ParentExecutionId): the spawning execution's id;
+            // ParentExecutionId: the spawning execution's id;
             // null for non-routed runs.
             parentExecutionId: _parentExecutionId,
             sourceSiteId: string.IsNullOrEmpty(_siteId) ? null : _siteId,
@@ -510,7 +510,7 @@ internal sealed class AuditingDbCommand : DbCommand
     /// <summary>
     /// Compose a JSON request summary capturing the SQL statement and
     /// parameter values. Parameter values are captured by default per the
-    /// M4 acceptance criteria; per-target SQL-parameter redaction is applied
+    /// acceptance criteria; per-target SQL-parameter redaction is applied
     /// at write time via <c>AuditLogOptions.PerTargetOverrides.RedactSqlParamsMatching</c>.
     /// </summary>
     private string? BuildRequestSummary()