Claude-Session: https://claude.ai/code/session_01GT67ACmpMR7b9LGRPLijMi
This commit is contained in:
@@ -4,6 +4,8 @@
|
||||
|
||||
- **2026-10-13 #36 runtime regression proof refreshed.** Rebuilt HandshakeResetEchoTests passed all three cases with local fakes, terminal exit0; an earlier no-build attempt matched no tests and is excluded from evidence. Tracker now distinguishes implemented runtime b623fdb0 from remaining QA/prod database-owned script rollout (deployment register row119, scripts13/14/36 and15/16/25/26/37/38). No database writes, deployments or fresh live rig claims.
|
||||
|
||||
- **2026-11-13 deployed `8e32f353` to wonder-app-vd03 (DEV) and enabled the audit hash chain** (was `424db155`; owner go on #107). 37 commits, no migration (64). Build: clean worktree, self-contained win-x64, zip SHA-256 `0cf06cf5…7fdebc`, LocalDb 0.3.8. WinRM swap 07:13–07:14 EST, site data path ~45 s, central API ~25 s; `sc failureflag 1` on both services (restart actions existed, but non-crash failures were FALSE, so a #132 exit 75 would have left the node stopped). Env block digest-identical before/after. **#131 applied** (`apply.sh apply 131`, SBTEST01/02 deployments 95/96; verify groups C+D 13/13 on the old binary and again after; C13 skipped because SAPID 103559 routes to Z28061) — #131 closed. Gates: health 200 ×4, MxGateway Connected 398/412 = baseline, Z28062 144 Good = baseline, AuditLog writing, Overview Up. **Hash chain:** backfill 843 → `unknown`, then `AuditLog__HashChain__Enabled=true` in the Central service env (ChainBacklog unset, head export off, single login), Central-only restart; one anchor (2026-11 `ChainSeq 0`, cutoff 2026-11-13T12:16:53.114Z), 0 pre-cutoff rows chained, `verify-chain 2026-11` Intact with 507 pre-cutoff rows, 2026-10 NotChained (667). Backup `ScadaBridge_pre-8e32f353_20261113T071302.bak`; rollback scripts in `E:\ApiInstall\_stage-sb-8e32f353\`. Record `docs/deployment/deployment-records/2026-11-13-wonder-app-vd03-8e32f353.md` (`581e25ca`). QA not deployed.
|
||||
|
||||
- **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.
|
||||
|
||||
Reference in New Issue
Block a user