From 2e2ce626657546a97be95ea3eb4a9934fc86c486 Mon Sep 17 00:00:00 2001
From: Joseph Doherty <dohejw01@gmail.com>
Date: Thu, 12 Nov 2026 06:00:30 -0500
Subject: [PATCH] docs(history): correct vd03 Galaxy-ack note (no Galaxy driver
 deployed there)

---
 .claude/skills/sister-project-history/otopcua.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/.claude/skills/sister-project-history/otopcua.md b/.claude/skills/sister-project-history/otopcua.md
index 0d34e59..5a9bf3a 100644
--- a/.claude/skills/sister-project-history/otopcua.md
+++ b/.claude/skills/sister-project-history/otopcua.md
@@ -470,6 +470,6 @@ Owner-authorised WinRM. Preflight: every blocking check passed; snapshot-isolati
 generated on the box; folder swap, ~11 s downtime. First Windows host on OPC UA SDK 2.0.1 (#782). **ScadaBridge-visible
 on this box:** FOCAS `Spindle/S1/MaxRpm` → `BadNodeIdUnknown` (renamed `MotorSpeedPct`, tag not re-pointed); macro
 `parts-count`/`parts-required` decoded at the right offset; spindle `Load` is a real percent (Float64); unreported program
-fields read `BadNoData`. Galaxy acks against the upgraded mxaccessgw `2b13564e` are no longer blocked by the old
-OtOpcUa build. The post-deploy AdminUI deploy (drift = re-serialisation only) is left to the owner. Record:
+fields read `BadNoData`. (The vd03 ConfigDb has no Galaxy driver — 1 FOCAS driver only — so the earlier note that
+its Galaxy acks fail against mxaccessgw `2b13564e` did not apply to this box's deployed config.) The post-deploy AdminUI deploy (drift = re-serialisation only) is left to the owner. Record:
 `docs/deploy/vd03-upgrade-b8b4c18f-to-master.md` §(h).