Scope alarm tracking to selected templates and surface endpoint/security state on the dashboard so operators can deploy in large galaxies without drowning clients in irrelevant alarms or guessing what the server is advertising

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

tests/ZB.MOM.WW.LmxOpcUa.Tests/Helpers/OpcUaServerFixture.cs

@@ -150,7 +150,9 @@ namespace ZB.MOM.WW.LmxOpcUa.Tests.Helpers
             string? applicationUri = null,
             string? serverName = null,
             AuthenticationConfiguration? authConfig = null,
-            IUserAuthenticationProvider? authProvider = null)
+            IUserAuthenticationProvider? authProvider = null,
+            bool alarmTrackingEnabled = false,
+            string[]? alarmObjectFilters = null)
         {
             var client = mxClient ?? new FakeMxAccessClient();
             var r = repo ?? new FakeGalaxyRepository
@@ -176,8 +178,18 @@ namespace ZB.MOM.WW.LmxOpcUa.Tests.Helpers
                 builder.WithAuthentication(authConfig);
             if (authProvider != null)
                 builder.WithAuthProvider(authProvider);
+            if (alarmTrackingEnabled)
+                builder.WithAlarmTracking(true);
+            if (alarmObjectFilters != null)
+                builder.WithAlarmFilter(alarmObjectFilters);
 
             return new OpcUaServerFixture(builder, r, client);
         }
+
+        /// <summary>
+        ///     Exposes the node manager currently published by the running fixture so tests can assert
+        ///     filter counters, alarm condition counts, and other runtime telemetry.
+        /// </summary>
+        public ZB.MOM.WW.LmxOpcUa.Host.OpcUa.LmxNodeManager? NodeManager => Service.NodeManagerInstance;
     }
 }