docs/chore: flag uns-loader README stale + add historian SQL reference; gitignore .claude tooling + local VPN notes

otopcua-uns-loader/README.md

@@ -1,5 +1,16 @@
 # otopcua-uns-loader
 
+> ⚠️ **STALE w.r.t. OtOpcUa's current model (as of ~2026-06-12).** OtOpcUa retired the
+> `SystemPlatform` namespace kind, the galaxy **mirror**, alias tags, and the namespace-kind
+> driver rule: **Galaxy is now a standard `Equipment`-kind driver**, and a galaxy point is an
+> ordinary equipment `Tag` bound to `GalaxyMxGateway` with `TagConfig.FullName`. The
+> SystemPlatform-mirror `populate` and the VirtualTag+Script `populate-equipment` paths below no
+> longer match the server. Also note: a **headless deploy now exists** — `POST
+> http://localhost:9200/api/deployments` with header `X-Api-Key: docker-dev-deploy-key` (the "no
+> SQL/REST/CLI trigger" claim below is outdated). To drive the new model this tool would need
+> reworking to emit equipment `Tag` rows directly. `galaxy-hierarchy.json` (the raw Galaxy DEV
+> pull) is still a valid source. Background: `OtOpcUa/docs/plans/2026-06-12-galaxy-standard-driver-design.md`.
+
 A **reloadable** populate-and-verify tool for the OtOpcUa galaxy Unified Namespace.
 Recreates a UNS load grounded in the real AVEVA Galaxy **DEV** hierarchy (the 40
 `TestMachine` instances) and verifies it streams **live values** on OPC UA — so