From 484b176cd63525c804fd01d3a665586b7ab5dbc7 Mon Sep 17 00:00:00 2001 From: Joseph Doherty Date: Fri, 9 Oct 2026 08:00:11 -0400 Subject: [PATCH] docs(index): OtOpcUa #663 in-place ApplyDelta re-subscribes data + alarms Claude-Session: https://claude.ai/code/session_01Ef2ozxS7QPanGT8uoATbTe --- .claude/skills/sister-project-history/otopcua.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.claude/skills/sister-project-history/otopcua.md b/.claude/skills/sister-project-history/otopcua.md index 0b3d6b2..a0a18c7 100644 --- a/.claude/skills/sister-project-history/otopcua.md +++ b/.claude/skills/sister-project-history/otopcua.md @@ -154,3 +154,7 @@ AddRoute of the dev Mac (`oee-tagdump-mac`, `10.181.206.245.1.1`) on the two tes so a failed alarm subscribe after an outage is retried. **ScadaBridge-visible:** native conditions keep updating across unrelated deploys and recover after an upstream outage without a driver respawn. No wire-contract change. Pinned by an end-to-end `NativeAlarmFeedSurvivesDeployTests`; not live-gated on the rig. +- **2026-10-09 #663 (closed; OtOpcUa `1355049f`).** #662 review follow-up: an in-place `ApplyDelta` on a Connected driver + called `ReinitializeAsync` but kept the actor's data + alarm handles, which the reinit had invalidated, so the driver + would go silent. Now releases both at the driver, reinitialises, and re-subscribes both. **Latent only** — unreachable + from a deploy since #516 (a DriverConfig change respawns). **ScadaBridge impact: none.**