diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index a271b7e4..711b5dcc 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -466,8 +466,9 @@ jobs:
           # NM+dnsmasq, dns-delegate, no-resolver) across five distros,
           # plus end-to-end scenarios that boot a real fips daemon with a
           # real TUN and assert `dig @127.0.0.53 AAAA <npub>.fips`
-          # returns AAAA. Pins the production DNS bind path that
-          # ISSUE-2026-0002 lived in. Single matrix entry runs all 13
+          # returns AAAA. Pins the production DNS bind path where a
+          # loopback-delivered query was once misattributed to the mesh
+          # interface and dropped. Single matrix entry runs all 13
           # scenarios sequentially; ~7-12 min warm, ~12-15 min cold.
           - suite: dns-resolver
             type: dns-resolver
diff --git a/packaging/common/fips-dns-setup b/packaging/common/fips-dns-setup
index 2a6678b2..6617060f 100755
--- a/packaging/common/fips-dns-setup
+++ b/packaging/common/fips-dns-setup
@@ -117,8 +117,7 @@ EOF
 #   - The IPV6_PKTINFO ifindex attribution behaviour where Linux reports
 #     a packet to fips0's own IPv6 address as arriving on fips0 (despite
 #     loopback delivery), which would otherwise be silently dropped by
-#     the daemon's mesh-interface filter — see ISSUE-2026-0002 in the
-#     project tracker.
+#     the daemon's mesh-interface filter.
 #
 # This backend is the recommended path on every systemd-resolved host
 # that doesn't have native dns-delegate support (systemd >= 258).
diff --git a/testing/chaos/scenarios/bloom-storm.yaml b/testing/chaos/scenarios/bloom-storm.yaml
index 9a017512..ca94eba9 100644
--- a/testing/chaos/scenarios/bloom-storm.yaml
+++ b/testing/chaos/scenarios/bloom-storm.yaml
@@ -72,7 +72,7 @@ netem:
 # `interval_secs`, the policies on the two listed edges are swapped.
 # This drives n04 to alternate parents between n02 and n03 each
 # round. The 4s cadence and 5ms-vs-100ms delta come from the
-# original ISSUE-2026-0019 reproduction harness — they are
+# original reproduction harness for this flap — they are
 # calibrated to produce a parent switch per round under the
 # zero-hysteresis FIPS overrides below.
 link_swap:
diff --git a/testing/interop/interop-test.sh b/testing/interop/interop-test.sh
index ab27b3c1..83c1ac9f 100755
--- a/testing/interop/interop-test.sh
+++ b/testing/interop/interop-test.sh
@@ -949,7 +949,7 @@ echo ""
 # versions. A mixed-version bloom/tree-encoding divergence shows up as a
 # node that never produces an in-band estimate (or returns null). Strict
 # band = [0.75N, 1.25N]; polled up to MESH_SIZE_TIMEOUT (the estimate
-# converges over minutes — see ISSUE-2026-0046 on its transient jitter).
+# converges over minutes and is transiently jittery).
 echo "Phase 7: Mesh-size estimate convergence (strict ±25% of true N=$NUM_NODES)"
 PASSED=0; FAILED=0
 ms_lo="$(awk -v n="$NUM_NODES" 'BEGIN{printf "%.2f", 0.75*n}')"
diff --git a/testing/mesh-lab/compose-trace-nat.yml b/testing/mesh-lab/compose-trace-nat.yml
index 63680d19..cd172a16 100644
--- a/testing/mesh-lab/compose-trace-nat.yml
+++ b/testing/mesh-lab/compose-trace-nat.yml
@@ -1,6 +1,6 @@
 # Compose override that bumps RUST_LOG to trace level on the modules
 # relevant to NAT-traversal handshake-completion flake evidence
-# collection (ISSUE-2026-0027):
+# collection:
 #
 #   - fips::discovery::nostr            — overlay advert publish/consume
 #                                          (where the cross-init race begins)
diff --git a/testing/static/scripts/rekey-test.sh b/testing/static/scripts/rekey-test.sh
index bc78113b..4a4d39c2 100755
--- a/testing/static/scripts/rekey-test.sh
+++ b/testing/static/scripts/rekey-test.sh
@@ -176,7 +176,7 @@ RECONVERGE_STALL=10
 TIMEOUT=5
 CONVERGENCE_PING_TIMEOUT=1
 # Strict-ping retry policy for the per-phase ping_all asserts. Under 1%
-# i.i.d. packet loss (the lab condition surfaced by ISSUE-2026-0028) a
+# i.i.d. packet loss (the lab condition this retry policy is sized for) a
 # single-shot ping fails at roughly 2% per directed pair, so a 20-pair
 # strict assert misses with probability ~1 - (0.98)^20 ≈ 33%, which is
 # below the per-pair loss-math floor but well above the routing-state