using ZB.MOM.WW.OtOpcUa.Commons.Protos.MeshTransport.V1; namespace ZB.MOM.WW.OtOpcUa.Commons.Protos; /// /// The single source of truth for which variants /// the cross-mesh command transport actually handles. Both the contract-lock test (which proves /// this list stays in lock-step with the generated oneof) and the oneof↔domain mapper reference /// this array, so adding a fifth command to mesh_transport.proto forces a matching entry /// here or the build/test goes red. /// /// /// Mirrors , and for a sharper reason: a telemetry variant /// nobody handles loses an observation, whereas a command variant nobody handles loses a /// deployment, a driver restart or an alarm acknowledgement — silently, since the sender's ack /// only ever meant "received". /// public static class MeshTransportProtoContract { /// /// Exactly the four cross-mesh command oneof cases mirrored from the domain records: /// DispatchDeployment / RestartDriver / ReconnectDriver / AlarmCommand. The fifth message on /// this contract, ApplyAckMessage, travels the opposite direction on its own RPC and is /// not a oneof member, so it is deliberately absent from this list. /// public static readonly CommandEnvelope.CommandOneofCase[] HandledCases = [ CommandEnvelope.CommandOneofCase.DispatchDeployment, CommandEnvelope.CommandOneofCase.RestartDriver, CommandEnvelope.CommandOneofCase.ReconnectDriver, CommandEnvelope.CommandOneofCase.AlarmCommand, ]; }