dohertj2/lmxopcua
1
0
Fork 0
Code Issues 32 Pull Requests Actions Packages Projects Releases Wiki Activity

docs(mtconnect): live gate PASSED against the shared AllowPut fixture (15/15); rig OPC UA leg deferred to the chrome session

Browse Source
This commit is contained in:
Joseph Doherty
2026-08-05 07:14:55 -04:00
parent 0e3381d599
commit e238a71bbc
2 changed files with 13 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/plans/2026-08-05-mtconnect-writeback-design.md
+12 -1
View File
@@ -1,6 +1,17 @@
# MTConnect write-back + MQTT write-through record reconciliation — design
**Status:** DRAFT 2026-08-05.
**Status:** DONE 2026-08-05 — merged to master (`0e3381d5`); unit suites green (MTConnect 534/534,
MQTT 658/658, AdminUI 1064/1064); **live gate PASSED** (§4): the full integration suite ran live
against the shared fixture (`10.100.0.35:5000`, AllowPut now on) — 15/15, 0 skipped — covering the
write round-trip (value read back from `/current`), the real agent-refusal → `BadCommunicationError`
mapping (with the no-`deviceName` → `BadNodeIdUnknown` falsifiability control), and the disabled
gate (`BadNotWritable`, agent untouched). The same legs also ran against a local OrbStack fixture
during development with agent-log corroboration. **One leg is deliberately deferred to the
operator's chrome session:** the docker-dev rig OPC UA leg (author an MTConnect driver with
`write.enabled` + a `ReadWrite` tag in AdminUI, deploy, `Client.CLI write`, read back) — authoring
requires the AdminUI, and per the operator's instruction chrome-driven gates run separately.
Remember the CurrentWrite caveat when running it: the tag must be authored `ReadWrite`
(browse-commit defaults to `Read`).
## 1. Scope correction: the MQTT half of this request is already shipped