docs(scadabridge-history): DCL OPC UA SDK 1.5.378.106 -> 1.5.378.182 (e36cd605), wire-compat vs SDK 1.5 + 2.0.1 servers; 2.0.x deferred (ScadaBridge#125)

Claude-Session: https://claude.ai/code/session_01GT67ACmpMR7b9LGRPLijMi
This commit is contained in:
Joseph Doherty
2026-11-12 14:09:10 -05:00
parent ccfcc7c3d2
commit e573ee40d5
@@ -7,3 +7,13 @@
- **2026-11-11 deployed `424db155` to wonder-app-vd03 (DEV)** (was `0e540291`). Owner-approved WinRM deploy. Migrations 58→64 (`AddNativeAlarmSourceMesReportable`, `PrefixSearchIndexes`, `AddAuditLogHashChain`, `AddConfigGraphRowVersions`, `FlipAuditLogClusteredKey`, `AuditMaintenanceGrants`) applied by script with central + site stopped; #111 DEV sizing: 2,394 rows / 8 MB flip in ~1.5 s. **The plain `dotnet ef migrations script --idempotent` output fails (Msg 207 `ChainSeq`: column added and indexed in one batch)** — the deployed script adds `GO` per guarded block + `XACT_ABORT`; forward/rollback rehearsed on a restored copy of the vd03 DB. Downtime ~50 s; verify OK. Backup `ScadaBridge-backups\ScadaBridge_pre-424db155_20261111T164219.bak`. QA not deployed.
- **2026-11-12 #129 alarm Severity runs one direction (higher = more urgent), main `dd4f1c2a`.** MxGateway native alarms and computed `PriorityLevel` now band AVEVA-style priority onto `AlarmConditionState.Severity` with OtOpcUa's `GalaxyAlarmPriority` table (lmxopcua#887): 1–250→1000, 251–500→750, 501–750→500, 751–999→250, ≤0→1000, >999→250 (`AlarmPriorityBands`). OPC UA rows are unchanged. The raw number (= pre-#129 Severity) is kept on new `AlarmConditionState.Priority`, `ScriptAlarm.Priority` and `AlarmStateChanged.Priority`. There is no proto change: central derives Severity from the wire `priority` by kind, and pre-#129 `native_alarm_state` rows are upgraded on rehydrate. The native MES 900–999 band and the MES API `Severity`/`MinSeverity`/`MaxSeverity` key off `Priority`, so they select the same alarms as before. The rig seed scripts were switched; **deployed MES scripts (CvdReactor, vd03 SBTEST01/02) must switch `a.Severity`→`a.Priority` in the same deploy: deploy gate ScadaBridge#131.** **Visible flip:** Alarm Summary worst/filter/sort and the Sev column now rank AVEVA priority 1 highest. A computed raise logs `Error` at priority 1–500 (was raw ≥700). Tests (Release): Commons 977, DCL 549, Communication 834, SiteRuntime 1055, CentralUI 1545, all green; a mutation revert turned 62 red. Not deployed.
- **2026-11-12 OPC Foundation SDK 1.5.378.106 → 1.5.378.182 (`main` `e36cd605`, ScadaBridge#125 ask 2, owner option B; not deployed).**
- Client (DCL) and the test-only Server move in lockstep. No source changes, no API breaks.
- Release build has 0 warnings. DCL tests pass 536/536.
- **Wire-compat re-run** with the bumped client, using the lmxopcua harness (`438484fd`, run at master `2e9cccbd`), ACL off:
- The matrix passes 11/11 in None, Sign and SignAndEncrypt, against both the SDK 1.5 baseline `83ed880e` and the SDK **2.0.1** master `a28adba2`.
- All 8 trust controls fail closed (0x80130000 and 0x801A0000).
- Failover passes 8/8 legs, with the same timings as on the old client.
- **Operational note:** since .156, a CA-issued OPC UA server cert that the DCL trusts needs an issuer with `keyCertSign`. SDK self-signed certs are unaffected.
- **2.0.x is deferred** until lmxopcua#799 and #801 close. #125 stays open to track it.