task-galaxy-e2e branch — non-FOCAS work-in-progress snapshot

Catch-all commit for pending work on the task-galaxy-e2e branch that
wasn't part of the FOCAS migration. Grouping by topic so future per-topic
commits can be cherry-picked if needed.

TwinCAT
- src/.../Driver.TwinCAT/AdsTwinCATClient.cs + TwinCATDriverFactoryExtensions.cs:
  factory-registration extensions + ADS client refinements.
- src/.../Driver.TwinCAT.Cli/Commands/BrowseCommand.cs: new browse command
  for the TwinCAT test-client CLI.
- tests/.../Driver.TwinCAT.IntegrationTests/TwinCAT3SmokeTests.cs + TwinCatProject/:
  fixture scaffold with a minimal POU + README pointing at the TCBSD/ESXi
  VM for e2e.
- docs/Driver.TwinCAT.Cli.md + docs/drivers/TwinCAT-Test-Fixture.md:
  documentation for the above.
- docs/v3/twincat-backlog.md: forward-looking backlog seed.

Admin UI + fleet status
- src/.../Admin/Components/Pages/Clusters/DriversTab.razor + Hosts.razor:
  UI refresh for fleet-status rendering.
- src/.../Admin/Hubs/FleetStatusHub.cs + FleetStatusPoller.cs +
  Admin/Program.cs: SignalR hub + poller plumbing for live fleet data.
- tests/.../Admin.Tests/FleetStatusPollerTests.cs: poller coverage.

Server + redundancy runtime (Phase 6.3 follow-ups)
- src/.../Server/Hosting/RedundancyPublisherHostedService.cs: HostedService
  that owns the RedundancyStatePublisher lifecycle + wires peer reachability.
- src/.../Server/Redundancy/ServerRedundancyNodeWriter.cs: OPC UA
  variable-node writer binding ServiceLevel + ServerUriArray to the
  publisher's events.
- src/.../Server/Program.cs + Server.csproj: hosted-service registration.
- tests/.../Server.Tests/ServerRedundancyNodeWriterTests.cs +
  Server.Tests.csproj: coverage for the above.

Configuration
- src/.../Configuration/Validation/DraftValidator.cs +
  tests/.../Configuration.Tests/DraftValidatorTests.cs: draft-validation
  refinements.

E2E scripts (shared infrastructure)
- scripts/e2e/README.md + _common.ps1 + test-all.ps1: shared helpers + the
  all-drivers test-all runner.
- scripts/e2e/test-opcuaclient.ps1: OPC UA Client e2e runner.

Docs
- docs/v2/implementation/phase-6-{1,2,3,4}*.md + exit-gate-phase-{3,7}.md:
  phase-gate + implementation doc updates.
- docs/v2/plan.md: top-level plan refresh.
- docs/v2/redundancy-interop-playbook.md: client interop playbook for the
  Phase 6.3 redundancy-runtime work.

Two orphan FOCAS docs remain on disk but deliberately unstaged —
docs/v2/focas-deployment.md and docs/v2/implementation/focas-simulator-plan.md
describe the now-retired Tier-C topology and should either be rewritten
or deleted in a follow-up.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

scripts/e2e/README.md

@@ -53,27 +53,47 @@ read-only tag.
 
 ## Status
 
-Stages 1 + 2 (driver-side probe + loopback) are verified end-to-end
-against the pymodbus / ab_server / python-snap7 fixtures. Stages 3-5
-(anything crossing the OtOpcUa server) are **blocked** on server-side
-driver factory wiring:
+All seven driver factories are registered in
+`src/ZB.MOM.WW.OtOpcUa.Server/Program.cs` — Galaxy, FOCAS, Modbus,
+AB CIP, AB Legacy, S7, TwinCAT. `DriverInstanceBootstrapper` can
+materialise any `DriverType` row from the central Config DB into a
+live driver. The factory-wiring block that originally gated stages
+3-5 is closed.
 
-- `src/ZB.MOM.WW.OtOpcUa.Server/Program.cs` only registers Galaxy +
-  FOCAS factories. `DriverInstanceBootstrapper` skips any `DriverType`
-  without a registered factory — so Modbus / AB CIP / AB Legacy / S7 /
-  TwinCAT rows in the Config DB are silently no-op'd even when the seed
-  is perfect.
-- No Config DB seed script exists for non-Galaxy drivers; Admin UI is
-  currently the only path to author one.
+Live-boot verification:
 
-Tracking: **#209** (umbrella) → #210 (Modbus), #211 (AB CIP), #212 (S7),
-#213 (AB Legacy, also hardware-gated — #222). Each child issue lists
-the factory class to write + the seed SQL shape + the verification
-command.
+- **Galaxy** — 7/7 stages (read / write / subscribe / alarms / history)
+  against a real Galaxy + `OtOpcUaGalaxyHost` on this dev box.
+- **AB CIP, S7** — 5/5 stages each under task #220 against the
+  `ab_server` + `python-snap7` fixtures.
+- **AB Legacy** — 5/5 stages under task #222 against `ab_server` SLC500
+  / MicroLogix / PLC-5 profiles (requires the `cip-path /1,0` workaround
+  for the Docker fixture).
+- **Modbus** — 5/5 stages against the `pymodbus` + dl205 profile,
+  including HR[200] scratch register + per-protocol bidirectional +
+  subscribe-sees-change stages.
+- **TwinCAT** — factory registered; driver features validated against the
+  TCBSD VM virtual-PLC fixture (FreeBSD + TwinCAT/BSD runtime on ESXi —
+  bypasses the Hyper-V/RTIME conflict that blocks XAR on the dev box).
+  `TWINCAT_TRUST_WIRE=1` is still required to run the script —
+  false-pass-prevention belt, not an "unverified" flag.
+- **FOCAS** — factory registered; gated by `FOCAS_TRUST_WIRE=1` pending
+  the lab-rig CNC (task #222 follow-up).
+- **OpcUaClient (gateway)** — eight-stage script (`test-opcuaclient.ps1`)
+  covers probe / remote read / forward bridge / subscribe / reverse
+  bridge / browse mirror / alarm / history against the opc-plc Docker
+  fixture at `opc.tcp://localhost:50000`. Reverse-bridge / alarm /
+  history stages are opt-in per the parameter docs (opc-plc's default
+  image has no writable nodes and does not historize).
 
-Until those ship, stages 3-5 will fail with "read failed" (nothing
-published at that NodeId) and `[FAIL]` the suite even on a running
-server.
+Remaining work is **per-protocol seed authoring**: each dev fills in
+the NodeIds their server publishes under `e2e-config.json` (sidecar
+is `.gitignore`-d; see `e2e-config.sample.json` for the shape). Admin
+UI remains the supported path for authoring the matching driver
+instance rows in the Config DB.
+
+Tracking: umbrella #209 is closed; remaining TwinCAT / FOCAS work
+tracks under their hardware-fixture tasks (#221 / #222).
 
 ## Prereqs
 
@@ -85,7 +105,9 @@ server.
    for the simulator matrix — pymodbus / ab_server / python-snap7 /
    opc-plc cover Modbus / AB / S7 / OPC UA Client. FOCAS and TwinCAT
    have no public simulator; they are gated with env-var skip flags
-   below.
+   below. For OpcUaClient, `docker compose -f
+   tests/ZB.MOM.WW.OtOpcUa.Driver.OpcUaClient.IntegrationTests/Docker/
+   docker-compose.yml up -d` brings up `opc-plc` on port 50000.
 3. **PowerShell 7+**. The runner uses null-coalescing + `Set-StrictMode`;
    the Windows-PowerShell-5.1 shell will not parse `test-all.ps1`.
 4. **.NET 10 SDK**. Each script either runs `dotnet run --project
@@ -136,7 +158,8 @@ section to skip it.
 | Galaxy | — | **PASS** (requires OtOpcUaGalaxyHost + a live Galaxy; 7 stages including alarms + history) |
 | S7 | — | **PASS** (python-snap7 fixture) |
 | FOCAS | `FOCAS_TRUST_WIRE=1` | **SKIP** (no public simulator — task #222 lab rig) |
-| TwinCAT | `TWINCAT_TRUST_WIRE=1` | **SKIP** (needs XAR or standalone Router — task #221) |
+| TwinCAT | `TWINCAT_TRUST_WIRE=1` | **SKIP** by default; features **validated** against the TCBSD VM fixture — set the env var to run |
+| OpcUaClient | — | **PASS** stages 1-4 + browse (opc-plc Docker fixture); stages 5/7/8 are opt-in (require writable / alarm / historizing upstream) |
 | Phase 7 | — | **PASS** if the Modbus instance seeds a `VT_DoubledHR100` virtual tag + `AlarmHigh` scripted alarm |
 
 Set the `*_TRUST_WIRE` env vars to `1` when you've pointed the script at