docs: point markdown backlogs at Gitea issues (status lives in Gitea)

docs/drivers/AbLegacy.md

@@ -1,5 +1,8 @@
 # AB Legacy Driver
 
+> **Status lives in Gitea.** Open follow-ups and known gaps noted in this doc are tracked as issues on
+> gitea.dohertylan.com/dohertj2/lmxopcua (label `migrated`, 2026-11-06). This doc describes the system — do not track status here; file new work as an issue.
+
 In-process native-protocol driver that exposes legacy Allen-Bradley PLCs —
 **SLC 500**, **MicroLogix**, **PLC-5**, and Logix-via-PCCC — as OPC UA nodes. It
 runs inside the OtOpcUa server's .NET 10 AnyCPU process and speaks PCCC over
@@ -274,7 +277,7 @@ Simulator evidence:
   [Wire evidence](#wire-evidence-native-pccc).
 - **PLC-5 native is N-file reads only.** Every other file type and all PLC-5 writes are refused before the
   wire and reach the client as `BadNotSupported` (handle kept, health unchanged; #571 closed). Native is opt-in
-  for every family; an explicit Native on PLC-5 / `logixpccc` logs a Warning at init.
+  for every family; an explicit Native on PLC-5 / `logixpccc` logs a Warning at init. PLC-5 hardware proof → #752 (SLC/MicroLogix evidence → #592).
 - Status-bit sub-element writes (e.g. `T4:0.DN`, `C5:0.DN`) are Unsupported natively (they would clobber the
   control word); nothing goes on the wire — the driver refuses before creating the tag's runtime, so not even an
   init read is sent (`NativeAbLegacyTagRuntime.WriteRefusal` is the single predicate, asked through

docs/drivers/Mqtt.md

@@ -1,5 +1,8 @@
 # MQTT Driver
 
+> **Status lives in Gitea.** Open follow-ups and known gaps noted in this doc are tracked as issues on
+> gitea.dohertylan.com/dohertj2/lmxopcua (label `migrated`, 2026-11-06). This doc describes the system — do not track status here; file new work as an issue.
+
 In-process MQTT **broker-subscribe** driver. It holds one MQTTnet 5 client against one broker,
 subscribes to the topics its authored tags name, and forwards each PUBLISH straight to
 `ISubscribable.OnDataChange`. Ingest is **push, not poll**; writes go back out as ordinary publishes
@@ -250,7 +253,7 @@ One subscription (`spBv1.0/{GroupId}/#`) feeds a per-edge-node state machine
 - **Unsupported datatypes are skipped with a warning, never guessed**: `PropertySetList`, `Unknown`,
   extension values, and any `Template`/`DataSet` that cannot be flattened honestly. `Int8`→`Int16` and
   `UInt8`→`UInt16` widen; `*Array` variants map to the element type with the array bit set — but
-  **array metrics are not read in v1** (warned once, never fed), so the browse picker offers them, and any
+  **array metrics are not read in v1** (warned once, never fed; → #754), so the browse picker offers them, and any
   metric whose type is unsupported, **without an address**: the browse-commit refuses them rather than
   committing a tag that waits for initial data forever (R06:M-5).
 - **Ingest state is reset at every session/authoring seam** — a reconnect or a `ReinitializeAsync`

docs/drivers/Sql.md

@@ -1,5 +1,8 @@
 # SQL Poll Driver
 
+> **Status lives in Gitea.** Open follow-ups and known gaps noted in this doc are tracked as issues on
+> gitea.dohertylan.com/dohertj2/lmxopcua (label `migrated`, 2026-11-06). This doc describes the system — do not track status here; file new work as an issue.
+
 Getting-started guide for the `Sql` driver — a **read-only** Equipment-kind driver that polls rows
 out of a relational database and publishes them as OPC UA variables. For the design rationale read
 [`docs/plans/2026-07-15-sql-poll-driver-design.md`](../plans/2026-07-15-sql-poll-driver-design.md);
@@ -16,7 +19,7 @@ already writes to. There is no protocol here and nothing to "connect" to a machi
 (`Npgsql`) and `Oracle` (ODP.NET managed — **Oracle 12.2 or later**, the floor the
 `FETCH FIRST` paging needs). `SqlProvider` also declares `MySql` and `Odbc`, but those remain
 **reserved names, not working backends** — authoring one fails the driver rather than silently
-falling back.
+falling back. → #753
 
 Two provider-specific things are worth knowing before you author against them:
 
@@ -30,7 +33,7 @@ Two provider-specific things are worth knowing before you author against them:
 **Read-only, structurally.** `SqlDriver` does not implement `IWritable`, so no configuration can
 produce a write. The `allowWrites` config field exists and is **inert**; the factory *warns* when it
 is authored `true` rather than failing, on the grounds that the flag cannot do harm but an operator
-who believes writes are enabled can.
+who believes writes are enabled can. → #753
 
 ## Tag models
 
@@ -106,7 +109,7 @@ canonical text form. SQL Server behaves the same way.
 authored `keyValue` refused the tag while the identically-bound `whereValue` was served — and the
 deploy gate reported the key as *missing* when it was right there in the blob.)
 
-### `Query` — deferred to P3
+### `Query` — deferred to P3 (→ #753)
 
 Named arbitrary-`SELECT`. **The v1 parser rejects it**, and that refusal is enforced end-to-end —
 parser, validator, planner and the AdminUI editor all decline it rather than accepting the value and