docs(xmldoc): fill missing XML docs + strip tracking-ID comments across src

Adds <summary>/<param>/<returns>/<inheritdoc> where missing and removes
project bookkeeping IDs (task/tracking refs) from shipped code comments,
so the docs read cleanly and CommentChecker is quiet except for known
false positives (PLC/protocol terms, event/IEqualityComparer inheritdoc).
Doc/comment-only; no logic changed; solution builds clean.

src/Server/ZB.MOM.WW.OtOpcUa.OpcUaServer/AddressSpacePlan.cs

@@ -53,7 +53,7 @@ public sealed record AddressSpacePlan(
     public IReadOnlyList<EquipmentVirtualTagDelta> ChangedEquipmentVirtualTags { get; init; } = Array.Empty<EquipmentVirtualTagDelta>();
 
     /// <summary>
-    ///     OpcUaServer-001 — UNS Area / Line folder renames: a folder whose stable id is unchanged but
+    ///     UNS Area / Line folder renames: a folder whose stable id is unchanged but
     ///     whose <c>DisplayName</c> differs between the previous + next composition. A deploy whose ONLY
     ///     change is an Area or Line rename produces NO Equipment / Driver / Alarm / Tag / VirtualTag
     ///     delta, so without this set the plan would be <see cref="IsEmpty"/> and
@@ -84,7 +84,7 @@ public sealed record AddressSpacePlan(
     public sealed record EquipmentTagDelta(EquipmentTagPlan Previous, EquipmentTagPlan Current);
     public sealed record EquipmentVirtualTagDelta(EquipmentVirtualTagPlan Previous, EquipmentVirtualTagPlan Current);
 
-    /// <summary>OpcUaServer-001 — one renamed UNS Area / Line folder: the stable folder
+    /// <summary>One renamed UNS Area / Line folder: the stable folder
     /// <paramref name="FolderNodeId"/> (the area's <c>UnsAreaId</c> or line's <c>UnsLineId</c>, the exact
     /// NodeId <c>MaterialiseHierarchy</c> placed the folder at) and the <paramref name="NewDisplayName"/>
     /// to apply in place.</summary>
@@ -103,6 +103,7 @@ public static class AddressSpacePlanner
     /// </summary>
     /// <param name="previous">The previous composition result.</param>
     /// <param name="next">The new composition result.</param>
+    /// <returns>The diff plan between the two compositions.</returns>
     public static AddressSpacePlan Compute(AddressSpaceComposition previous, AddressSpaceComposition next)
     {
         ArgumentNullException.ThrowIfNull(previous);
@@ -138,7 +139,7 @@ public static class AddressSpacePlanner
             t => t.VirtualTagId,
             (a, b) => new AddressSpacePlan.EquipmentVirtualTagDelta(a, b));
 
-        // OpcUaServer-001 — UNS Area / Line renames: a folder whose stable id is unchanged but whose
+        // UNS Area / Line renames: a folder whose stable id is unchanged but whose
         // DisplayName differs. Diffed by stable id (UnsAreaId / UnsLineId) so an Area/Line whose ONLY
         // change is its friendly name is no longer a silent no-op at the IsEmpty gate. The folder NodeId
         // IS the area/line id (the exact scheme MaterialiseHierarchy uses), so the rename carries it
@@ -163,7 +164,7 @@ public static class AddressSpacePlanner
     }
 
     /// <summary>
-    ///     OpcUaServer-001 — emit a <see cref="AddressSpacePlan.FolderRename"/> for every folder present in
+    ///     Emit a <see cref="AddressSpacePlan.FolderRename"/> for every folder present in
     ///     BOTH snapshots (matched by stable <paramref name="identity"/>) whose <paramref name="displayName"/>
     ///     differs (ordinal). Added/removed folders are NOT renames — they're handled by the equipment /
     ///     hierarchy rebuild path — so this pass only flags an in-place display-name change on a surviving