Joseph Doherty 49dfabc141 feat(deploy): coordinator records degraded acks; deployment seals but names degraded nodes (#601) ...

An Applied+Degraded ack keeps NodeDeploymentState.Status = Applied with
FailureReason 'Applied degraded: <reason>' (no enum/migration change). The
deployment still seals (the revision is running; latest-sealed drives drift)
but Deployment.FailureReason names the degraded nodes and the seal logs at
Warning. Recovered from the DB on singleton failover. Old-node acks (no field,
DPS JSON or gRPC) behave exactly as before.

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

2026-10-08 17:32:09 -04:00

..

Client

fix(client): alarm filter selected ActiveState/Id as ONE QualifiedName — every event read inactive

2026-10-08 16:19:27 -04:00

Core

feat(deploy): additive degraded flag on ApplyAck + publish-actor apply outcome reply (#601)

2026-10-08 17:19:57 -04:00

Drivers

Merge b640-640: driver diagnostics surface on /hosts (#640)

2026-10-08 17:13:34 -04:00

Server

feat(deploy): coordinator records degraded acks; deployment seals but names degraded nodes (#601)

2026-10-08 17:32:09 -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