docs(index): vd03 OtOpcUa #793 close-out — MaxRpm re-pointed (9adc5590), ACL off, no ScadaBridge OPC UA link

.claude/skills/sister-project-history/otopcua.md

@@ -468,8 +468,9 @@ AddRoute of the dev Mac (`oee-tagdump-mac`, `10.181.206.245.1.1`) on the two tes
 ### 2026-11-12 — wonder-app-vd03 upgraded `b8b4c18f` → master `5fb4b4db` (#793)
 Owner-authorised WinRM. Preflight: every blocking check passed; snapshot-isolation migration applied; `Security__ApiKeys__Pepper`
 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
+on this box:** FOCAS `Spindle/S1/MaxRpm` → `BadNodeIdUnknown` (renamed `MotorSpeedPct`; the vd03 tag was re-pointed + renamed and shipped in deployment `9adc5590`, reads Good); macro
 `parts-count`/`parts-required` decoded at the right offset; spindle `Load` is a real percent (Float64); unreported program
 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.) Post-deploy AdminUI deploy done 11:02 UTC (owner-authorised): deployment `e4b4824a` Sealed, `/fleet` node **Applied** (not degraded), no 3952; the drift was master's composer re-serialising the 2026-08-05 config. New benign log lines: SDK 2 LDS `RegisterServer` retries (`BadServiceUnsupported`), mesh-PSK `ot-mesh-psk-dev` absent (DPS transport, unused). Record:
 `docs/deploy/vd03-upgrade-b8b4c18f-to-master.md` §(h).
+**Close-out (same day):** `Security:Acl:Enabled` is off on vd03; vd03 ScadaBridge has **no** OPC UA data connection to OtOpcUa (only `MxGateway` → `localhost:5120`), so none of the FOCAS changes reach ScadaBridge there; rollback of `data\` is compatible (LocalDb 0.3.4 both sides, additive `alarm_condition_comment` table, 0 scripted-alarm rows). Record §(h) close-out bullet.

deployment.md

@@ -472,7 +472,7 @@ wonder-sql-vd03; `EnableSnapshotIsolation` migration applied; `Security__ApiKeys
 `E:\ApiInstall\OtOpcUa.bak.20261112-pre-5fb4b4db`, data backup under `E:\ApiInstall\OtOpcUa-backups\`, rollback
 script `E:\ApiInstall\_stage-otopcua-5fb4b4db\rollback.ps1`, ConfigDb backup
 `OtOpcUaConfig-pre-20261112-otopcua-5fb4b4db.bak` (instance default backup dir). Post-deploy AdminUI deploy
-`e4b4824a` → **Applied**; health 200 ×3, ServiceLevel 255. Full record: OtOpcUa
+`e4b4824a` → **Applied**; then `9adc5590` re-pointed the FOCAS `MaxRpm` tag to `MotorSpeedPct`; health 200 ×3, ServiceLevel 255. Full record: OtOpcUa
 `docs/deploy/vd03-upgrade-b8b4c18f-to-master.md` §(h). QA vq03/vq04 are unchanged from the 2026-09-10 round.
 
 Neither install is a scripted in-repo flow — the operational procedures live in ScadaBridge