Protocol field rollout checkpoint
Root owns12 driver forms (excluding Calculation),10 device forms and13 tag editors after the OT01 field-pattern freeze. The common resilience/identity/collection/picker wrappers and modal pages remain the sister agent's scope. Existing compact native label geometry is retained; native for/id and hint/error relationships implement the same shared field contract without changing defaults, model parsing, emitted JSON or protocol behavior. InputNumber's existing parser feedback appears only when an EditContext exists; standalone bodies retain their original no-EditForm support.
The initial35 real component cases render two simultaneous instances with actual controls, positive NativeAlarm fields and a mutation-refusing script-list fake. Only common resilience is explicitly stubbed because it has a separate owner/contract suite. Initial result:34failed/1passed. One failure was an incorrect inventory assumption: MqttDevice, like GalaxyDevice, is informational and has no per-device endpoint. The corrected expectation explicitly asserts no controls for both, leaving33 actual naming/duplicate-ID failures in the baseline; neither view gains invented connection fields. The initial raw result remains retained. No tests are skipped. Native IDs/names and referenced descriptions are checked on rendered DOM, not source declarations. Default/conditional protocol serialization tests remain required for each batch.
Batch1: AbCip, AbLegacy and Focas driver forms now have scoped label/control IDs, existing hint relationships and existing InputNumber parser feedback. AbCip's existing browse-delay domain message joins the persistent field feedback container without changing its reject-before-emit behavior. Batch contract/parity results:59passed/0failed, including actual standalone/parser-feedback cases for these three forms; remaining protocol failures are expected until their own migration batch.
Batch2: Galaxy, Heidenhain and Modbus driver forms:30focused field/parser/standalone and existing model/parity tests pass. Protocol C# bodies and existing event/bind expressions remain byte-for-byte unchanged across the35-file owned inventory; check-protocol-boundaries.py verifies that boundary independently of rendered field tests. Conditional aggregate model errors retain their original scope, rather than being attributed to unrelated controls.
Batch3: MQTT, MTConnect and OPC UA Client driver fields:98focused checks passed. Existing number parser messages now use the visible human field label through DisplayName across the nine migrated drivers; all nine field/standalone/parser groups plus existing page serialization/map tests pass188/188. No default, emitted JSON, callback or protocol-body change.
Batch4: S7, SQL and TwinCAT driver fields:115focused/serialization/parity cases pass. The named-queries textarea was the one remaining rendered name failure after initial association; its existing visible panel heading now supplies the name, and existing connection-ref/queries errors have persistent correctly scoped feedback targets. Raw initial failure is retained. Protocol C# and existing event/bind expressions remain unchanged.
Tag batch1: AB CIP, AB Legacy and FOCAS editors retain defaults and callbacks while receiving unique native labels/IDs;154focused field/model/authoring parity checks pass. FOCAS’s existing address/data-type mismatch now has one persistent linked feedback target for exactly those two fields, preserving its original refusal predicate.