Joseph Doherty edd01fcc34 fix(runtime): a changed alarm set re-subscribes instead of latching (review F1) ...

The alarm subscribe gated on 'a handle exists', which is correct for an idempotent
re-push and wrong for a deploy that widens/narrows the set. Combined with the
spawn-time desired set, a respawning deploy could latch the PREVIOUS revision's
alarm refs for the life of the connection; sourceNodeIds-filtering drivers
(OpcUaClient/AbCip/Focas) would never deliver the new alarm.

Seen RED: LastSubscribedAlarmRefs stayed [alarmX] after a deploy widening to
[alarmX, alarmY].

2026-08-20 10:24:52 -04:00

..

Client

ci(v2): whole-solution unit leg + fail-on-skip gate + deflake CLI sleeps (arch-review 07/S-1,S-2,S-4)

2026-07-08 17:58:42 -04:00

Core

fix(acl): browse transit reaches the shared root folder (narrow Browse grants were unreachable)

2026-08-18 09:45:04 -04:00

Drivers

fix(s7): worst-severity error message + OCE flushes recorded pass evidence (review round)

2026-08-18 07:10:51 -04:00

Server

fix(runtime): a changed alarm set re-subscribes instead of latching (review F1)

2026-08-20 10:24:52 -04:00

Tooling/ZB.MOM.WW.OtOpcUa.Analyzers.Tests

fix(archreview #10): wire CapabilityInvoker into prod dispatch via a Polly-free seam

2026-07-08 21:33:16 -04:00