c6edef0efb
v2-ci / build (push) Failing after 37s
v2-ci / unit-tests (tests/Core/ZB.MOM.WW.OtOpcUa.Cluster.Tests) (push) Has been skipped
v2-ci / unit-tests (tests/Server/ZB.MOM.WW.OtOpcUa.ControlPlane.Tests) (push) Has been skipped
v2-ci / unit-tests (tests/Server/ZB.MOM.WW.OtOpcUa.OpcUaServer.Tests) (push) Has been skipped
v2-ci / unit-tests (tests/Server/ZB.MOM.WW.OtOpcUa.Runtime.Tests) (push) Has been skipped
v2-ci / unit-tests (tests/Server/ZB.MOM.WW.OtOpcUa.Security.Tests) (push) Has been skipped
v2-ci / integration (tests/Server/ZB.MOM.WW.OtOpcUa.Host.IntegrationTests) (push) Has been skipped
v2-ci / integration (tests/Server/ZB.MOM.WW.OtOpcUa.OpcUaServer.IntegrationTests) (push) Has been skipped
Add a post-publish Step 4b that fails the refresh if the sidecar deploy folder is missing any load-bearing file (System.Memory.dll, MessagePack.dll, the .exe, or the net48 binding-redirect .exe.config). A partial/stale deploy that bypasses `dotnet publish` drops System.Memory.dll, so the sidecar JIT-load-faults in PipeServer.RunOneConnectionAsync (FileNotFoundException 'System.Memory, Version=4.0.1.2') and NSSM crash-loops it (exit 2 every ~2 min). Catching this at publish time beats discovering it as a production crash-loop. Guarded by -WhatIf; throws before any service is started.