docs(index): OtOpcUa master 363f0d81 — Galaxy status mapping (#866/#872), ring event queue (#870)

2026-11-11 15:38:51 -05:00
parent d042890d50
commit 601f7ae0e6
2 changed files with 7 additions and 1 deletions
@@ -454,3 +454,9 @@ AddRoute of the dev Mac (`oee-tagdump-mac`, `10.181.206.245.1.1`) on the two tes
    - **Galaxy VD03:** found #864/#865 (per-platform host status was always empty in production).
  - **Ops lesson:** `kill $(lsof -ti tcp:PORT)` killed OrbStack's network helper and took every local container down. Kill proxies by PID.
  - **Control plane (#868):** the deploy coordinator survives a ConfigDb outage at start (four review rounds). Node `NodeDeploymentState` rows now stay Applying until the address-space outcome is known.
+
+- **2026-11-11 Galaxy status + event-queue batch (master `363f0d81`, not deployed).** Closed #866, #870, #871; filed #872 (Warning/Pending status rows, open).
+  - **ScadaBridge consumer impact:**
+    - **#866 (Galaxy value status):** a failure status row's `detail` is an MXAccess `MxStatusDetail` code, never an OPC DA quality byte. Bad values now carry specific codes: stopped platform/engine → `BadCommunicationError` (was generic Bad), invalid references → `BadConfigurationError`, type errors → `BadTypeMismatch`, timeout → `BadTimeout`. **OK status rows are now graded by the item's OPC DA quality**: before, an off-scan / Bad / Uncertain attribute with an OK status row was published **Good**; it now arrives Bad/Uncertain. Detail-0 failure rows route on category, not `detected_by` (#872). Live, read-only on VD03: healthy attributes unchanged (Good).
+    - **#870:** event monitored-item queues are a ring buffer (SDK-parity tested); no wire change, lower Lock hold at large queues.
+  - **CI (#871):** two unit-test races that failed hosted runs 1218–1220 fixed (MeshPsk refresh, credential-lockout burst).