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

docs/web-ui/agent.md

@@ -85,7 +85,7 @@ structurally rather than for one specific trigger. Two columns:
     `agent_links()` in hive-agent is the single source of truth for
     both. No separate overflow (`⋯`) menu exists any more — it used
     to hold exactly this dashboard link plus a rebuild-container action
-    (mara, #3704: "remove rebuild button, move link to
+    (mara, `$HIVE_FORGE_URL/hyperhive/hyperhive/issues/3704`: "remove rebuild button, move link to
     dashboards into links menu") — rebuild had no real discoverability
     need of its own (the dashboard's own R3BU1LD button already covers
     it) so it's gone outright, and the dashboard link moved here,

docs/web-ui/css-vars.md

@@ -67,7 +67,7 @@ default palette). Default hexes shown are Catppuccin Mocha.
 | `--blue`       | `base0D`                    | `#89b4fa`   | links, interactive accent (distinct from cyan)                  |
 | `--purple`     | `base0E`                    | `#cba6f7`   | accent — active tabs, links, highlights                         |
 | `--pink`       | `base0F`                    | `#f5c2e7`   | thinking events                                                 |
-| `--crust`      | `mix(base00 58%, #000)`     | `#11111b`   | terminal / code block background (below `--bg`)                 |
+| `--crust`      | `mix(base00 58%, #000000)`  | `#11111b`   | terminal / code block background (below `--bg`)                 |
 | `--muted`      | `mix(base05 55.5%, base00)` | `#7f849c`   | secondary / dimmed text                                         |
 | `--subtext0`   | `mix(base05 77.7%, base00)` | `#a6adc8`   | toolbar/status text; dimmer than `--fg`, lighter than `--muted` |
 

docs/web-ui/dashboard.md

@@ -146,7 +146,7 @@ part-way through a spawn is byte-identical on disk to a tombstone, and
 the pane lists both. The pane carries a standing warning to that effect, and
 the row badge says `offline` rather than `destroyed` — the absence of a
 container is all hive-c0re can actually prove. Fixing it properly
-needs a recorded destroy: **#3020**, deferred to the swarm-controller /
+needs a recorded destroy: **`$HIVE_FORGE_URL/hyperhive/hyperhive/issues/3020`**, deferred to the swarm-controller /
 snapshot-storage rework where the problem changes shape.
 
 *Stale permission entries*: agents with explicit capability or
@@ -236,7 +236,7 @@ than reconstructing chrome hive-c0re no longer sends. Settled entries
 render their **full step tree**, not just a bare summary — the wire
 doesn't filter `Done` nodes out.
 
-**State filter (#2606).** A row of per-state checkboxes above
+**State filter (`$HIVE_FORGE_URL/hyperhive/hyperhive/issues/2606`).** A row of per-state checkboxes above
 the tree — one per lifecycle state, matching the row glyphs — lets the
 operator narrow which root groups render; unchecking a state re-fetches
 `GET /api/jobq/graph?states=<checked, comma-joined>` rather than
@@ -811,7 +811,7 @@ below).
 
 ### Status badges
 
-**Which single badge (#3139):** `ContainerView.failed`
+**Which single badge (`$HIVE_FORGE_URL/hyperhive/hyperhive/issues/3139`):** `ContainerView.failed`
 (systemd `ActiveState=failed` — the unit exhausted its bounded
 restarts and gave up on its own) draws a red `✖ gave up` badge;
 otherwise a plain muted `■ not running` — a container an operator

docs/web-ui/shape.md

@@ -244,7 +244,8 @@ render, `restoreOpenDetails()` re-applies after. Long-content
 drill-ins (file previews, diffs, journald logs) now open in the
 **side panel** (see below) rather than expanding inline. The
 dashboard's own answered-questions history list was the only
-`<details data-restore-key>` consumer and is gone (#3721)
+`<details data-restore-key>` consumer and is gone
+(`$HIVE_FORGE_URL/hyperhive/hyperhive/issues/3721`)
 — `snapshotOpenDetails()` / `restoreOpenDetails()` currently have
 nothing to restore, kept in place for the next collapsible section
 that needs it rather than ripped out along with their one caller.