lmxopcua/docs/plans/2026-07-24-driver-expansion-tracking.md

Driver-expansion — Waves 0–2 tracking

Living status tracker for the driver-expansion program (Waves 0, 1, 2). One row per deliverable, each pointing at its design doc, its implementation plan (once written), and its current status. The authoritative architecture index is the program design doc; this file is the authoritative progress index.

Program design (architecture / shared contract / build order): 2026-07-15-driver-expansion-program-design.md

Last updated: 2026-07-24.

Legend

Status	Meaning
✅ Done	Merged to master, tests green.
🟡 Live gate open	Code merged; a live /run or hardware-gated verification still outstanding.
📝 Plan ready	Executable implementation plan (*-implementation.md + .tasks.json) written; not yet built.
📐 Design only	Design doc exists; no implementation plan yet — writing-plans is the next step.
⛔ Not started	No design, no plan.

Doc types (per the writing-plans skill): a design states architecture, decisions, and risks; an implementation plan is the bite-sized, TDD, file-path-level task list the subagent-driven executor runs off, with a co-located .tasks.json for resume. A deliverable is only buildable once it reaches 📝.

Summary

Wave	Deliverable	Design	Impl. plan	Status	Effort	Fixture / hardware
0	Universal Discover-backed browser	design	plan · tasks	🟡 Live gate open	S–M	none (retrofits shipped drivers)
1	Modbus RTU (extend Modbus)	design	plan · tasks	📝 Plan ready (11 tasks)	S (lowest)	pymodbus rtu_over_tcp — CI-simulatable, no new infra
1	SQL poll	design	plan · tasks	📝 Plan ready (22 tasks)	S–M	existing central SQL Server 10.100.0.35,14330 + SQLite unit
2	MTConnect Agent	design	plan · tasks	📝 Plan ready (23 tasks)	S–M	Dockerized mtconnect/cppagent — CI-simulatable
2	MQTT / Sparkplug B	design	plan · tasks	📝 Plan ready (27 tasks, P1+P2)	M–L	Mosquitto/EMQX + C# Sparkplug sim — CI-simulatable

Waves 3+ (BACnet/IP, Omron) and the deferred MELSEC are tracked in the program design doc §6/§8, not here. Omron CIP is the program's sole real-hardware wire gate; BACnet's broadcast/BBMD leg is env-gated live. Both are out of this file's scope until they're pulled forward.

---

Wave 0 — Universal Discover-backed browser 🟡

What it is. One generic DiscoveryDriverBrowser (+ CapturingAddressSpaceBuilder, CapturedTreeBrowseSession, BrowserSessionService fallback, and the ITagDiscovery.SupportsOnlineDiscovery gate) that turns any driver's ITagDiscovery.DiscoverAsync into an AdminUI browse tree. It is the Wave-0 gate: every browsable new driver depends on this seam, and it retrofits browse to the already-shipped AbCip / TwinCAT / FOCAS drivers for near-zero marginal cost.

• Design: 2026-07-15-universal-discovery-browser-design.md
• Implementation plan: 2026-07-15-universal-discovery-browser-implementation.md · .tasks.json
• Status: 🟡 code-complete + merged, live gate open.
  • Merged to master — 056887d6 (Merge feat/universal-discovery-browser — Wave-0 universal Discover-backed browser), 2026-07-15.
  • Implementation plan: 19 / 19 tasks completed.
  • Lit up AbCip / TwinCAT / FOCAS pickers with zero per-driver browse code.
• Outstanding: the full tree-render live /run gate is fixture-blocked — tracked as Gitea #468. Complete this before leaning on browse in Wave 2/3.

---

Wave 1 — low-effort / high-leverage pair 📝

Both are fully CI-simulatable with zero new hardware; Modbus RTU needs no new infra at all, and SQL poll reuses the always-on central SQL Server. This is the recommended next build.

Modbus RTU — 📝 Plan ready

• Design: 2026-07-15-modbus-rtu-driver-design.md
• Implementation plan: 2026-07-24-modbus-rtu-driver.md · .tasks.json — 11 tasks (1 trivial / 5 small / 2 standard / 3 high-risk).
• Scope: extend the existing Modbus driver with a Transport selector (RTU CRC-16 + FC-aware length, no TxId) + a rtu_over_tcp pymodbus docker profile + the AdminUI selector. Direct-serial transport is descoped (user, 2026-07-15) — RTU-over-TCP via a serial→Ethernet gateway is the only shipped mode, so there is no serial hardware gate.
• Fixture: add an rtu_over_tcp profile to the existing Modbus integration fixture. First P1 step is confirming the pymodbus simulator exposes the RTU framer on a TCP server.
• Effort: S — the lowest on the roadmap. Recommended first.

SQL poll — 📝 Plan ready

• Design: 2026-07-15-sql-poll-driver-design.md
• Implementation plan: 2026-07-24-sql-poll-driver.md · .tasks.json — 22 tasks. ISqlDialect seam in from day one; only the SQL Server dialect built in v1 (Postgres/ODBC deferred).
• Scope: a bespoke schema-browser driver polling a SQL table into equipment tags (SQL Server P1; Postgres/ODBC land in P2/P3 behind ISqlDialect).
• Fixture: SQLite unit fixture (primary) + an env-gated integration fixture against the existing central SQL Server (10.100.0.35,14330) with a seeded SqlPollFixture DB. The blackhole/timeout live-gate pauses a dedicated mssql container — never the shared central SQL Server (it hosts ConfigDb).
• Effort: S–M.

---

Wave 2 — strategic telemetry / UNS pair 📝

Both CI-simulatable on the shared docker host, no hardware.

MTConnect Agent — 📝 Plan ready

• Design: 2026-07-15-mtconnect-driver-design.md
• Implementation plan: 2026-07-24-mtconnect-driver.md · .tasks.json — 23 tasks. Task 0 is the TrakHound-vs-hand-rolled client decision; browse-picker live-verify is gated on Wave-0 #468.
• Scope: P1 Agent MVP (IDriver+ITagDiscovery+IReadable+ISubscribable+probe+rediscover), browse free via the Wave-0 universal browser (SupportsOnlineDiscovery=true, no browser code), typed editor, UNAVAILABLE→BadNoCommunication mapping, ring-buffer re-baseline paging.
• Fixture: canned XML unit fixtures (bulk of coverage) + a dockerized mtconnect/cppagent integration fixture (env-gated). Depends on Wave 0's browse seam being live-verified (#468).
• Effort: S–M (≈1–1.5 wk with TrakHound, ≈2.5–3 wk hand-rolled).

MQTT / Sparkplug B — 📝 Plan ready

• Design: 2026-07-15-mqtt-sparkplug-driver-design.md
• Implementation plan: 2026-07-24-mqtt-sparkplug-driver.md · .tasks.json — 27 tasks (P1 plain MQTT = Tasks 0–14, a complete shippable milestone; P2 Sparkplug B = Tasks 15–26). Task 0 is the mandatory MQTTnet-5/net10 + central-pinning validation spike.
• Scope: P1 plain MQTT (MQTTnet-5 connect/TLS/auth + hand-rolled reconnect, subscribe→ OnDataChange, retained last-value read, #-observation browser); P2 Sparkplug B ingest (vendored Tahu proto, birth/alias/seq-gap/rebirth state machine, death→STALE).
• Fixture: Mosquitto/EMQX broker (TLS + real auth, not anonymous) + a project-owned C# Sparkplug edge-node simulator for the rebirth/seq-gap/death test matrix + env-gated live suite (MQTT_FIXTURE_ENDPOINT).
• Effort: M–L. Top risks: Sparkplug state-machine correctness; MQTTnet-5/net10 + the repo's fragile central pinning (mitigated by hand-rolling Tahu over one MQTTnet-5 client).

---

Next actions

1. Close the Wave-0 live gate (Gitea #468) — unblocks browse verification for MTConnect/BACnet.
2. Build Wave 1 via subagent-driven development — Modbus RTU first (lowest effort, no new infra), then SQL poll. Both plans are 📝 ready; execute with /superpowers-extended-cc:executing-plans docs/plans/2026-07-24-modbus-rtu-driver.md.
3. Build Wave 2 (MTConnect, then MQTT/Sparkplug) — both plans 📝 ready. MTConnect's browse leg wants #468 closed first; MQTT's Task 0 pinning spike gates everything after it.

Update this file's Summary table and per-wave status whenever a deliverable changes state.