feat(mtconnect): authoring DataType warning + loud ignored-DeviceName warning (#613 slice)

Claude-Session: https://claude.ai/code/session_01Ef2ozxS7QPanGT8uoATbTe

docs/drivers/MTConnect.md

@@ -397,8 +397,21 @@ for anything beyond values-and-conditions.
    `DeviceName` (see [Write-back](#write-back--observation-injection-off-by-default)).
    So `MTConnectDriverOptions.DeviceName` does double duty — request scope for
    reads/browse, fallback write target for writes.
-3. **Nothing validates a raw tag's declared OPC UA `DataType` against the
-   blob's coercion type.** The `/probe`-sourced inference
+
+   **It is no longer silent (#613).** When the instance's raw tags carry two or
+   more distinct non-blank `RawTagEntry.DeviceName` values, driver init logs one
+   Warning naming them and the driver-level scope they collapse into. A single
+   value is not reported (it is just the `/raw` Device's own name). Real
+   per-device routing remains deferred.
+3. **Authoring only *warns* when a declared coercion type cannot hold the
+   inferred one (#613).** The AdminUI tag editor (`MTConnectTagConfigModel.Warnings()`)
+   compares the declared type with `MTConnectDataTypeInference` over the
+   `/probe` metadata a browse-commit stamped (`mtCategory`/`mtType`), and shows an
+   advisory line — it never blocks a save (the deploy gate does not refuse it) and
+   is a no-op for hand-authored blobs with no stamped metadata. `representation`
+   is not on the model, so TIME_SERIES arrays are not covered. Beyond that,
+   nothing validates a raw tag's declared OPC UA `DataType` against the
+   blob's coercion type. The `/probe`-sourced inference
    (`MTConnectDataTypeInference`) narrows how often an author picks a wrong
    type, but it doesn't close the gap — an authored `DataType` mismatched
    against the actual Agent observation still surfaces as `BadTypeMismatch`