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

docs/plans/2026-06-14-deferred-followups.md

@@ -1,5 +1,8 @@
 # Deferred Follow-ups Implementation Plan
 
+> **Status lives in Gitea.** Open items from this file are tracked as issues on gitea.dohertylan.com/dohertj2/mxaccessgw
+> (label `migrated`, 2026-11-06). This file is a historical/design record — do not track status here; file new work as an issue.
+
 **Date:** 2026-06-14
 **Status:** D1 executed (commit 4af24b9 — `mxgateway.alarms.provider_switches` emitted in `DashboardSnapshotService.cs:198`). D2 resolved as no-op (see resolution section below). D3 (ForceSubtag validation) was exercised through the forced-subtag work (`2026-06-15-forced-subtag-mode-fix.md`); D4 (windev backup prune) has no completion record in the repo and is treated as pending; D5 (wonder redeploy) was superseded by later wonder deployments. D3–D5 are ops/validation with no code.
 **Context:** After the alarm-subtag-fallback cleanup (merged `5976770`) and its redeploy to
@@ -281,7 +284,7 @@ remain explicitly open — none are code defects:
   emitted on the alarm failover/failback path and unit-tested, but the dev rig's object-driven
   alarms can't be made to fail a real alarmmgr→subtag switch from outside, so the `reason` tagging
   is unproven against a live failover. Re-verify when a rig (or capture) can drive an actual
-  alarmmgr fault. (stillpending §1.3.)
+  alarmmgr fault. (stillpending §1.3.) → #210
 
 - **`DrainEvents` is a diagnostic snapshot, not an exhaustive drain.** The worker now answers
   `DrainEvents` (handled in `WorkerPipeSession`, off-STA), but it pulls from the same event queue
@@ -294,7 +297,7 @@ remain explicitly open — none are code defects:
   / `SetBufferedUpdateInterval` are implemented and live-confirmed; the empty `NoData` bootstrap
   event converts cleanly live (`f7ada90`). A real parallel quality/timestamp sample batch
   (length > 1) is undrivable on the current rig, so the multi-sample path is exercised only by unit
-  tests against a fake `IMxAccessServer`. (stillpending §3.2.)
+  tests against a fake `IMxAccessServer`. (stillpending §3.2.) → #210
 
 - **8-arg alarm ack operator `domain`/`full_name` — vendor-blocked.** The AVEVA `IwwAlarmConsumer2`
   8-arg `AlarmAckByName` returns −55 (stub) and `AlarmAckByGUID` is `E_NOTIMPL` on this build, so the