v2 release-readiness — blocker #3 closed; all three code-path blockers shut
Phase 6.3 Streams A + C core shipped (PRs #98-99):
- RedundancyCoordinator + ClusterTopologyLoader read the shared config DB +
enforce the Phase 6.3 invariants (1-2 nodes, unique ApplicationUri, ≤1
Primary in Warm/Hot). Startup fails fast on violation.
- RedundancyStatePublisher orchestrates topology + apply lease + recovery
state + peer reachability through ServiceLevelCalculator. Edge-triggered
OnStateChanged + OnServerUriArrayChanged events the OPC UA variable-node
layer subscribes to.
Doc updates:
- Top status flips from NOT YET RELEASE-READY → RELEASE-READY (code-path).
Remaining work is manual (client interop matrix, deployment signoff,
OPC UA CTT pass) + hardening follow-ups that don't block v2 GA ship.
- Release-blocker #3 section struck through + CLOSED with PR links.
Remaining Phase 6.3 surfaces (peer-probe HostedServices, OPC UA
variable-node binding, sp_PublishGeneration lease wrap, client interop)
explicitly listed as hardening follow-ups.
- Change log: new dated entry.
All three release blockers identified at the capstone are closed:
- #1 Phase 6.2 dispatch wiring → PR #94 (2026-04-19)
- #2 Phase 6.1 Stream D wiring → PR #96 (2026-04-19)
- #3 Phase 6.3 Streams A/C core → PRs #98-99 (2026-04-19)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
e71f44603c