check-issue-refs: blanket-ban tracker tags in markdown too, no exceptions

swarmctl/README.md

@@ -32,7 +32,8 @@ There used to be: a private `users.json` here, canonical, with `users.yml`
 rendered from it, while `swarm-authelia-bridge` kept its own pair against
 the _same_ physical file. Two canonical stores for one file is a seam, and
 it bit — a writer whose own JSON was missing could not tell "nothing here
-yet" from "someone else's users", and refused to write (#3422).
+yet" from "someone else's users", and refused to write
+(`$HIVE_FORGE_URL/hyperhive/hyperhive/issues/3422`).
 
 The argument for the split was that it let this crate work without a YAML
 parser. It didn't: the JSON was read back on every run, so the round-trip