# OT13 device form field associations Assigned scope is ten actual DeviceForms surfaces. Source inspection found **eight editable forms,20controls and six InputNumber fields**. Galaxy and MQTT are both intentionally informational: their connection belongs to the driver, and MQTT preserves a legacy-device-key warning. Both files remain byte-identical; no device endpoint or dummy field was invented. Per-file source inventories include these explicit dispositions. The eight forms retain native compact label/grid geometry and existing protocol controls. Per-instance GUID field scopes now connect visible labels, IDs and existing hint/error targets. InputNumber uses its visible human label for parser DisplayName; its existing Blazor ValidationMessage is rendered only with a cascading EditContext, inside an always-present described target. Standalone use has no new EditForm requirement. Heidenhain's existing aggregate model error still validates only Host/Port and is linked only to those endpoint controls; the existing credential-reference explanation is linked to its three reference inputs. Validation rules, defaults, models, JSON keys/values, events and binds are untouched. The existing central cases supplied the meaningful red:8missing-name/duplicate-ID failures and12passes across20device cases, no skips. After associations all20pass (two instances/unique IDs/resolved descriptions plus standalone for all10surfaces). Existing model/save-gate/dispatch/authoring/serialization parity checks pass112/112, no skips. The shared35-form source guard independently confirms original C# bodies and all event/bind expressions unchanged; helper prefixes only. No test framework/package change or weakened assertion/skip was introduced. The initial MQTT test assumption was corrected by the root owner before this batch; empty controls remain an asserted contract for both informational surfaces. A separate reusable Razor-only host mounts only a hardcoded whitelist of the eight actual component types, two instances each, over local draft callbacks. Program registers no backend services or connection/operation endpoints. At1440/390, actual browser DOM contains40controls with unique IDs, visible labels and resolved descriptions;16representative label clicks focus the correct native control. Existing endpoint/credential-reference hints resolve. A fractional invalid integer in Modbus Port produces the human Port/number parser message with aria-invalid=true and no config-change callback. No save/probe/OPC/DB/network/credential-store action exists. The first browser click reached SSR before circuit readiness; an explicit OnAfterRender fixture marker fixes the harness readiness condition, with no production code change. This is native label/focus/help/parser proof, not a blanket screen-reader or whole-host acceptance claim. Evidence is under `device-forms/`: red/green/contract TRX and original logs, source boundary guard, browser-results.json/captures and summary.json. Source inventory files are named `-source-inventory.json`. `canary/` is reusable for root's frozen driver/tag families: add explicit approved type entries or own pages and only mutation-refusing synthetic script reads if required. Do not add production host services or arbitrary type/query activation. Its completed owned process is stopped and loopback closed; root may rebuild it with a separate artifacts path after adding its own pages. The shared ot-ui host and other agents' source/test ownership remain untouched. Commands from repository root: ```sh dotnet test tests/Server/ZB.MOM.WW.OtOpcUa.AdminUI.Tests/ZB.MOM.WW.OtOpcUa.AdminUI.Tests.csproj --artifacts-path /tmp/ot13-device-fields-artifacts --filter 'FullyQualifiedName~ProtocolFormAccessibilityTests&DisplayName~DeviceForm' python3 docs/ui-consistency/ot13-root-fields/check-protocol-boundaries.py # The exact112-test contract filter and results are retained in contracts.log/TRX. dotnet run --project docs/ui-consistency/ot13-root-fields/device-forms/canary/DeviceFormCanary.csproj --artifacts-path /tmp/ot13-device-browser-artifacts --no-launch-profile --urls http://127.0.0.1:0 python3 docs/ui-consistency/ot13-root-fields/device-forms/check-browser.py ``` The browser helper reads the local host's actual startup origin from browser-host.log; redirect a new run there. Parent owns central tests, final cross-family/browser inventory and gate/ledger updates. Scope boundary does not imply all35form families were completed by this device slice.