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.ManagementService/ManagementEndpoints.cs

@@ -18,8 +18,8 @@ public static class ManagementEndpoints
     private static readonly TimeSpan DefaultAskTimeout = TimeSpan.FromSeconds(30);
 
     /// <summary>
-    /// Resolves the ManagementActor Ask timeout from configuration
-    /// (finding ManagementService-010). Falls back to <see cref="DefaultAskTimeout"/>
+    /// Resolves the ManagementActor Ask timeout from configuration.
+    /// Falls back to <see cref="DefaultAskTimeout"/>
     /// when options are absent or the configured value is not strictly positive — a
     /// zero/negative timeout would make every management call fail immediately.
     /// </summary>
@@ -43,7 +43,7 @@ public static class ManagementEndpoints
 
     /// <summary>
     /// Per-request body-size ceiling for the management endpoint. ASP.NET Core's
-    /// default cap is ~30 MB and would reject Transport (#24) Import calls -- a
+    /// default cap is ~30 MB and would reject Transport Import calls -- a
     /// 100 MB raw bundle base64-inflates to ~140 MB plus envelope. 200 MB is
     /// comfortable without going unbounded.
     /// </summary>
@@ -142,7 +142,7 @@ public static class ManagementEndpoints
     /// Parses a management request body — a JSON object with a <c>command</c> name and an
     /// optional <c>payload</c> — into the strongly-typed command record. The parsed
     /// <see cref="JsonDocument"/> is disposed deterministically and the missing-payload
-    /// case does not allocate a throwaway document (finding ManagementService-006).
+    /// case does not allocate a throwaway document.
     /// </summary>
     /// <param name="body">The raw JSON request body string.</param>
     /// <returns>A <see cref="CommandParseResult"/> with the deserialized command on success, or an error on failure.</returns>