docs(mtconnect): describe the fixed browse-commit coercion type (#560)

The comments and docs that described Driver.MTConnect-003 as live at HEAD would
have been wrong the moment 64be41d8 landed:

- code-reviews/Driver.MTConnect/findings.md — Driver.MTConnect-003 Resolved,
  with the fixing commit; module open-finding count 5 -> 4.
- code-reviews/Driver.MTConnect.Contracts/findings.md — the one clause inside
  Contracts-001's prose that asserted 003 was Open.
- docs/drivers/MTConnect.md — the coercion-precedence warning now states that a
  browse-committed tag resolves at step 1 CARRYING the step-3 answer, and that
  step 3 remains the rescue for a hand-authored / CSV / API blob with no type.
- MTConnectDriver.BuildBinding, MTConnectDataTypeInference and
  MTConnectDriverOptions.RawTags remarks — same correction, each keeping a short
  historical note of what the defect was so a reader meeting the old blobs still
  understands them.

Comment-only in src; the driver suite (538) and AdminUI suite (1474) re-run green.

code-reviews/Driver.MTConnect.Contracts/findings.md

@@ -61,7 +61,7 @@ false premise concealed a live defect rather than merely misinforming a reader.
 
 The second is what makes this worth recording rather than a tidy-up: a reader auditing the browse
 path would have taken that remark as evidence the case was handled. The underlying defect is
-recorded as `Driver.MTConnect-003` (Open, fix belongs in `RawBrowseCommitMapper`).
+recorded as `Driver.MTConnect-003` (Resolved `64be41d8`, 2026-08-10, in `RawBrowseCommitMapper`).
 
 **Recommendation:** Correct both remarks to describe the callers that exist, and — rather than
 deleting the precedence rule, which is still correct for hand-authored, CSV-imported and API-authored