fix(deploy): wire native-alarm-source capability validation into flattening pipeline (#22)

FlatteningPipeline loaded data connections but never passed the alarm-capable
connection set to SemanticValidator, so the native-alarm-source capability check
(built but inert) never ran — a source bound to a non-alarm-capable connection
deployed silently. Compute the capable set (IAlarmSubscribableConnection: OPC UA
+ MxGateway) and thread it through ValidationService to SemanticValidator.

src/ZB.MOM.WW.ScadaBridge.Commons/Interfaces/Protocol/AlarmCapableProtocols.cs

@@ -0,0 +1,31 @@
+namespace ZB.MOM.WW.ScadaBridge.Commons.Interfaces.Protocol;
+
+/// <summary>
+/// Single source of truth for which data-connection protocol strings produce an
+/// adapter that implements <see cref="IAlarmSubscribableConnection"/> (i.e. can
+/// mirror native alarms).
+///
+/// The set MUST stay in sync with the protocols registered against an
+/// alarm-subscribable adapter in the DCL <c>DataConnectionFactory</c>: today the
+/// "OpcUa" adapter (<c>OpcUaDataConnection</c>) and the "MxGateway" adapter
+/// (<c>MxGatewayDataConnection</c>) both implement
+/// <see cref="IAlarmSubscribableConnection"/>. The runtime decision is made in
+/// <c>DataConnectionActor</c> via <c>_adapter is IAlarmSubscribableConnection</c>;
+/// this central-side helper lets the deploy pipeline and Central UI gate
+/// native-alarm-source bindings against the same notion without instantiating an
+/// adapter. Adding a new alarm-capable protocol = register the adapter in the
+/// factory AND add its protocol string here.
+/// </summary>
+public static class AlarmCapableProtocols
+{
+    /// <summary>
+    /// Determines whether a data connection's protocol string resolves to an
+    /// alarm-capable adapter (one implementing <see cref="IAlarmSubscribableConnection"/>).
+    /// Case-insensitive; <c>null</c>/blank is not alarm-capable.
+    /// </summary>
+    /// <param name="protocol">The data connection protocol string (e.g. "OpcUa").</param>
+    /// <returns><c>true</c> when the protocol's adapter can subscribe native alarms; otherwise <c>false</c>.</returns>
+    public static bool IsAlarmCapable(string? protocol) =>
+        string.Equals(protocol, "OpcUa", StringComparison.OrdinalIgnoreCase)
+        || string.Equals(protocol, "MxGateway", StringComparison.OrdinalIgnoreCase);
+}

src/ZB.MOM.WW.ScadaBridge.DeploymentManager/FlatteningPipeline.cs

@@ -1,4 +1,5 @@
 using ZB.MOM.WW.ScadaBridge.Commons.Entities.Sites;
+using ZB.MOM.WW.ScadaBridge.Commons.Interfaces.Protocol;
 using ZB.MOM.WW.ScadaBridge.Commons.Interfaces.Repositories;
 using ZB.MOM.WW.ScadaBridge.Commons.Types;
 using ZB.MOM.WW.ScadaBridge.Commons.Types.Flattening;
@@ -111,8 +112,18 @@ public class FlatteningPipeline : IFlatteningPipeline
             ReturnDefinition = s.ReturnDefinition
         }).ToList();
 
+        // Compute the alarm-capable connection-name set so the semantic validator
+        // can gate native-alarm-source bindings. "Alarm-capable" matches the DCL
+        // runtime decision (DataConnectionActor: _adapter is IAlarmSubscribableConnection),
+        // mapped from the protocol string via the shared AlarmCapableProtocols helper.
+        var alarmCapableConnectionNames = dataConnections.Values
+            .Where(c => AlarmCapableProtocols.IsAlarmCapable(c.Protocol))
+            .Select(c => c.Name)
+            .ToHashSet(StringComparer.Ordinal);
+
         // Validate
-        var validation = _validationService.Validate(config, resolvedSharedScripts);
+        var validation = _validationService.Validate(
+            config, resolvedSharedScripts, alarmCapableConnectionNames);
 
         // Compute revision hash
         var hash = _revisionHashService.ComputeHash(config);

src/ZB.MOM.WW.ScadaBridge.TemplateEngine/Validation/ValidationService.cs

@@ -45,8 +45,18 @@ public class ValidationService
     /// </summary>
     /// <param name="configuration">The flattened configuration to validate.</param>
     /// <param name="sharedScripts">Optional list of shared scripts for validation context.</param>
+    /// <param name="alarmCapableConnectionNames">
+    /// Optional set of site data-connection names whose protocol resolves to an
+    /// alarm-capable adapter (see
+    /// <see cref="Commons.Interfaces.Protocol.AlarmCapableProtocols"/>). When supplied,
+    /// the semantic validator gates every native-alarm-source binding against it.
+    /// <c>null</c> skips the capability check (its absence makes the check inert).
+    /// </param>
     /// <returns>A merged <see cref="ValidationResult"/> aggregating all pipeline stage outcomes.</returns>
-    public ValidationResult Validate(FlattenedConfiguration configuration, IReadOnlyList<ResolvedScript>? sharedScripts = null)
+    public ValidationResult Validate(
+        FlattenedConfiguration configuration,
+        IReadOnlyList<ResolvedScript>? sharedScripts = null,
+        IReadOnlySet<string>? alarmCapableConnectionNames = null)
     {
         ArgumentNullException.ThrowIfNull(configuration);
 
@@ -59,7 +69,7 @@ public class ValidationService
             ValidateScriptTriggerReferences(configuration),
             ValidateExpressionTriggers(configuration),
             ValidateConnectionBindingCompleteness(configuration),
-            _semanticValidator.Validate(configuration, sharedScripts)
+            _semanticValidator.Validate(configuration, sharedScripts, alarmCapableConnectionNames)
         };
 
         return ValidationResult.Merge(results.ToArray());