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

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