merge: MTConnect review findings resolved (Driver.MTConnect-004 write-back authoring, -005/-006/-007)

# Conflicts:
#	code-reviews/Driver.MTConnect/findings.md

docs/drivers/MTConnect.md

@@ -284,7 +284,10 @@ for why Interfaces was rejected as the write-back shape. Design record:
    `AllowPutFrom = <host list>` so only named hosts may write; that list is the Agent's
    own access control and this driver neither reads nor influences it.
 2. **The driver** — `"Write": { "Enabled": true }` in the driver config (default
-   `false`; an absent block is disabled).
+   `false`; an absent block is disabled). Authored in the AdminUI on the `/raw` driver
+   config modal's **Write-back** section (`MTConnectDriverForm`), which writes the block
+   explicitly in both states — so turning the switch back off clears a previously
+   authored `true` rather than leaving it standing.
 
 Either gate alone leaves the shipped read-only behaviour unchanged: with `Write.Enabled`
 off every slot is refused `BadNotWritable` without an Agent being touched, and with