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.InboundAPI/InboundDatabaseHelper.cs

@@ -13,7 +13,7 @@ namespace ZB.MOM.WW.ScadaBridge.InboundAPI;
 /// by name and never reference <c>System.Data</c>.
 ///
 /// <para>
-/// <b>SQL-injection protection (InboundAPI-026).</b> Statement text is authored by the
+/// <b>SQL-injection protection.</b> Statement text is authored by the
 /// (design-time) method script, but every <em>value</em> is bound as a named SQL
 /// parameter (anonymous-object properties become <c>@</c>-prefixed parameters via
 /// <see cref="AddParameters"/>) and is NEVER string-concatenated into the command text.
@@ -24,13 +24,13 @@ namespace ZB.MOM.WW.ScadaBridge.InboundAPI;
 /// </para>
 ///
 /// <para>
-/// <b>Reads and writes are both permitted</b> (InboundAPI-026 design decision): the move-in
+/// <b>Reads and writes are both permitted</b>: the move-in
 /// integration needs to record results, not just read them. Use <see cref="QueryAsync"/>
 /// / <see cref="QuerySingleAsync{T}"/> for reads and <see cref="ExecuteAsync"/> for writes.
 /// </para>
 ///
 /// <para>
-/// <b>Async + deadline-bound (InboundAPI-027).</b> Every call uses the async ADO.NET path
+/// <b>Async + deadline-bound.</b> Every call uses the async ADO.NET path
 /// end-to-end (no <c>.GetAwaiter().GetResult()</c> blocking a pool thread) and honours the
 /// executing method's deadline token on the command itself, with a <see cref="DbCommand.CommandTimeout"/>
 /// backstop derived from the method timeout — so a slow query is bounded by the method
@@ -103,7 +103,7 @@ public sealed class InboundDatabaseHelper
 
     /// <summary>
     /// Executes a write statement (INSERT/UPDATE/DELETE/DDL) and returns the number of
-    /// rows affected. Writes are authorized for inbound API scripts (InboundAPI-026);
+    /// rows affected. Writes are authorized for inbound API scripts;
     /// values are still bound as parameters, never concatenated.
     /// </summary>
     /// <param name="connectionName">Name of a connection configured on the central database gateway.</param>
@@ -122,7 +122,7 @@ public sealed class InboundDatabaseHelper
     {
         var cmd = conn.CreateCommand();
         cmd.CommandText = sql;
-        // InboundAPI-027: a CommandTimeout backstop derived from the method timeout so a
+        // A CommandTimeout backstop derived from the method timeout so a
         // slow query cannot outrun the method deadline even if the provider does not
         // honour token cancellation mid-statement.
         if (_commandTimeoutSeconds > 0) cmd.CommandTimeout = _commandTimeoutSeconds;