fix(address-space): announce surgically-added raw nodes; equipment-with-references removal stays surgical (#599)

- AnnounceAddedNodes raises NodeAdded in the Raw realm for the existing parents of
  added raw containers/tags (ComputeRawAddAnnouncements); Uns side unchanged.
- ApplyPureRemove removes UNS reference variables BEFORE the equipment subtree, so a
  reference the subtree's id-prefix scope reaches no longer ratchets to a full rebuild
  (03/P5). A NotSubsumed filter was not used: in production a reference NodeId is
  Area/Line/Equipment/Name, outside the subtree scope, so filtering would leak it.
  The matching RemoveEquipmentSubtree severing (03/S20) is in the node-manager commit.
- UnsReferenceBackingParityTests: reflection guard discovering the classifier's surgical
  raw-tag whitelist and requiring a same-typed mirror field (03/U11).

Claude-Session: https://claude.ai/code/session_01Ef2ozxS7QPanGT8uoATbTe

src/Server/ZB.MOM.WW.OtOpcUa.Runtime/OpcUa/OpcUaPublishActor.cs

@@ -592,15 +592,11 @@ public sealed class OpcUaPublishActor : ReceiveActor, IWithTimers
             // (subscriptions are dead anyway) — the guard skips it. AnnounceAddedNodes is Safe-wrapped
             // internally, so a faulting announce can never break the deploy.
             //
-            // KNOWN GAP, and NOT a neutral pre-existing one — the delta work made it matter. Before this
-            // branch, a plan carrying raw adds went through a full RebuildAddressSpace, so every client had to
-            // re-browse anyway and the missing announcement changed nothing observable. Now those adds are
-            // materialised surgically while existing subscriptions stay alive, so an unannounced add is
-            // genuinely INVISIBLE until a client happens to browse again.
-            // Added UNS reference variables ARE announced (their equipment folder is the parent, which is the
-            // realm AnnounceAddedNodes hardcodes). Added RAW containers/tags are still not: the announce is
-            // Uns-only, and a raw parent needs a realm-aware RaiseNodesAddedModelChange call. That is a real
-            // follow-up, not an accepted limitation.
+            // The announce is realm-aware (Gitea #599): UNS parents in the Uns realm, and the parents of
+            // added RAW containers/tags in the Raw realm. It matters because of the delta work — before it, a
+            // plan carrying raw adds went through a full RebuildAddressSpace, so every client re-browsed
+            // anyway; now those adds are materialised surgically while existing subscriptions stay alive, and
+            // an unannounced add would stay invisible until a client happened to browse again.
             if (!outcome.RebuildCalled) _applier.AnnounceAddedNodes(plan);
 
             OtOpcUaTelemetry.OpcUaSinkWrite.Add(1, new KeyValuePair<string, object?>("kind", "rebuild"));