Remove native-launcher fallbacks for the four Dockerized fixtures — Docker is the only supported path for Modbus / S7 / AB CIP / OpcUaClient integration. Native paths stay in place only where Docker isn't compatible (Galaxy: MXAccess COM + Windows-only; TwinCAT: Beckhoff runtime vs Hyper-V; FOCAS: closed-source Fanuc Fwlib32.dll; AB Legacy: PCCC has no OSS simulator). Simplifies the fixture landscape + removes the "which path do I run" ambiguity; removes two full native-launcher directories + the AB CIP native-spawn path; removes the parallel profile-as-CLI-arg-builder code from AbServerFixture.

Modbus — deletes tests/.../Modbus.IntegrationTests/Pymodbus/ (serve.ps1, standard.json, dl205.json, mitsubishi.json, s7_1500.json, README.md). Profile JSONs live only under Docker/profiles/ now. Docker/README.md loses its "Native-Python fallback" section; docs/drivers/Modbus-Test-Fixture.md "What the fixture is" bullet flipped from "primary launcher is Docker, native fallback under Pymodbus/" to "Docker is the only supported launch path".

S7 — deletes tests/.../S7.IntegrationTests/PythonSnap7/ (server.py, s7_1500.json, serve.ps1, README.md). Docker/README.md loses "Native-Python fallback"; docs/drivers/S7-Test-Fixture.md updated to match.

AB CIP — the biggest simplification because the native-binary spawn had the most code. AbServerFixture.cs rewrites: drops Process management (no more Process _proc + Kill/WaitForExit), drops LocateBinary() PATH lookup, drops the IAsyncLifetime initialize-spawns-server behavior. Fixture is now a thin TCP probe against localhost:44818 (or AB_SERVER_ENDPOINT override) — same shape as Snap7ServerFixture / ModbusSimulatorFixture / OpcPlcFixture. IsServerAvailable() simplifies to a single 500 ms probe. AbServerProfile.cs drops AbServerPlcArg + SeedTags + BuildCliArgs + ToCliSpec + the entire AbServerSeedTag record — the compose file is the canonical source of truth for which tags + which --plc mode each family gets; the profile record now carries just Family + ComposeProfile (matches the docker-compose service key) + Notes. KnownProfiles.ForFamily + .All stay for tests that iterate families. AbServerProfileTests.cs rewrites to match: drops BuildCliArgs_* + ToCliSpec_* + SeedTags_* tests; keeps the family-coverage contract tests + verifies the ComposeProfile strings match compose-file service names (a typo in either surfaces as a unit-test failure, not a silent "wrong family booted" at runtime). Docker/README.md loses "Native-binary fallback" section; docs/drivers/AbServer-Test-Fixture.md "What the fixture is" flipped to Docker-only with clearer skip rules.

dev-environment.md §Docker fixtures — the "Native fallbacks" subsection goes away; replaced with a one-line note that Docker is the only supported path for these four fixtures + a fresh clone needs Docker Desktop and nothing else.

Verified: whole-solution build 0 errors, AB CIP profile unit tests 6/6, AB CIP Docker smoke 4/4 (all family theory rows), S7 Docker smoke 3/3. Container lifecycle clean. The deleted native code surface was already redundant — every fixture the native paths served is now covered by Docker; keeping them invited drift between the two paths (the original AB CIP native profile had three undetected bugs per the #162 commit message: case-sensitive --plc, bracket tag notation, --path=1,0 requirement — noise the Docker path now avoids by never running the buggy code).

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

docs/drivers/AbServer-Test-Fixture.md

@@ -13,24 +13,22 @@ quirk. UDT / alarm / quirk behavior is verified only by unit tests with
 - **Binary**: `ab_server` — a C program in libplctag's
   `src/tools/ab_server/` ([libplctag/libplctag](https://github.com/libplctag/libplctag),
   MIT).
-- **Primary launcher**: Docker. `Docker/Dockerfile` multi-stage-builds
-  `ab_server` from source against a pinned libplctag tag + copies the
-  binary into a slim runtime image. `Docker/docker-compose.yml` has
-  per-family services (`controllogix` / `compactlogix` / `micro800` /
-  `guardlogix`); all bind `:44818`.
-- **Lifecycle**: `AbServerFixture` probes `127.0.0.1:44818` at collection
-  init. When a Docker container is running (or `AB_SERVER_ENDPOINT` is
-  set) the fixture skips its legacy spawn path + the tests dial the
-  running container. When neither is present, it falls back to the
-  pre-Docker path of resolving `ab_server` off `PATH` + spawning it.
+- **Launcher**: Docker (only supported path). `Docker/Dockerfile`
+  multi-stage-builds `ab_server` from source against a pinned libplctag
+  tag + copies the binary into a slim runtime image.
+  `Docker/docker-compose.yml` has per-family services (`controllogix`
+  / `compactlogix` / `micro800` / `guardlogix`); all bind `:44818`.
+- **Lifecycle**: `AbServerFixture` TCP-probes `127.0.0.1:44818` at
+  collection init + records a skip reason when unreachable. Tests skip
+  via `[AbServerFact]` / `[AbServerTheory]` which check the same probe.
 - **Profiles**: `KnownProfiles.{ControlLogix, CompactLogix, Micro800, GuardLogix}`
-  in `AbServerProfile.cs`. Each composes a CLI arg list + seed-tag set; the
-  `Docker/docker-compose.yml` `command:` entries mirror those args 1:1.
+  in `AbServerProfile.cs` — thin Family + ComposeProfile + Notes records;
+  the compose file is the canonical source of truth for which tags get
+  seeded + which `--plc` mode the simulator boots in.
 - **Tests**: one smoke, `AbCipReadSmokeTests.Driver_reads_seeded_DInt_from_ab_server`,
   parametrized over all four profiles via `[AbServerTheory]` + `[MemberData]`.
-- **Skip rules** via `[AbServerFact]` / `[AbServerTheory]`: accept a live
-  listener on `:44818` (Docker), an `AB_SERVER_ENDPOINT` override, or the
-  native binary on `PATH`; skip otherwise.
+- **Endpoint override**: `AB_SERVER_ENDPOINT=host:port` points the
+  fixture at a real PLC instead of the local container.
 
 ## What it actually covers
 

docs/drivers/Modbus-Test-Fixture.md

@@ -11,18 +11,16 @@ shaped (neither is a Modbus-side concept).
 
 ## What the fixture is
 
-- **Simulator**: `pymodbus` (Python, BSD) — primary launcher is a pinned
-  Docker image at
+- **Simulator**: `pymodbus` (Python, BSD) launched as a pinned Docker
+  container at
   `tests/ZB.MOM.WW.OtOpcUa.Driver.Modbus.IntegrationTests/Docker/`.
-  Native-Python fallback under `Pymodbus/` is kept for contributors who
-  don't want Docker.
+  Docker is the only supported launch path.
 - **Lifecycle**: `ModbusSimulatorFixture` (collection-scoped) TCP-probes
   `localhost:5020` on first use. `MODBUS_SIM_ENDPOINT` env var overrides the
   endpoint so the same suite can target a real PLC.
 - **Profiles**: `DL205Profile`, `MitsubishiProfile`, `S7_1500Profile` —
   each composes device-specific register-format + quirk-seed JSON for pymodbus.
-  Profile JSONs are canonical under `Docker/profiles/`; `Pymodbus/` carries
-  a copy for the native fallback.
+  Profile JSONs live under `Docker/profiles/` and are baked into the image.
 - **Compose services**: one per profile (`standard` / `dl205` /
   `mitsubishi` / `s7_1500`); only one binds `:5020` at a time.
 - **Tests skip** via `Assert.Skip(sim.SkipReason)` when the probe fails; no

docs/drivers/S7-Test-Fixture.md

@@ -17,12 +17,12 @@ session types, PUT/GET-disabled enforcement — all need real hardware.
 `tests/ZB.MOM.WW.OtOpcUa.Driver.S7.IntegrationTests/` stands up a
 python-snap7 `Server` via `Docker/docker-compose.yml --profile s7_1500`
 on `localhost:1102` (pinned `python:3.12-slim-bookworm` base +
-`python-snap7>=2.0`). Native-Python fallback under `PythonSnap7/` kept
-for contributors who prefer to avoid Docker. `Snap7ServerFixture` probes
-the port at collection init + skips with a clear message when unreachable
-(matches the pymodbus pattern). `server.py` reads a JSON profile + seeds
-DB/MB bytes at declared offsets; seeds are typed (`u16` / `i16` / `i32` /
-`f32` / `bool` / `ascii` for S7 STRING).
+`python-snap7>=2.0`). Docker is the only supported launch path.
+`Snap7ServerFixture` probes the port at collection init + skips with a
+clear message when unreachable (matches the pymodbus pattern).
+`server.py` (baked into the image under `Docker/`) reads a JSON profile
++ seeds DB/MB bytes at declared offsets; seeds are typed (`u16` / `i16`
+/ `i32` / `f32` / `bool` / `ascii` for S7 STRING).
 
 **Unit layer**: `tests/ZB.MOM.WW.OtOpcUa.Driver.S7.Tests/` covers
 everything the wire-level suite doesn't — address parsing, error

docs/v2/dev-environment.md

@@ -178,13 +178,9 @@ real PLC instead of the simulator:
 - `S7_SIM_ENDPOINT` (default `localhost:1102`)
 - `OPCUA_SIM_ENDPOINT` (default `opc.tcp://localhost:50000`)
 
-**Native fallbacks** — contributors who prefer not to run Docker can
-launch some fixtures natively:
-
-- Modbus: `pip install "pymodbus[simulator]==3.13.0"` + `.\Pymodbus\serve.ps1 -Profile <profile>`
-- S7: `pip install python-snap7` + `.\PythonSnap7\serve.ps1 -Profile s7_1500`
-- AB CIP: build `ab_server` from libplctag + drop on `PATH` (fixture auto-detects + spawns it)
-- OpcUaClient: no native fallback documented — Docker is the simplest route.
+No native launchers — Docker is the only supported path for these
+fixtures. A fresh clone needs Docker Desktop and nothing else; fixture
+TCP probes skip tests cleanly when the container isn't running.
 
 See each driver's `docs/drivers/*-Test-Fixture.md` for the full coverage
 map + gap inventory.