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/AddressSpaceApplier.cs

@@ -20,7 +20,7 @@ namespace ZB.MOM.WW.OtOpcUa.OpcUaServer;
 ///             tear-down + rebuild.</item>
 ///     </list>
 ///
-///     This is the side-effecting layer Task 47 deferred to F14. It stays pure-of-SDK so
+///     This is the side-effecting layer deferred to F14. It stays pure-of-SDK so
 ///     production binds a real SDK sink, dev/Mac binds <see cref="NullOpcUaAddressSpaceSink"/>,
 ///     and tests can capture every call.
 /// </summary>
@@ -101,7 +101,7 @@ public sealed class AddressSpaceApplier
             plan.ChangedEquipment.Count + plan.ChangedDrivers.Count + plan.ChangedAlarms.Count +
             plan.ChangedEquipmentTags.Count +
             plan.ChangedEquipmentVirtualTags.Count +
-            // OpcUaServer-001: a UNS Area/Line rename is an in-place change to an existing folder node.
+            // A UNS Area/Line rename is an in-place change to an existing folder node.
             plan.RenamedFolders.Count;
         var addedCount =
             plan.AddedEquipment.Count + plan.AddedDrivers.Count + plan.AddedAlarms.Count +
@@ -122,7 +122,7 @@ public sealed class AddressSpaceApplier
         // respawn (DriverHostActor → ApplyVirtualTags), so it skips the rebuild and PRESERVES every
         // client's server-wide subscriptions. Any structural / node-affecting vtag change (Name/
         // FolderPath/DataType) — or any non-vtag change anywhere — still forces a full rebuild.
-        // F10b + FB-7 (surgical tag write): a CHANGED equipment tag whose ONLY differences are Writable /
+        // F10b (surgical tag write): a CHANGED equipment tag whose ONLY differences are Writable /
         // IsHistorized / HistorianTagname / DataType / IsArray / ArrayLength (a plain value variable — no
         // alarm condition node) can be updated IN PLACE on the existing node via
         // ISurgicalAddressSpaceSink.UpdateTagAttributes (see TagDeltaIsSurgicalEligible), avoiding the full
@@ -140,7 +140,7 @@ public sealed class AddressSpaceApplier
             plan.ChangedEquipmentVirtualTags.Any(d => !VtagDeltaIsNodeIrrelevant(d));
 
         var surgicalTagDeltas = plan.ChangedEquipmentTags.Where(TagDeltaIsSurgicalEligible).ToList();
-        // OpcUaServer-001 — UNS Area / Line renames are surgically applicable (in-place DisplayName swap)
+        // UNS Area / Line renames are surgically applicable (in-place DisplayName swap)
         // when no structural rebuild fires. When a rebuild DOES fire (any add/remove/structural change),
         // MaterialiseHierarchy re-creates every folder with the new display names, so the renames are
         // covered for free and need no separate surgical pass.
@@ -383,7 +383,7 @@ public sealed class AddressSpaceApplier
     }
 
     /// <summary>
-    ///     #85 — build the UNS Area/Line/Equipment folder hierarchy in the address space from a
+    ///     Build the UNS Area/Line/Equipment folder hierarchy in the address space from a
     ///     composition snapshot. Called by <c>OpcUaPublishActor</c> after a rebuild so OPC UA
     ///     clients browsing the server see proper folder structure instead of flat tag ids.
     ///     Idempotent: each <c>EnsureFolder</c> call returns the existing folder if already
@@ -420,19 +420,13 @@ public sealed class AddressSpaceApplier
     ///     ensure its optional <c>FolderPath</c> sub-folder under the existing equipment folder, then
     ///     ensure a Variable (NodeId = <c>FullName</c>, the driver-side ref) inside it. Variables
     ///     start BadWaitingForInitialData; the driver fills live values in a later milestone.
-    ///     Idempotent.
-    ///     <para>
-    ///         <b>Task 0 architecture decisions (recorded per the equipment-namespace-structure
-    ///         plan).</b> Decision #1 = <b>A</b> — a sink-based pass, NOT a reuse of
-    ///         <c>EquipmentNodeWalker</c>: no sink-backed <c>IAddressSpaceBuilder</c> adapter exists
-    ///         (<c>GenericDriverNodeManager.CapturingBuilder</c> decorates another builder, not the
-    ///         sink), and the walker re-creates the whole Area/Line/Equipment tree with browse-path
-    ///         NodeIds — incompatible with this path's logical-Id NodeIds (decision #3) and the
-    ///         already-materialised equipment folders (decision #4). Decision #4 = this pass adds
-    ///         ONLY variables (and any per-tag sub-folder); <see cref="MaterialiseHierarchy"/> owns
-    ///         the equipment folders and this pass never re-creates them. The sink's
-    ///         <c>EnsureVariable</c> takes a plain <c>string dataType</c> (not a DriverAttributeInfo).
-    ///     </para>
+    ///     Idempotent. This is a sink-based pass, NOT a reuse of <c>EquipmentNodeWalker</c>: no
+    ///     sink-backed <c>IAddressSpaceBuilder</c> adapter exists, and the walker re-creates the
+    ///     whole Area/Line/Equipment tree with browse-path NodeIds, incompatible with this path's
+    ///     logical-Id NodeIds and the already-materialised equipment folders. This pass adds ONLY
+    ///     variables (and any per-tag sub-folder); <see cref="MaterialiseHierarchy"/> owns the
+    ///     equipment folders and this pass never re-creates them. The sink's <c>EnsureVariable</c>
+    ///     takes a plain <c>string dataType</c> (not a DriverAttributeInfo).
     /// </summary>
     /// <param name="composition">The composition result containing the equipment tags to materialise.</param>
     public void MaterialiseEquipmentTags(AddressSpaceComposition composition)
@@ -442,7 +436,7 @@ public sealed class AddressSpaceApplier
 
         // Sub-folders first — a tag's FolderPath becomes one folder UNDER its equipment folder
         // (deduped per distinct equipment+path). Tags with no FolderPath hang directly under the
-        // equipment folder, which MaterialiseHierarchy already created (decision #4: never re-create
+        // equipment folder, which MaterialiseHierarchy already created (never re-create
         // the equipment folder here).
         var foldersCreated = new HashSet<string>(StringComparer.Ordinal);
         foreach (var tag in composition.EquipmentTags)
@@ -641,7 +635,7 @@ public sealed class AddressSpaceApplier
             Historize = d.Current.Historize,
         }).Equals(d.Current);
 
-    // F10b + FB-7: a CHANGED equipment tag whose ONLY differences are Writable / IsHistorized /
+    // F10b: a CHANGED equipment tag whose ONLY differences are Writable / IsHistorized /
     // HistorianTagname / DataType / IsArray / ArrayLength (a plain value variable — no alarm condition node)
     // can be updated IN PLACE on the existing node via ISurgicalAddressSpaceSink.UpdateTagAttributes,
     // avoiding a full rebuild (preserving subscriptions). The presentation-shape fields (DataType / IsArray /
@@ -650,7 +644,7 @@ public sealed class AddressSpaceApplier
     // differences still fall through to a rebuild — FullName/DriverInstanceId re-route the node to a different
     // driver point, Name re-derives the NodeId, and an alarm flip turns the node into a Part 9 condition. The
     // override-unequal default also covers any future field.
-    // REACH (live-verified FB-7): the shape path only fires for drivers whose TagConfig carries a stable
+    // REACH (live-verified): the shape path only fires for drivers whose TagConfig carries a stable
     // top-level "FullName" (Galaxy = tag_name.AttributeName; OpcUaClient = the node id) — there a DataType/array
     // edit leaves FullName untouched ⇒ surgical. For structured-TagConfig protocol drivers (Modbus/S7/AbCip/…)
     // AddressSpaceComposer.ExtractTagFullName falls back to the RAW TagConfig blob as FullName, so a DataType/