docs: MTConnect write-back recorded; stale MQTT write-through/browse-gap records reconciled

docs/drivers/Mqtt.md

@@ -521,6 +521,11 @@ and only** browse action that publishes anything.
 - **Scope** is the last node clicked in the tree. A device or metric resolves **up to its owning edge
   node** (Sparkplug has no device-scoped rebirth); a group fans out to every observed edge node
   beneath it and is refused **whole** past 32, publishing nothing.
+- **An empty tree can still arm a rebirth** ([#514](https://gitea.dohertylan.com/dohertj2/lmxopcua/issues/514),
+  fixed `7f53bd96`): when no scope is selected the panel offers a `group/edgeNode` input, so a plant
+  whose edge nodes all birthed before the window opened — the exact case the affordance exists for —
+  is reachable without a tree click. Deliberately an **edge node**, never a group: a typed group
+  broadcast is a self-inflicted broker storm on a large plant.
 - **Two clicks, never one** — `Request rebirth…` arms a confirm panel naming the resolved scope and
   its consequence; changing the selection disarms it.
 - **Gated on `DriverOperator`**, enforced server-side in `BrowserSessionService.RequestRebirthAsync`
@@ -547,14 +552,6 @@ in the rebuilt tree.
 > affected **every** driver's picker since 2026-05-28; it surfaced here because choosing a rebirth
 > scope is the first flow that requires clicking a label rather than the ▶ toggle.
 
-> ⚠️ **Known gap — a completely empty tree cannot arm a rebirth.** The rebirth scope is taken from the
-> last node clicked *in the tree*, so on a plant that has not birthed since the window opened there is
-> nothing to click and `Request rebirth…` stays disabled — the exact case the affordance exists for.
-> `MqttBrowseSession.ResolveRebirthTargets` already accepts a bare `{group}/{edgeNode}` for a node the
-> window has never seen (it calls that "the prime rebirth target"); what is missing is a UI path to
-> enter one, or to default the scope to the driver's own configured `GroupId`. Until then: use
-> **Refresh** after any birth, or author the tags by **Manual entry**, which is always available.
-
 ## Test Connect
 
 `MqttDriverProbe` performs **one CONNECT** (no SUBSCRIBE, no publish) under a `-probe-` client id and
@@ -583,8 +580,6 @@ identical words. See [TestConnectProbes.md](TestConnectProbes.md).
 
 ## Operational Notes
 
-- **Read-only.** No writes reach the broker; every node is ViewOnly. Sparkplug NCMD is used for
-  **rebirth requests only** — never to command a device.
 - **No alarms, no driver-side history.** Historization is a server-side concern (`isHistorized`).
 - **Both pair nodes subscribe independently** — MQTT fan-out is per-connection, and the Primary gate
   applies downstream, not to ingest. This is also why `clientId` must stay unset (above).