Joseph Doherty 1badc10445 test(v3-batch4): add Calculation to the driver-probe idempotency key set ...

Pre-existing stale test surfaced by Batch 4's full gate (Batch 2/3 gates were
live-/run and never ran Host.IntegrationTests): Batch 2 registered CalculationProbe
in DriverFactoryBootstrap (9 probes) but AddOtOpcUaDriverProbes_is_idempotent's
AdminUiDriverTypeKeys still listed 8, so distinctTypes(9) != Length(8). Calculation
is a real DriverTypeNames.Calculation pseudo-driver with a probe; add it and refresh
the now-stale *DriverPage.razor comment (that routed flow retired in Batch 2). Not a
Batch-4 code change — a test-correctness fix.

Claude-Session: https://claude.ai/code/session_01LVneM3eh1UtJxEisFXgmox

2026-07-16 13:22:27 -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

feat(v3-batch4-wp4): multi-notifier native alarms (single ReportEvent → raw + equipment notifiers) + teardown symmetry

2026-07-16 12:07:11 -04:00

Drivers

feat(driver-calc): B2-WP7 Calculation driver — IDependencyConsumer + triggers + deploy cycle gate

2026-07-16 04:29:37 -04:00

Server

test(v3-batch4): add Calculation to the driver-probe idempotency key set

2026-07-16 13:22:27 -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